Automatically create a Power App from a REST API throwing errors

(0) Share

Report

Posted on by Aedu

107

Hi all

Today I found this article Automatically create a Power App from a REST API | Microsoft Power Apps explaining new pac create feature. As mentioned in the article above we should give feedback here. So here it is.

Trying that new feature with a custom connector we use already in apps and flows throws the following errors (For data protection reasons, I have anonymized the paths and operations):

Warning AG2004: Warning encountered when generating controls for /<stripped>/{id}/<stripped>/callback/ path and AnalyzeInputsCallback operation. Details: Generating control(s) for Body parameter inputs of type array of object is not supported
Warning AG2004: Warning encountered when generating controls for /<stripped>/{id}/<stripped>/callback/ path and AnalyzeInputsCallback operation. Details: No valid value was generated for Body parameter inputs of type array
Warning AG2004: Warning encountered when generating controls for /<stripped>/{id}/<stripped>/callback/ path and AnalyzeInputsCallback operation. Details: Body parameter inputs of type array is an invalid operation call parameter since its value is either invalid or empty
Warning AG2004: Warning encountered when generating controls for /<stripped>/{id}/<stripped>/callback/ path and AnalyzeInputsCallback operation. Details: Formula to call or execute the operation is empty
Warning AG2004: Warning encountered when generating controls for /<stripped>/{id}/<stripped>/callback/ path and AnalyzeInputs operation. Details: Generating control(s) for Body parameter inputs of type array of object is not supported

Warning AG2004: Warning encountered when generating controls for /<stripped> path and <AOperationName> operation. Details: Generating control(s) for Body parameter metadata.agps[*] of type array of object is not supported
Warning AG2004: Warning encountered when generating controls for /<stripped> path and <AOperationName> operation. Details: No valid value was generated for Body parameter metadata.agps[*] of type array
Warning AG2004: Warning encountered when generating controls for /<stripped> path and <AOperationName> operation. Details: No valid value was generated for Body parameter metadata of type object
Warning AG2004: Warning encountered when generating controls for /<APath> path and <AOperationName> operation. Details: Body parameter metadata of type object is an invalid operation call parameter since its value is either invalid or empty
Microsoft PowerPlatform CLI
Version: 1.17.5+gcbb58e8

I think the new command is not fully developed yet, isn't it?

All responses (3)

Answers (1)

ChrisBal-MSFT Microsoft Employee on at

Like (0)

Report
Re: Automatically create a Power App from a REST API throwing errors

Hi @Aedu - it's not expected that you wouldn't get an .msapp generated if there are no errors and only warnings. We'd like to investigate further. Could you please send me a private message with the following info?:

A screenshot of the command you ran and the full console output
If able, the .swagger.json definition of the custom connector. You can redact/anonymize anything you need to from there but we'd like to see the types/definitions of the actions to make sure we're doing the right thing. You can get this by browsing to the custom connector in the Dataverse tab and clicking the Download button as shown here:
Aedu 107 on at

Like (0)

Report

Re: Automatically create a Power App from a REST API throwing errors

Hi
Thank you for answering.
No, it didn't generate anything.
Verified answer

ChrisBal-MSFT Microsoft Employee on at

Like (1)

Report

Re: Automatically create a Power App from a REST API throwing errors

Hello, thanks for writing in about this. There are certain cases where the command will generate warnings such as the ones you've seen here. There are all warnings, and not errors - so I would expect that it would still generate a .msapp file.

There are certain types of connector inputs and outputs that the 'canvas create' command doesn't currently support either because there is no suitable equivalent control in canvas apps, or because it's ambiguous or complex to render. These warnings indicate that one of these types is defined in the connector, and was skipped while generating the app.

More information about some of these limitations is here: https://docs.microsoft.com/en-us/power-platform/developer/cli/reference/canvas#remarks

This is something we hope to improve as we evolve the feature - your thoughts on what is critical to support and how important you feel it is will help us prioritize, so please send along feedback.