cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
SamWinter
Level: Power Up

Collect(Sammlung2;myconnec... rest api custom connector returns ONLY "TRUE" VALUES

Hello

i did a custom connector and tested it with a manual trigger. I successfuly got all the data i need. Now i need all this data in my powerapp i created a button with this code:

"Collect(Sammlung2;myconnectorname.getprospectcount("mytoken")) "

 

it works without errors but the problem is i am only getting "TURE" values as result in my Collection "Sammlung2" and not for example the expected values like prospect count  40 or more complex data structures from other api requests like prospect name,address. Every request(getprospectcount or getprostepcts ...) goes through but every time my collection is getting filled with just TUREs strings

 

the datastructure looks like this  i think the problem is that it always start with "result" array ?:

{ "result": [ { "id": "string", "version": "string", "a ....

"https://www.weclapp.com/api2/#/"

1 ACCEPTED SOLUTION

Accepted Solutions
Super User
Super User

Re: Collect(Sammlung2;myconnec... rest api custom connector returns ONLY "TRUE" VALUES

HI @SamWinter 

 

To resolve this please update the 'getprospectcount' action in the Definitions in your custom connectors, you need to add a response sample into the default 200 response body, once you updates the response body, recreate the connection of this connector in your app and this will work as per your expectations.
MicrosoftTeams-image (162).png

 

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

1 REPLY 1
Super User
Super User

Re: Collect(Sammlung2;myconnec... rest api custom connector returns ONLY "TRUE" VALUES

HI @SamWinter 

 

To resolve this please update the 'getprospectcount' action in the Definitions in your custom connectors, you need to add a response sample into the default 200 response body, once you updates the response body, recreate the connection of this connector in your app and this will work as per your expectations.
MicrosoftTeams-image (162).png

 

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

Follow PowerApps on Twitter

Stay Up-to-Date by following PowerApps on Twitter

Top Community Contributors for July 2019

Top Community Contributors for July 2019

Let's thank our top community contributors

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

FifthImage

Dynamics 365 and Power Platform April 2019 Release notes

Features releasing from April 2019 through September 2019!

Users Online
Currently online: 36 members 4,353 guests
Please welcome our newest community members: