Custom Connector - error: array not supported in parameter

[GonzaloR]

I am new to coding, and I'm trying to follow the microsoft guides on creating custom connectors.

I am attempting to connect to the Wrike api v4 to use with flow, and I have hit a wall when trying to create a folder with "project" properties. According to wrike "Wrike's API does not recognize application/json or form-data format of the query" .

So when I create an action in the custom connector to create a folder, I've added the "project" properties as part of the query, since it's my understanding I can't add them to the body. When using this method I have tested the connector in flow and I have been able to create a folder with the folderid(parent folder) and title. But, no matter what I try I cannot get the project parameters to work!

I am populating the request from this sample:

/api/v4/folders/{folderId}/folders?&title=Testfolder&description=descriptionTest&project=[{"ownerIds":"KUGEYQ5H","status":"Red","startDate":"2019-07-31","endDate":"2019-08-07"}]&shareds=shareds

and powerapps identifies the project parameter as an array, when I update the connector I get this error message:

Your custom connector has been successfully updated, but there was an issue converting it to WADL for PowerApps: An error occured while converting OpenAPI file to WADL file. Error: 'Parameter with type='array' is not currently supported at JSON path paths./api/v4/folders/{folderId}/folders.post.parameters[3]'

When I test in flow, it doesn't show me the nested parameters, it just shows a "project" field input.

So I tried adding the project parameters with a compose action, but it doesn't recognize the input stand-alone json:

{
  "ownerIds": [
    "KUAFFXRP"
  ],
  "status": "Green",
  "startDate": "2020-08-06",
  "endDate": "2020-08-13"
}

And i tried or using encodeUri:

encodeUriComponent(outputs('Compose'))

When I peek at the code in flow, i noticed that the Project parameter values are inside "double quotes" and not nested parameters:

        "queries": {
            "title": "Wrike test 4",
            "project": "@{encodeUriComponent(outputs('Compose'))}"
        },

So, I'm stuck!

Is there a different way I can format my sample to make this work? Have I made some fundamental error somewhere along the way? 

[Anonymous]

Bumping for visibility 

@Anonymous 

[romanduda]

Hey Gonzalo,

we are also trying to get the Wrike API running by a custom connector within Power Automate. We are struggling to set the connector up correctly as it isn't generating the redirect URL after saving the the connector. Du you have any suggestions for us?

Thank you so much

Roman 

[GonzaloR]

Hi @romanduda 

I'm not sure I know the answer, I'd suggest double checking your inputs in the General tab and Security tab, I attached screenshots of mine here in case they help.

Obviously you'll need your own client id and refresh URL. I hope this helps!

[romanduda]

Hi @GonzaloR,

i tried exactly the same configuration on the Europe side. It didn’t worked on my side. So, you are able to connect to WRIKE an automate through POWER Automate?! 

thanks for your time. 
Roman

[Anonymous]

Hi!

I'm having the same issue here! I'd like to know if there was any update on this matter.

Thanks!

[romanduda]

Finally we got it running. You need to make sure, that you use the right URLs. Are you hosted on US or European Server?

[Anonymous]

Hi romanduda!

Thank you for you attention! Actually, I asked about the error "array not supported in parameter" which GonzaloR brought, but I am not trying to connect with Wrike as you both did, but with UpMiner (documentation here).

In my case, I wanted to create a custom connector with an OpenAPI 2 file, but this message was shown:

An error occured while converting OpenAPI file to WADL file. Error: 'Parameter with type='array' is not currently supported at JSON path paths['/{token}/lote/duplicidade'].get.parameters[1]'

I also tried with an OpenAPI 1 file, and I succeeded to create the custom connector. But, as GonzaloR, the connector didn't show me the paremeters.

Can you help me with this situation?

[GonzaloR · Accepted solution]

Hi @Anonymous ,

I found a way around it:

Here are a few screenshots

1. of the request

2. The parameter settings for the "project" query, note the default text - this works for me because there are relativeley few fields here.

3.  The  action in power automate, I replace the default text as necessary

I hope this helps!