Forum Discussion

EmberKrumwied's avatar
EmberKrumwied
Qrew Captain
3 years ago
Solved

Formula Field and Pipeline Issue

Me again...: ) I have a formula field that combines the selections in 2 different fields.  The result of which is copied to another field when the form/record is saved.  (This is to create a relati...
  • EmberKrumwied's avatar
    EmberKrumwied
    3 years ago

    After some more testing I have realized that the field the formula is looking to does not get populated until the record is saved (thus the "0" value).  This in turn causes the form rule save feature to copy the wrong value.  Thus, the pipeline kicks off and creates a new record but uses the wrong value.  So I changed the formula to pull the needed information from a different field and it all appears to be working as expected.



    ------------------------------
    Ember
    ------------------------------
MarkShnier__You's avatar
MarkShnier__You
Icon for Qrew Legend rankQrew Legend
3 years ago

Wow, this is surprising.  For sure a Pipeline does not start until the record is actually saved.  It's hard to believe that the combined field is not populated when the record first saves as it only saves once, and presumably, you are saying that it saves correctly.

I have two thoughts. One is that instead of triggering when the record is saved, trigger the rule when the formula field is not equal to the data entry field and deselect the check box at the bottom of the form rule so that the rule fires all the time.

The other thought really should not be necessary,  because its hard to believe that the record is not being saved correctly, but the Pipeline could trigger and then it could have a step to lookup the trigger record and then have an Conditional Branch to create the parent if needed. That would delay the actual Pipeline to pull the record details.



------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------