cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ericonline
Community Champion
Community Champion

CUSTOM CONNECTOR: Research and findings

Entering my 3rd day straight on a complex GET/POST nested JSON schema problem. Thought I'd share some interesting findings I've found:

  1. A schema that returns "Success" in the Custom Connector "Test" area, does not directly transfer to a Custom Connector POST function ( myCustomConnector.POST({<things:andStuff>}) ) in PowerApps.
    1. This really sucks and its largely due, I believe, to 2.

  2. When dealing with POST schemas, " [ ] " 's <> work. The Custom Connector function needs "Table({<your schema here>}). It will not "see into" square brackets. 
    1. You can interrogate the needed schema by substituting [ for Table(, hover over the red squiggly intellisense, and build the correct schema from this. (handy but suuuuper-hacky).

Hope this helps!

1 ACCEPTED SOLUTION

Accepted Solutions
v-yuxima-msft
Community Support
Community Support

Hi @ericonline ,

 

Thanks for your information.

This is very helpful.

 

Best Regards.

Yumia

View solution in original post

3 REPLIES 3
v-yuxima-msft
Community Support
Community Support

Hi @ericonline ,

 

Thanks for your information.

This is very helpful.

 

Best Regards.

Yumia

View solution in original post

ericonline
Community Champion
Community Champion

Adding on to this... kind of related. 

  • For a ClearCollect statement that does NOT use a Custom Connector-defined JSON schema, I'm UNABLE to use Table()!
  • I MUST use "[ ]" 's instead of Table()!
  • Weird.

Example:

  • Does not work:
  • ClearCollect(colSample,
        Table(
            {parameter: "test", paramValue: 123},
            {parameter: "toast", paramValue: 345},
            {parameter: "toots", paramValue: 567}
        )
    )
  • Does work:
  • ClearCollect(colSample,
        [
            {parameter: "test", paramValue: 123},
            {parameter: "toast", paramValue: 345},
            {parameter: "toots", paramValue: 567}
        ]
    )
    Hope this helps someone else too!

@ericonline 

 

I think this may have something to do with the fact that ability to add so-called 'tabular-capabilities' is absent in custom connectors.

 

See: https://powerusers.microsoft.com/t5/PowerApps-Ideas/Custom-API-with-tabular-capabilities/idi-p/13394

 

HTH,

Josh

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

Power Apps Community Call

Monthly Power Apps Community Call

Did you miss the call?? Check out the Power Apps Community Call here!

secondImage

Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Top Solution Authors
Top Kudoed Authors
Users online (59,079)