I've had this happen on 2 different occasions in this app I'm workin on where out of nowhere, part of it stops working saying that the Variable type is incompatible with the same variable used in other areas of the application. This is after the code had worked properly for a while. When I go to View Variables to see what's happening, it says Error under the variable name (both times this has happened it's been with Records. Closing Power Apps and restarting it doesn't do anything, it still shows error (even without having run the app). The only way to get it working again is to change all occurrences of that variable name to something different, which ends up removing the offender from the list of variables and all of a sudden, it starts working again, without having changed anything else other than the name.
Is there a better way to destroy a variable showing an Error than to remove all references to it and calling it something new? This most recent case wasn't too bad because it was only mentioned in one part of the app a few times, but the first time it happened was a major PITA. Is this a bug?
Hi @zuurg ,
It sounds definitely like you are using the same variable name with two different structures (number/text/record etc) in different places. Use your Search to find all the occurrences and see what type of variable you are setting in each.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Visit my blog Practical Power Apps
This is not a bug!
If you are seeing this often, then you are working with variables in a way that is not a good one!
PowerApps has to infer its schema for all record types in the app. To do this it has to look over every formula and determine how they all interact in order to establish the schema.
When you are doing things (potentially in your case) like : Set(someVar, Patch(someList, {someRecord})) it will infer its schema from somelist. If you then alter that in other places to change or add columns or types, then it gets confused...quickly!!
9 times out of 10, you can exit the designer and then go back in and it will re-infer the schema and it will be correct. This happens because, as you change formulas and potentially schemas, it re-infers the schema and does not forget it. This is also another reason why some people say..."I was working on designing the app just fine, then came back to it the next day and there were errors everywhere". This is because it was inferring the schema during design time the first time and some schema "stuck" and was good even though it was "stuck", but when re-opened, it re-inferred and that was no longer there and not "stuck" and then nothing else recognized it.
So, the moral of the story is - firstly avoid variables as much as possible and use only when really needed. Second, try to avoid creating your own schemas if the schema is based on a datasource. Let the datasource always be the "leader" to the schema.
Hopefully this is helpful for you.
That is helpful and the Set(SomeVar,Patch...) is exactly the context I'm using it in. In this case, it's only mentioned in a few places, and no changes have been made to the sharepoint list's structure. It actually just did it again, when I was adding in a SortByColumns at the beginning of the Gallery's Items property. When I select a record from the gallery then hit the line's edit button, it displays an Edit form in a popup. The places where the code broke was on the edit icon (the code is Set(vMyResourceRecord,ThisItem)) and in the popupscreen's Patch code (again, using the Set(vMyResourceRecord,Patch...)
1) Is it safer to just have the EditForm's item property set to Galleryname.Selected?
2) If I get rid of the variable and point to the Galleryname.Selected instead, how can I confirm the creation of the record? This is the code I'm using to verify it:
If(
Not(IsBlank(vMyResourceRecord)) And IsEmpty(Errors('Resources')),
Notify(
"Changes Saved!",
NotificationType.Success,
2000
),
Notify(
"Update Failed",
NotificationType.Error,
2000
)
);
Refresh('Resources')
Using the Form's SubmitForm() isn't an option here so I can't use the OnSuccess.
Well, I'm actually more zoned in on your last point - "Using the Form's SubmitForm() isn't an option here so I can't use the OnSuccess." Why is that?? If you have a form, you should always be using the SubmitForm() method.
For #1 - you can use the gallery.selected property, however, this can lead to issues. Your gallery will always re-evaluate its Items property whenever any changes occur to any part of it (i.e. datasource changes, a reference value changes, etc.) This will cause the gallery to reset to default. In most cases (unless you have a Default record set in it), it will revert to the first record in the gallery...and thus, your form will have the wrong record in it!
I would say that 90% of the time I lean toward using a variable for the record selected. i.e. Set(var, ThisItem) Variables are snapshots of data, and in this case, it is what you want. There are times it is not needed (if you know your gallery will not re-evaluate and reset).
For #2, get your SubmitForm to work and you will not have to worry about that and you will be able to confirm that it submitted by the form.
I'd love to be able to use the SubmitForm - especially in this case since the form is pretty simple. If it was an edit to the form, no problem. The area that I ran into issues with was when I was trying to add a new record - there is a required field in the SP List that I didn't want showing on the form (the Project ID). When editing, no problem because it's already there, just couldn't figure out how to get it to save for the new record. (I can get it from the underlying gallery's SP list's .Selected.'Project ID' (it's a different list than the one the form is submitting for).
I had the field marked as not visible (but the Default was populated with the previously mentioned gallery.Selected.'Project ID') and it would still not do it and tell me the field was required. If you have any tricks to handle that, it'll make my life much easier. 🙂
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