This is a general question which I think I know the answer to but have seen inconsistent results.
In many of the SharePoint Power Apps that I build I load the SP data the user is editing into a variable:
Set( gblRequest, LookUp( 'Requests', ID = SharePointIntegration.SelectedListID ) );I then set the Forms Item property to this variable. Generally works well.
There are occasions where an action by the user will require me to update a property in that variable that is different than the one tied to the field the user is currently editing, maybe in an OnChange() event. This is how I have been doing that:
Set(
gblRequest,
Patch(
gblRequest,
{
Status: { Value: "Changed" }
}
)
);
This is a simple example, but should give you an idea of what I am doing.
So my question is, is this correct? Will this always have the expected outcome?
I have seen instances where I have a Drop Down that is tied to one property in the variable (gblRequest in this example). When the user changes the value of that drop down I need to force a reset on two other fields in the variable. I do that in the OnChange() for the drop down. What I see when that happens is the reset works, but the drop down value gets reset back to it's original value.
Not 100% sure what is going on here.
Anything to help solve this would be appreciated.
Thanks.

Report
All responses (
Answers (