[BUG] Issue with x-ms-dynamic-list

[ZeeCapp]

Type of Connector

Independent Publisher Connector

Name of Connector

eWay-CRM

Describe the bug

Our connector makes use of x-ms-dynamic-list swagger properties for dropdown values. However, this doesn't seem to work, even though it did work when we last tested it (before submitting the connector for publish). I'm not sure if there is an issue with our swagger definition or if the issue is caused by something else. When I was testing this issue, it seems that the request for the dynamic list values doesn't reach our API at all, so it seems that the issue occurs somewhere inside Power Automate before the request for the list values is sent to our API. Here is a screenshot of the error inside Power Automate:

Here is the full error message:

The dynamic invocation request failed with error: Unexpected error occurred when calling the ApiHubsRuntime API: 'System.InvalidOperationException: Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects.
   at System.Net.Http.Headers.HttpHeaders.CheckHeaderName(String name)
   at System.Net.Http.Headers.HttpHeaders.Add(String name, String value)
   at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass51_1`2.<<CallService>b__0>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 583
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<CallService>d__51`2.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 530'.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 2 - One or more important connector features are down

To Reproduce

To reproduce, you will need to create a trial account through our website - https://signup-v2.eway-crm.com/

After you have your account ready, got to Power Automate and search for the eWay-CRM connector and log in. Select the Save Company action and search for the TypeEn parameter. Click on the dropdown menu -> at this point you should see the error.

Expected behavior

The list of values should load without issues.

Environment summary

Install Method - pip 24.0
CLI version - 0.0.20
OS version - Windows 11 Pro - 26100.3476
Shell Type - PowerShell

Additional context

No additional context.

[troystaylor]

Hi Jan,
I see that your connector is in fact a certified connector and not an Independent Publisher connector, and that you haven't open-sourced your connector's Swagger file. Can you share snippets of those two actions and I can take a look?

Troy

[ZeeCapp]

@troystaylor please, excuse my mistake.

Below you should find all the relevant swagger snippets, but i can provide more if necessary.

This is the action that actually obtains the list values:

"/SearchEnumValues": {
    "post": {
        "operationId": "SearchEnumValues",
        "summary": "Search Enum Values",
        "description": "Search Enum Values",
        "x-ms-visibility": "internal",
        "consumes": [
            "application/json"
        ],
        "parameters": [
            {
                "name": "requestBody",
                "in": "body",
                "schema": {
                    "type": "object",
                    "properties": {
                        "transmitObject": {
                            "type": "object"
                        },
                        "includeForeignKeys": {
                            "type": "boolean",
                            "default": false
                        },
                        "includeRelations": {
                            "type": "boolean",
                            "default": false
                        }
                    }
                }
            }
        ],
        "responses": {
            "200": {
                "description": "Response",
                "schema": {
                    "type": "object",
                    "properties": {
                        "ReturnCode": {
                            "type": "string"
                        },
                        "Data": {
                            "type": "array",
                            "items": {
                                "type": "object",
                                "properties": {
                                    "ItemGUID": {
                                        "type": "string"
                                    },
                                    "FileAs": {
                                        "type": "string"
                                    },
                                    "En": {
                                        "type": "string"
                                    }
                                }
                            }
                        }
                    }
                }
            },
            "default": {
                "description": "Operation Failed."
            }
        }
    }
},

And here is an example of a property that uses x-ms-dynamic-list:

 "TypeEn": {
      "description": "Company type identificator.",
      "type": "string",
      "uniqueItems": false,
      "x-ms-summary": "TypeEn",
      "x-ms-dynamic-list": {
          "operationId": "SearchEnumValues",
          "itemsPath": "Data",
          "itemValuePath": "ItemGUID",
          "itemTitlePath": "En",
          "parameters": {
              "requestBody/transmitObject": {
                  "value": {
                      "EnumType": "79a27ea8-067d-4616-ac48-1d68c800c131",
                      "IsVisible": true
                  }
              },
              "requestBody/includeForeignKeys": {
                  "value": false
              },
              "requestBody/includeRelations": {
                  "value": false
              }
          }
      }
  },

[troystaylor]

Do you have any custom code being used? I don't see any header being defined, which is what that response error in the dropdown is.
I would also suggest defining "transmitObject" with each parameter. You should removing the "default" response (you'll get the error regardless) and also change the 200 response to number 201 (POST is usually 201).

[ZeeCapp]

@troystaylor We don't use any custom code, however removing the "default" response from the /SearchEnumValues operation definition actually fixed the issue. 😅 Thanks for your support!