PowerApp Clear Form.LastSubmit record variable

[BDOJoe]

I have a PowerApp that consists of multiple forms that together create or edit a record on a sharepoint list. The flow currently is

Form1 -> Save -> SubmitForm(Form1);Set(currentGrievanceForm,Form1.LastSubmit); -> Navigate to Form2

Where each form section has the 'Item' property set to currentGrievanceForm so that the current record is passed between forms in the case that the user is editing an existing record, or viewing a read-only version of the record. The issue that I'm running into is that when I edit a record and then go back and create a new one, the currentGrievanceForm value isn't cleared out so the new record is using the Id of an already saved sharepoint list item. Is there any way to clear out the "currentGrievanceForm" from the main menu of my application when the "New" button is clicked? I've already tried Set(currentGrievanceForm, blank());, but that didn't work. Any thoughts?

[BDOJoe]

It's showing an Id of '73'. Maybe I'm not setting/Clearing the variable correctly? I see that Globally and in View1, I have a currentGrievanceForm variable, and then within each of those, I see that the value is defined multiple times in different areas using Set(). Is it possible I should be using something other than Set?

[RandyHayes]

@BDOJoe 

This is where I was trying to go...do you have this variable defined in another way?  You say that you see it in View1 - what is View1?

The question is (beside the above) have you done an UpdateContext({currentGrievanceForm.. somewhere?

[BDOJoe]

In all scenarios where I want to update the currentGrievanceForm, I've been using Set(). Should I only be using set once, and then UpdateContext in all other situations?

[RandyHayes]

@BDOJoe 

No, you should only be using set.  Set sets global variables.  UpdateContext sets context (screen) variables.  If you make a context variable with the same name as the global variable, then when you reference the variable on the screen where you defined the context variable, it will prefer the context over the global.

So, still, tell me more about what you mean by View 1.  You said you saw this in View 1.  What does that mean?  Screenshot??

[BDOJoe]

Here are the variables. GrievanceForm_PatientStatement is the name of the screen that holds Form1

[RandyHayes]

@BDOJoe 

Yep, here's the issue.  You have conflicting variables.

Click on the variable in the screen list and look to see where it is defined (under definitions)

[BDOJoe]

It's being defined multiple places globally. Would you expect the variable to only be defined once? I.e. only defined globally and not defined inside the GrievanceForm_PatientStatement screen.

[RandyHayes · Accepted solution]

@BDOJoe 

Global is fine.  The problem is you showed me a photo with it defined in a screen.

Global variables will not show in a screen like that...they are context variables.

As mentioned you need to click on the GrievanceForm_PatientStatement screen in your variable list, then click on the currentGrievanceForm variable and look at its definitions.  Not the global.

[BDOJoe]

You were absolutely right! I was incorrectly setting the currentGrievanceForm value on the Gallery which was causing the conflict. Now, when going between edits and creating a new form it *looks* like everything is working as expected. I'll continue to test and see if the issue is completely resolved.

[RandyHayes]

@BDOJoe 

Yes, a context variable will override a global on the screen it is defined on.  They are two separate variables with the same name.