Costin -
Since you're triggering on each record being added your Pipeline will perform that same action for each being added. It seems from your setup that when a new TMS report is added - you want to copy it over to a new table automatically correct?
If that is the case - you technically do not need to do a search in step B where you are querying for similar records in the TMS table. Instead - you can just retrieve the fields in Step A when the 'New Record' is being triggered, and copy it straight away into your second table.
Reading back to your original post - your original comment was that you wanted this to run on a schedule, of which if that is your intent, then you probably don't actually want to trigger on a new record as you are doing in Step A. Instead - you would just launch the Pipeline with the Search in Step B and schedule it to run once a week.
So in summation - you should either 1) Remove Step A and just do a weekly search to copy your records, or 2) Remove Step B from searching the table and instead copy each record in real time.
Good day,
Thank you for your guidance!
It appears that I cannot trigger a single copy when there are more than one record added; this is clear in step A, where the option specifically mentions "When Record Created."
Later edit:
I just noticed the option below where the trigger is "On New Event".
The outcome looks like what I need.
A. When a user adds multiple records the pipeline is triggered by the event.
B. With the search option, I will retrieve the records based on my criteria.
C. The records are copied only once to the output table.
Concerns:
------------------------------
Costin Angelescu
------------------------------
Costin -
The 'New Event' is a proxy for when records are added/modified - so you can handle both event types if needed in one Pipeline. It will work fine here.
As for the error - since you're still doing a search records you will still need a loop. The pipeline needs to index the record you're currently on - so IF you are still doing the search step you will need the loop.
I'll repeat one of my earlier suggestions that you don't need the search step at all. In your example it seems like you want to pick up the new record upon creation and immediately copy it. If thats true - then your 'trigger' in Step A can retrieve all the fields you need and then Step B is just copying the record. You would only need to do a search in this case if you were looking for other records of if these was on a schedule where you were running this weekly. Your Pipeline should probably look like:
Step A: New Event (On Record created) - include all the fields you want to copy in the fields the retrieve
Step B: Create new Record in clone table - include mapping of all the fields you wanted copied.
Hi,
Thank you.
After records are added, I need the pipeline to search in the entire table (new records + old records) and retrieve all with a specific criteria like: all records with "Uploaded" from column "Status".
If I delete the search, then the Create record option will just copy without my criteria.
Do you have any suggestion in this way?
Best regards,
Costin
|
| Costin Angelescu Europe I-Trade E-mail: angelescu.c@pg.com To identify I-Trade FAP owner for each carrier pls use the DOMO Card |
The concern with doing the 'Search' is that you're going to pick up more records than just the one that is being added. So you might pick up older records and end up creating duplicates. If that is the case - then you just need to reinsert the loop.
The potential here is that lets say you create record A - you do your search and find 5 records and you create 5 copies of those records. If you then create record B and you search to get the same 5 records above, then you'd be creating 5 of the same records as dupes.
If you are using the event as the trigger then you should really only be doing a 1 to 1 create then copy. If your goal is to copy records that meet a search criteria and copy those records on a schedule, then you shouldn't be using the 'On Event' as the trigger and instead you should just be doing a search and copy the response instead of having the pipeline run for each record being generated.
