some variable and collections have been reset

[Anonymous]

Hi everyone,

I'm getting multiple errors in my app after 2 days of not touching it. The only change that was made was a view change in the SharePoint list which I'm pretty sure shouldn't have affected it? I saw another post regarding this issue but my issue appears to be different. I have multiple versions of this app and they are all affected despite no changes being made to them in the last couple days.

https://powerusers.microsoft.com/t5/Building-Power-Apps/some-variables-and-collections-have-been-res...

[PeterCBell_au]

As above, many hours wasted. Renaming variables didnt work.

Illogical but what worked was;

 multiple set statements of the form Set(vABC,vDEF) alleged a and b were incompatible types

 When used editor to delete vABC and then retyped it with autocomplete --> fixed errors.

[Catmarch1]

can someone from microsoft advise what's going on here?  like another poster, i made a copy of a screen that referenced the problem variable.  however, i've put a lot of work into that new screen and it seems stupid to have to make another copy of the app and redo that screen.  I don't want to put in a lot of hours (unpaid) to remake the suspected trouble screen and find out that's not the problem.  This variable that suddenly doesn't work anymore is used throughout the app, literally on every screen and in a lot of code; ie if this variable doesn't work, i can't even test what's going on; i can't even assign a specific value to the variable.

This variable points to an ID field in a sharepoint list, so the sharepoint data isn't the problem, it's an ID field, so there's no way the attributes of that field have changed. 

this is extremely frustrating.

[powerUser1611]

@Catmarch1 

The error is saying that there is a mismatch between your data source (SharePoint list) and the variable's definition. Without knowing more about your specific case, it is hard to know exactly what it could be, but I would try deleting your data source and re-adding it (your code won't be affected by this) or using the find/replace feature to rename your variable (I have had instances where renaming the variable actually fixed the issue, as silly as it sounds). If you want to make a new post about your problem, feel free to tag me in it and I will try my best to help. 

[Justin6]

I had this issue pop up to challenge me out of the blue this morning.

Still don't know the root cause really, but found many of my references to some of my variables (not all of course.... that might make it too obvious a problem!) to have a different property defined than what it used to.

For example

VAR_EXAMPLE.SITE_CODE
Throughout the app (including in custom components) had become
VAR_EXAMPLE.'data-ABC4D9B773E622A78EBA3F884C399C2CSITE_CODE'

This applied to a bunch of other variables and luckily for me the damage was fairly limited.  So I was able to use the find and replace tools to pick through and re-build all the references... again taking care to check in the custom components (Where the 'find' was not locating them).

Anyway, thought this might help someone else with this issue as well.

[rizkihidayat]

I experienced the same thing, until now I don't know how to avoid errors.

but I found a solution for a moment: create and connect to a dummy database, then when editing and getting an error, click skip then remove the dummy database and add it again, then the error will disappear.

I hope this helps.

[Rick_Terminal]

This problem can possibly be caused by any minor syntax error in the "OnStart" property of application.

I used ChatGPT to locate a syntax that appeared in one of a hundred or so Set commands that preceded the OnStart Collections build.  A close parenthesis 'went missing', meaning further down the code no OnStart collections could be set.

Hopefully this helps someone under the right circumstances.

[tinbantan]

Thank you. Your solution help me to fix problem. Retype Variable name that don't coppy and paste name 😍

[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.

[Monish_Kawale]

Please remove all the data sources and re add them. It will resolve this error

[Pedro_Henrique]

I don't know if my case it's the same as yours but I'll try what you did, thanks for the advice!