some variables and collections have been reset

[gjeh]

Hello All,

Over the past months I have worked on creating an App in PowerApps. However today I wanted to check back in and see if there are any design features I'd like to improve so I logged in to editor mode and found myself with this error:

It doesn't matter if I select 'Save and reload' or 'Skip' - both buttons in actuality don't do a single thing for me. they just remove the pop-up and leave me with an error ridden application. As you can see in the image above I've marked yellow several comma's (` , `).

Why these comma's suddenly appeared I have no clue, however they should be semi-colons (` ; `) between arguments and double semi-colon between functions   [example:   Set(var;true) ;; Set(othervar;false)  ]. this is how I originally wrote everything because I'm working under the European language template.

What am I to do? It obviously isn't a choice to just accept it and spend days of work fixing all the errors if it can get F'd like this at any random moment anyway..

What caused this error? how do i prevent it from happening, and how do I revert everything without deleting work.

To sum up:

1 this came out of nowhere after not editing the app for several days.

2 semicolons (;) have been changed to commas (,) as if the language template were suddenly different

3 Both options in the pop-up window don't do a single thing.

4 I've already set back an older version of the app, obviously without result otherwise this post wouldn't be here aswel as that the problem appeared out of nowhere so it also just apppeared out of nowhere on an older version.

[Nico0405]

I experienced the same Problem for a while now and was just ignoring it. Everything worked just fine, just the warning was a little annoying.

In my case the problem was that one variable stored a number which came from diffrent datasources. Even though the datatype was the same from all datasources this was the reason of the problem. My solution was to call the Value() function for everything i was storing in the variable. Now I don`t have warnigs anymore.

[TimRd2]

I had the same problem where it complained about a variable that was set as a number, either 0 or ThisItem.ID.  I wrapped all the Set(variable,ThisItem.ID) in Value() and it quit complaining.  Set(variable,Value(ThisItem.ID));
Hope this helps someone.