Looking for Pipeline Suggestion
I am working on a pipeline that will update a set of records when a separate record is updated. Use case, The user needs to create several records to perform the same task at multiple locations. A ...
Forum Discussion
Good morning,
If you're trying to move data between records that have an established Table-to-Table Relationship, then you generally will use Lookup Fields to move data from the Parent/Master Record to the Children. As long as the tables are in the same app, then you can also use Summary fields to move data from Children to the Parent, or now you can use Formula Queries (without a direct relationship). QuickBase hasn't documented the Formula Queries limitations that I know of, but I have definitely run into them. If you want the values to remain static after the Children records are created, then you can use a Snapshot Field.
With Pipelines, you are limited to 26 Steps (A - Z). So, it would take all of those steps if you only change a single field per step, and it will be a lot of nested IF statements, that I am not sure if there is a limitation on this inside of Pipelines. Another option, you could build 24 separate Pipelines.
If you choose to do this via a Pipeline, then I would recommend updating it inside of a single step. 500 records is enough that I would consider using a Bulk Record Upsert setup instead of just updating the records directly. This will help prevent throttling of your Pipeline.
Good Luck,
John
------------------------------
John Crosland
------------------------------
If you're trying to move data between records that have an established Table-to-Table Relationship, then you generally will use Lookup Fields to move data from the Parent/Master Record to the Children. As long as the tables are in the same app, then you can also use Summary fields to move data from Children to the Parent, or now you can use Formula Queries (without a direct relationship). QuickBase hasn't documented the Formula Queries limitations that I know of, but I have definitely run into them. If you want the values to remain static after the Children records are created, then you can use a Snapshot Field.
With Pipelines, you are limited to 26 Steps (A - Z). So, it would take all of those steps if you only change a single field per step, and it will be a lot of nested IF statements, that I am not sure if there is a limitation on this inside of Pipelines. Another option, you could build 24 separate Pipelines.
If you choose to do this via a Pipeline, then I would recommend updating it inside of a single step. 500 records is enough that I would consider using a Bulk Record Upsert setup instead of just updating the records directly. This will help prevent throttling of your Pipeline.
Good Luck,
John
------------------------------
John Crosland
------------------------------