So... this one kind of hurts. I hope I'm doing something wrong.
I hope I'm just doing something incorrectly because, the result of this, is that I need a Custom Connector FOR EACH GET REQUEST! Even though its the same URL just additional parameters tacked on.
The result is that my Users must authenticate to 4 (yep, one for POST too) Custom Connectors the first time they use the app. NOT FUN.
Does anyone else have a solution for this? Maybe something to do with base URL ?
HI @ericonline ,
Why do you add one operation for each of your three Requests (that you mentioned) within your custom connector?
Based on the needs that you mentioned, I think it is not necessary to add one operation for each of your three Requests (that you mentioned) within your custom connector.
On your side, you just need to add single one operation for your third Request (https://mycompany.com/api?param1=yadda¶m2=yah¶m3=yougetit) within your custom connector, then eidt these Query parameters and set the Visibility property of theses Query Parameters (param1, param2 and param3) as advanced:
then when you call your custom connector actions within your app, you could specify these query parameters optionally rather than mandatory.
The reason why @ericonline needs 3 Get operations is because depending on the arguments that he passes to his API, the schema that the API returns will be different. Unless I misunderstand you, how would you configure the 'response' part of a single operation to support multiple schemas?
@v-xida-msft , Thank you for the advice.
At first, I did try adding a single custom connector with all three parameters at first. I did not try setting the parameters to "advanced". (Thats a cool tip to know!)
The question is, which of the 3 schemas do I paste into the Response example? Each is different based on the parameters sent.
I've just been watching Mark Wood's Zapier talk at the 'PowerApps Virtual Summit' (it was a great talk!).
Although I've not used this, it seems that it might be possible to 'proxy' your 3 calls via a single custom connectiont to Zapier. Perhaps this might be worth investigating?
Thanks for the idea @timl .
My org is pretty "3rd party averse". Its challenging as is to get PowerPlatform sanctioning!
I'm wondering if there is a way to architect JSON responses to make them more "Custom Connector/PowerApps friendly".
Some ideas you, I and others have already learned:
I'd REALLY LOVE to hear from someone on the PowerApps team on that.
PS: Zapier has a killer remote working blog too.
I think what you need to try is using the x-ms-dynamic-schema vendor extension in your swagger.
It's not fun or easy and there are zero samples of using this in PowerApps but I believe the only way to get PA to fetch the schema dynamically.
Also, good luck getting a team member to chime in on custom connectors.
Lastly, FWIW, There is supposted to be new and improved guidance docs on Custom Connectors being resleased in the the 'April 19 release' timeframe, but I haven't found anything yet - prolly still forthcoming.
Check out new user group experience and if you are a leader please create your group
Did you miss the call?? Check out the Power Apps Community Call here!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.