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
Solved! Go to Solution.
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:
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
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:
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
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
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.
Thanks, simple but effective.
Do you have an example? I quite don't understand your solution, but I have the same problem.
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
Hi, Gary, how do you change the NULL value to something else when querying an API? The API team believes null is the correct value to pass into json.
Hi
As long as you have defined the field type in Flow as per my earlier example you can pass NULLs without problem - I have various text and numeric fields that pass NULLs quite happily (now the field type is defined).
Alternatively, if you want/need to change a NULL value the easiest way is to use a stored proceedure and get the flow to call that instead of the table. I have a number of numeric fields that default to NULL if nothing is entered that cause havoc with the formulas. I use "ISNULL(field_name, replacement_value)" in the stored proceedure SQL Query.
As a general rule, I use stored proceedures to carry out the heavy lifting e.g. joining tables, swapping indexes for values, carrying out calculations, etc. Generally much quicker and easier to check and revise - you can also use the stored proceedures in both PowerApps and PowerBI, very useful when running reports.
Hope this helps.
If null is not the issue, any chance you could help identify the issue with this schema? Test flow ran fine with correct response results, but PowerApps gives Registering error.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages