Forum Discussion
MarkShnier__You
Qrew Champion
No, you make a regular user field called
[Last Modified by before Pipeline]
Then have the Pipeline populate it. but I realize now that would need to be the first step of the pipeline or at least a step before the pipeline modifies the record. Also we do not yet have the ability to insert Pipeline steps so you may need to rebuild your Pipeline.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
[Last Modified by before Pipeline]
Then have the Pipeline populate it. but I realize now that would need to be the first step of the pipeline or at least a step before the pipeline modifies the record. Also we do not yet have the ability to insert Pipeline steps so you may need to rebuild your Pipeline.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
AshleySolomon
7 months agoQrew Trainee
Hey Mark,
I thought this solution would work for a workflow that I am trying to solve for with a PL.
"Last Modified By" shows up as an option to Trigger Step A off of, but not as an option for Subsequent Steps. Thoughts? Is this a bug possibly?
Ashley
------------------------------
Ashley Solomon
------------------------------
- MarkShnier__You7 months agoQrew Champion
My suggested solution was to make a new field of type User, and not try to change the built in field.
if you specify your new field that you created as part of the trigger step in the place for fields to be used in subsequent steps, then it should be offered further down the pipeline as a choice to populate.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------