Save a record then revert it
Please bear with me as I try to explain the scenario. I'm looking for a couple things out of this: 1- Is the method I'm trying to implement the best way to do this, or is there a better one 2- I'm t...
Forum Discussion
What is the ultimate goal?
One user inputs what they want new values to be for a certain number of fields, but those new values do not populate until another user 'approves' the changes?
------------------------------
Mike Tamoush
------------------------------
One user inputs what they want new values to be for a certain number of fields, but those new values do not populate until another user 'approves' the changes?
------------------------------
Mike Tamoush
------------------------------
That's correct Mike.
This would be in lieu of our staff having to retype in all the information in a record to send as a notification, our staff would instead just make the change, and save the record to send to the end user. Meanwhile the record would revert back to its original values, and would get written permanently only when the user approves it via their email button. (i.e: it would then be updated with their own Quickbase user, for auditing purposes)
With that said, I think I got it resolved. I will do some more testing, but, in case someone else might have a similar scenario.
What I did is I removed the second (Revert) part of the formula, and I created a Pipeline to trigger on the record if the field "Staging" is checked, (and if the modified date is within 5 minutes, for good measure)
Then I used the values in there to get the previous value {{a.$prev.First Name}} , etc...
This seems to have worked like a charm!
Thanks!
------------------------------
George Khairallah
CTO
gotomyerp, LLC
------------------------------
This would be in lieu of our staff having to retype in all the information in a record to send as a notification, our staff would instead just make the change, and save the record to send to the end user. Meanwhile the record would revert back to its original values, and would get written permanently only when the user approves it via their email button. (i.e: it would then be updated with their own Quickbase user, for auditing purposes)
With that said, I think I got it resolved. I will do some more testing, but, in case someone else might have a similar scenario.
What I did is I removed the second (Revert) part of the formula, and I created a Pipeline to trigger on the record if the field "Staging" is checked, (and if the modified date is within 5 minutes, for good measure)
Then I used the values in there to get the previous value {{a.$prev.First Name}} , etc...
This seems to have worked like a charm!
Thanks!
------------------------------
George Khairallah
CTO
gotomyerp, LLC
------------------------------