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 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
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
------------------------------
------------------------------
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
------------------------------- I wish I could just use the reports but I have an ID field that needs to be unique in the table and allow new records coming in to have that same ID - which is why I need the record to remove from that table to allow for the new entry...
I wish there was a cleaner more effective way to navigate the new pipelines as they don't seem to be very user-friendly and fit limited scenarios. Thank you all for your attempt to help.
------------------------------
Lorrie B
------------------------------
