Global variable not recognised as a record

[Anonymous]

My app has two registration forms, each with their own data source - both SP lists. The first registration form is working fine and uses a global variable (varProjects) to save the data on each screen.

So on the home screen, the button which navigates to this form uses this formula:

Set(varProjects, Blank()). There is then a ClearCollect for the navigation menu component and varProjects is referenced under Status.

Status: varProjects.AboutComplete - where AboutComplete is a column in the actual data source.

The variable is referenced as Item on each form for this registation. On each save button, where the form is in edit mode, the formula is:

Patch (
ProjectRegister,
varProjects,
Form_About.Updates, {AboutComplete:true}.

This works absolutely fine. However, if I use another variable for my 2nd registration form with the same formulas, I get errors. So in the ClearCollect when I add: Status: varData.AboutComplete I get this error:

Incompatible type: the 'Status' column in the data source you're updating expects a boolean type and you're using a error type.

My patch on the save button has the following error:

The function 'Patch' has some invalid arguments. Invalid argument type (Boolean). Expecting a Record value instead.

It looks like varData is set to false, but I set it to Blank.

The item is set to varData. Why is it not recognising it as a record value?

[Anonymous]

Anyone able to help with this please? I've checked the Variables screen for it and it's set as Boolean with value 'true' yet there is nowhere where it has been defined as this as far as I can see. I've tried removing all mention of the variable and starting again with a new name and it still sets it as a boolean.

These are the two definitions of it: 

In the gallery: 

UpdateContext({conLoading: true});
Select(Parent);
Set(varYourData, DatasetsGallery.Selected;

Navigate('Dataset About')
;
UpdateContext({conLoading: false}))

On the button to open the form:

et(
varFormMode,
FormMode.New
); Set(varYourData, {}; ClearCollect(NavigationMenuData,{Title:"About",Image:maindetails,Status: true,Screen:'Dataset About'},{Title:"Data types & Categories",Image:maindetails,Status:true,Screen:'Data types and categories'},{Title:"Sharing & Outsourcing",Image:maindetails,Status:true,Screen:'Data Sharing Outsourcing'}, {Title:"Risk Mitigation",Image:maindetails,Status:true,Screen:'Data Risk Mitigation'}, {Title:"Access, Storage & Location",Image:maindetails,Status:true,Screen:'Data Access storage location'}, {Title:"Linked",Image:maindetails,Status:true, Screen:'Data Linked' }, {Title:"Retention, Archiving & Deletion",Image:maindetails,Status:true,Screen:'Data Retention Archiving'});

Navigate('Dataset About'))

[Anonymous · Accepted solution]

Issue resolved. I removed all reference to the variable, saved and published the app then started again. Seems to be working now.

[Anonymous]

This happened to me when I duplicated a PowerApp Screen and left all the variable names the same as the previous screen so the variable broke in the previous Screen. It wasn't recognizing it was of type record variable anymore it only said variable, so everything related to it broke. I tried to replace all of these variable names at once using the search and replace feature, but it didn't worked, but when i did it one by one it worked so that's how i solved it.

[DavidWahlroos]

Is there a fix for this? I have been fighting with this issue for some time.  MS needs to get this environment working well with all the emphasis they put on it.

[DavidWahlroos]

I have this kind of garbage happen very often. And I am using OOB submits and no special patch commands. 

I save my work for the day and everything is fine. Next day, I open the app and  the environment is not pleased.

I have multiple global variables, typically ones that represent a record, which have been previously defined and in use working just fine. Then, for NO REASON I can see I  get the typical vague errors

-expecting a record (when that is what it was) or

-this does not match another definition "somewhere else" in the application.

Really?

THERE IS NO WAY I should have to spend a minute, let alone sometimes hours tracking down this stuff, changing variables, etc. when it was all working last time I closed the App.

This is all a big pile of B.S. as far as the dev environment goes. The concept and usefulness has great potential, but the dev environment is WAY TO IMMATURE to have MS pushing this as a viable, reliable, maintainable solution.