creating a pipeline
Hello, I've followed the various tutorials for creating pipelines, but none seem to fit my needed scenario. I need a record to move to another table if a field contains a certain selection, an...
Forum Discussion
Hi Lorrie,
You will need to different Pipelines, but they will be basically mirror images of each other.
You will want to start with a On New Event Trigger, and set it up for when the status changes to Closed/Open depending on the table that is triggering the event. You'll want to select all of the fields that you're going to need to transfer.
Then you use a Create Record, and then drag and drop the fields from step A into the corresponding fields in Step B.
Then you use a Delete Record, and select the record from Step A(Trigger).
I hope that this helps
------------------------------
John Crosland
------------------------------
You will need to different Pipelines, but they will be basically mirror images of each other.
You will want to start with a On New Event Trigger, and set it up for when the status changes to Closed/Open depending on the table that is triggering the event. You'll want to select all of the fields that you're going to need to transfer.
Then you use a Create Record, and then drag and drop the fields from step A into the corresponding fields in Step B.
Then you use a Delete Record, and select the record from Step A(Trigger).
I hope that this helps
------------------------------
John Crosland
------------------------------
Hi John,
Thanks for replying, I've figured out what you have mentioned so far - now the issue is the fields that have a relationship don't move with the record because I can add them to the specified field group. It only shows the add button label and not the field.
------------------------------
Lorrie B
------------------------------
Thanks for replying, I've figured out what you have mentioned so far - now the issue is the fields that have a relationship don't move with the record because I can add them to the specified field group. It only shows the add button label and not the field.
------------------------------
Lorrie B
------------------------------
- MarkShnier__You
Qrew Legend
@Lorrie B Did you specify in the trigger record step that you will need to use those fields later on down the pipeline?
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------- Hi Mark, that's the problem, the fields don't populate for me to select; only the add record button field does, but none of the related fields populate with the other field options.
------------------------------
Lorrie B
------------------------------- Hi Lorrie,
The design you describe is Table A (Open Records) and Table B (Closed Records), with the same fields and relationships set up.
You seem to be saying that there is a relationship between Table A and Table B, because you say that there is an Add Record Button Field available to you. If this is the case, then you won't want to delete the record because then the relationship would be lost.
A simpler solution to your problem would be as Mark originally suggested. Create Reports and Permissions based upon the Status of Open and Closed, and then you won't need to duplicate and remove data from a table.
I wish you the best of luck!
John
------------------------------
John Crosland
------------------------------
