Forum Discussion
What makes you think it 'appears to be kicking off'? Are you watching the pipeline on another screen and seeing it kick off when you make a selection? Or is it just a troubleshooting guess?
Are you using the manual field at any point in your pipeline (the field that the formula field is copied to when the record is saved)? If so, my guess is as soon as it is saved it looks at all the fields and uses them in the pipelines. Maybe it all happens so fast that the alternate field is still 'blank' for a split second - meaning that field is not being sent to the pipeline. Alternately, if your relationship is based off that alternate field (I am guessing it is a scalar field), the relationship doesnt exist until after the record is saved, so if your pipeline is dependent on the relationship, it may not exist yet. It may only exist a split second after the pipeline fires.
------------------------------
Mike Tamoush
------------------------------
- EmberKrumwied2 years agoQrew Captain
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
------------------------------