cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
johnmarlowe
Level: Powered On

Registering Error when trying to add a flow

Hi 

I'm trying to add a flow into Powerapps and I keep getting a "Registering Error" Message.

When nI try running the flow outside of powerapps, it executes as succesfully and as expected, however I'm frustrated that I keep getting this message when trying to add it in to Powerapps.

 

Has anyone come accross this and knows why this happens?

 

Thanks

Andrew

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support Team
Community Support Team

Re: Registering Error when trying to add a flow

Hi @johnmarlowe,

 

Could you please share a bit more about the error message within your app?

Do you mean that you faced this issue when you added a flow into your app?

 

I have made a test on my side and don't have the issue that you mentioned. The user @mokhawaja has faced same issue with you, please check the response within the following thread:

https://powerusers.microsoft.com/t5/General-Discussion/Error-on-adding-a-flow-run-SQL-query-to-power...

 

If you added a "Request - Response" action (use it to return data to your app) within your flow. please check if you have typed proper JSON schema format within the "Request - Response" action. In other words, please check if there are some columns which did not have its type defined within the JSON schema.

 

In addition, please take a try to re-create your flow and then register it within your app again , check if the issue is solved.

 

Best regards,

Kris

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

6 REPLIES 6
Community Support Team
Community Support Team

Re: Registering Error when trying to add a flow

Hi @johnmarlowe,

 

Could you please share a bit more about the error message within your app?

Do you mean that you faced this issue when you added a flow into your app?

 

I have made a test on my side and don't have the issue that you mentioned. The user @mokhawaja has faced same issue with you, please check the response within the following thread:

https://powerusers.microsoft.com/t5/General-Discussion/Error-on-adding-a-flow-run-SQL-query-to-power...

 

If you added a "Request - Response" action (use it to return data to your app) within your flow. please check if you have typed proper JSON schema format within the "Request - Response" action. In other words, please check if there are some columns which did not have its type defined within the JSON schema.

 

In addition, please take a try to re-create your flow and then register it within your app again , check if the issue is solved.

 

Best regards,

Kris

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

johnmarlowe
Level: Powered On

Re: Registering Error when trying to add a flow

Many thanks - I'd used the sample payload to create the schema but had neglected to check that all the data types were declared, as per your suggestion. Having done this now it appears to be working and has solved the issue.

 

Thank you

Andrew

Highlighted
tommysantos141
Level: Power Up

Re: Registering Error when trying to add a flow

In case this helps anyone, I just had that issue pulling data form an external system. I combed through the JSON output field by field and when I use the "Use sample payload to generate schema" option and paste in a sample, the resulting schema doesn't like NULL data values. I made all of those "" and PowerApps took it.

GaryEden
Level: Powered On

Re: Registering Error when trying to add a flow

Thanks, simple but effective.

 

Jef
Level: Powered On

Re: Registering Error when trying to add a flow

Do you have an example? I quite don't understand your solution, but I have the same problem.

GaryEden
Level: Powered On

Re: Registering Error when trying to add a flow

Hi, this is how I understood it...

This would register an error...

 

[

      {

        "Id": 29,

        "AccountName": "Account 1",

        "AccountStatus": "Draft",

        "BusinessUnit": null,

        "SFID": "0015E00000mnnnAQAQ",

        "CustID": 1235,

        "Comments": "some text"

      },

      {

        "Id": 30,

        "AccountName": "Account 2",

        "AccountStatus": "Draft",

        "BusinessUnit": null,

        "SFID": "0015E00000mnnmgQAA",

        "CustID": 4563,

        "Comments": "Lorem ipsum dolor sit amet, consectetur adipiscing "

      }
]

 

In the above example, the "Business Unit" field is null in both records. As I understand it Flow doesn't have anything to make a decision on what type of value would be held in the field and throws an error.

 

However, if you pass an empty string or a value Flow can work it out.

 

This works (as the "Business Unit" field is now an empty string (although this would then hold numbers as text in this case))...

[

      {

        "Id": 29,

        "AccountName": "Account 1",

        "AccountStatus": "Draft",

        "BusinessUnit": "",

        "SFID": "0015E00000mnnnAQAQ",

        "CustID": 1235,

        "Comments": "some text"

      },

      {

        "Id": 30,

        "AccountName": "Account 2",

        "AccountStatus": "Draft",

        "BusinessUnit": "",

        "SFID": "0015E00000mnnmgQAA",

        "CustID": 4563,

        "Comments": "Lorem ipsum dolor sit amet, consectetur adipiscing "

      }
]

 

This also works (as there is a value in at least one of the "Busines Unit" fields)...

[

      {

        "Id": 29,

        "AccountName": "Account 1",

        "AccountStatus": "Draft",

        "BusinessUnit": "Management",

        "SFID": "0015E00000mnnnAQAQ",

        "CustID": 1235,

        "Comments": "some text"

      },

      {

        "Id": 30,

        "AccountName": "Account 2",

        "AccountStatus": "Draft",

        "BusinessUnit": null,

        "SFID": "0015E00000mnnmgQAA",

        "CustID": 4563,

        "Comments": "Lorem ipsum dolor sit amet, consectetur adipiscing "

      }
]

 

The other 'trick' I've learnt is to make sure that you have a representative sample to work from, around 10 to 20 records should be okay and ideally, make sure that every cloumn has the correct type of data in it to start with - then you don't get the error in the first place 🙂

 

Cheers

 

 

 

 

 

 

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

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

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

Top Kudoed Authors (Last 30 Days)
Users online (5,678)