Forum Discussion
QuickBaseJunkie
3 years agoQrew Captain
@Aaron Alpert
I don't believe there is a direct way to access the trigger information, but something like this would work (even if it's not pretty)...
Say the possible triggers are fid 6 "Status", fid 7 "Start Date", and fid 8 "Related Project".
If the pipeline was triggered by a change in the Start Date and the Related Project, the result would be 7, 8.
Let me know if this was helpful 👍
-Sharon
------------------------------
Quick Base Junkie
------------------------------
I don't believe there is a direct way to access the trigger information, but something like this would work (even if it's not pretty)...
Say the possible triggers are fid 6 "Status", fid 7 "Start Date", and fid 8 "Related Project".
{% set s = '6' if a.status != a.$prev.status %}
{% set d = '7' if a.start != a.$prev.start %}
{% set p = '8' if a.related_project != a.$prev.related_project %}
{{([s,d,p]|select("defined"))|list|join(', ')}}
If the pipeline was triggered by a change in the Start Date and the Related Project, the result would be 7, 8.
Let me know if this was helpful 👍
-Sharon
------------------------------
Quick Base Junkie
------------------------------
- BrittanyScheid5 months agoQrew Cadet
Related question, QuickBaseJunkie , where are you storing that variable in the pipeline? Are you putting that into a field on the table, or is there a way to store a variable just for use within the pipeline? And then follow up question, when using an "On New Event" trigger, is there a way to see if it was an add record or modify record that triggered the pipeline? Thanks!