That doesn't throw any errors but it doesn't solve the problem either @LaurensM.
Here are two little screenshots:
In the first, I'm showing the field that I've been modifying to test with. Simply incrementing a number at the end of a text field.
The second image shows what I can look up in the variables area of PA when I stop the app immediately after the form loaded that generated the first image.


It went from 9 to 11 because I tested twice without clicking through the gallery on the main page which would have results in TEST10 being there instead of TEST9. But it shows what is happening. Even though PA understands and shows that the underlying record for surveyVal contains the updated value, it's not showing in the form when that page loads.
Now one more clue:
The Item property for DetailForm1 is surveyVal.
When I look at that variable I see two weird things:
1. It's showing as a Context Variable on DetailScreen1 and not a Global.
2. It shows the data for TEST9.
And one more piece of evidence:
The url I'm generating to get the user directly to the correct record on DetailsScreen1 results in no data displaying.
?surveyId=5 is embedded in the url. I thought my deep linking was broken because this link results in a blank page being loaded.
BUT, today for some odd reason, I clicked the Edit button on DetailsScreen1 and low and behold, I was navigated to EditScreen1 with the right record visible. So riddle me that batman.
I'm sure the problem is with the Item property on DetailsForm1 but how do you mess up 'surveyVal'?
So the routing to the correct record on the EditScreen1:EditForm1 is very likely because the Item property of EditForm1 is userSurveys.Selected.
So surveyVal is setting correctly on AppStart and then through the gallery on the BrowseScreen otherwise DetailsScreen1:DetailsForm1 wouldn't show the correct record and it is. The problem appears to be updating the surveyVal record.
If you've been reading, thanks for your patience. 😄