Forum Discussion
MarkShnier__You
Qrew Champion
@Christopher Greene
The SaveBeforeNavigating syntax is known to fail i.e. (causing that pop up) if the only change to the record was In Grid Edit. I have found that it works reliably if the Parent record is changed. What I finally settled on which works perfectly is to make to helper fields on the form. One is called [Dirty the record] and the other one is called [Dirty the record plus 1]. The latter is a formula field obviously equal to
[Dirty the record] +1`
I then have a form rule set to fire all the time where if those two fields are not equal I change [Dirty the record] to be equal to the value in the field [dirty the record plus 1].
In your post above you are claiming that save before navigating fails even if both the parent and the child have been modified. In my experience that is not how it behaves. Try putting in that form rule and see if it solves the problem.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
The SaveBeforeNavigating syntax is known to fail i.e. (causing that pop up) if the only change to the record was In Grid Edit. I have found that it works reliably if the Parent record is changed. What I finally settled on which works perfectly is to make to helper fields on the form. One is called [Dirty the record] and the other one is called [Dirty the record plus 1]. The latter is a formula field obviously equal to
[Dirty the record] +1`
I then have a form rule set to fire all the time where if those two fields are not equal I change [Dirty the record] to be equal to the value in the field [dirty the record plus 1].
In your post above you are claiming that save before navigating fails even if both the parent and the child have been modified. In my experience that is not how it behaves. Try putting in that form rule and see if it solves the problem.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
ChristopherGre3
2 years agoQrew Trainee
.... But, if I click the table button or any other button, since those two helper fields are constantly changing, then I'll have to respond to the popup that warns of unsaved fields, specifically the two helper fields. The Save & Close button takes me out, but that is an option that I would hide from the end user with &ifv=1 in the query string. Anyway, I'm further along with the solution than I was yesterday.
Thanks again,
CGreene
------------------------------
Christopher Greene
------------------------------
Thanks again,
CGreene
------------------------------
Christopher Greene
------------------------------
- MarkShnier__You2 years agoQrew ChampionYes, I have no way to stop that pop up when you navigate away, as the record is now dirty. You would think because the table is set to auto save before navigating away that it would not do that though.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------- ChristopherGre32 years agoQrew TraineeYes, and I do have that set in the table properties. In fact I think tables default to that.
CGreene
------------------------------
Christopher Greene
------------------------------