@tommyly, I'm thinking you need to clear the globalVarID variable when you're done on the screen. This cleans things up.
Also, instead of using a condition to tell the form whether to be in edit or new mode, you can just do it straight from the edit and add buttons on the previous screen. It saves you guess work and conditions.
That seems to be more consistent: using EditForm or NewForm from the previous screen. Thanks!
I'm guessing the problem I had may have had to do with a discrepancy in the order in which events trigger versus when forms update. My initial instinct is that everything happens chronologically, but there may be some unexpected timing that cased the form to update out-of-step when altering it (e.g. EditForm/NewForm) in an OnVisible event.
Anyway, I will start using EditForm and NewForm from the invoking screen rather then rely on an if-statement within an OnVisible event.
You said that syntax was the problem, can you please write the code for me, cause I'm havin the same problem!!
Thnak you very much
The syntax solution metioned earlier is probably specific to the other user's app/rules. It would be best if you create a new topic and post details specific to your issue so we can help. If there is a specific action that doesn't work in Play mode, then providing the rules for that action would be a good start.
@AllenKim, I am having a similar issue the past couple days, which I have posted about here: https://powerusers.microsoft.com/t5/General-Discussion/Bug-date-field-not-getting-saved-in-play-mode...
When I turn off the "Delayed Load" setting, it seems to be fixed. Could this be a bug?
Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.
Continue your learning in our online communities.
Features releasing from October 2019 through March 2020
Coming to a city near you
Fill out a quick form to claim your user group badge now!
Connect, share, and learn with your peers year-round