Pipeline message-Skipped because set values are the same as in source object.

Question

I have a quickbase we will call it Network that has a connected table to another quickbase that we will call Escalations. On the connected table in the Network QB, i have two added fields that reps update in the Network QB. I then want to send the data in those two fields back to the Escalations QB. The fields in the Escalations QB have the same name.

I created a pipeline who's trigger is when one of those fields in the Network QB is updated. My next step is search record query on the Escalations QB and it pulls back the record where the Escalation QB record id matches the Network Escalation record id. Next step is the loop and the final step is an update record. The record to be updated is the search record. I pull in the fields to be updated and do the matching. The pipeline ran with no errors but the record from the Escalation QB did not update. On the activity I see on the update record step, it gives me this, "Skipped because set values are the same as in source object.".

What have I done wrong?

Thanks

donlarson · Answer

You said,&nbsp;&nbsp;You said, " Escalation QB record id matches the Network Escalation record id"Don't you need a reference field in the table that matches the other application?&nbsp; &nbsp;If you are actually comparing the RID of one table and the RID of another table,&nbsp; they will almost never match.&nbsp;&nbsp;

carolmcconnell · Answer

When I did the connected table from the Escalation QB to the Network QB I brought in the id of that record.&nbsp; So when the record is updated in the Network QB, I do the match on that record id.&nbsp; It's called record id in the Escalation QB and DNT Record ID in the Network QB. So, they should always match.&nbsp; Matching it not the issue, because it retrieves the correct record but it's not upating it.

carolmcconnell · Answer

Here is the YAML.&nbsp; I changed a few things for privacy.# Update DNT Escalation QuickBase## Account slugs:# &nbsp;- quickbase[123generic]: Realm Default Account &lt;None&gt;---- META:&nbsp; &nbsp; name: Update DNT Escalation QuickBase&nbsp; &nbsp; enabled: true- TRIGGER quickbase[123generic] record on_update -&gt; a:&nbsp; &nbsp; FILTERS:&nbsp; &nbsp; - AND:&nbsp; &nbsp; &nbsp; - 'liaison_closed_date set '&nbsp; &nbsp; inputs-meta:&nbsp; &nbsp; &nbsp; export_fields: '"Liaison Closed Date, Liaison Comments, DNT Record ID" &lt;11,&nbsp; &nbsp; &nbsp; &nbsp; 12, 6&gt;'&nbsp; &nbsp; &nbsp; table: '"Dental Network Operations: DNT Escalations" &lt;123generic&gt;'&nbsp; &nbsp; &nbsp; trigger_fields: '"Liaison Closed Date" &lt;11&gt;'- QUERY quickbase[123generic] record search -&gt; b:&nbsp; &nbsp; FILTERS:&nbsp; &nbsp; - AND:&nbsp; &nbsp; &nbsp; - id equals {{a.dnt_record_id}}&nbsp; &nbsp; inputs-meta:&nbsp; &nbsp; &nbsp; export_fields: '"Liaison Comments, Liaison Date Closed" &lt;167, 168&gt;'&nbsp; &nbsp; &nbsp; table: '"DNT Escalation: DNT Escalation" &lt;123generic&gt;'- b&lt;&gt;LOOP:&nbsp; - DO:&nbsp; &nbsp; - b&lt;&gt;ACTION quickbase record update -&gt; c:&nbsp; &nbsp; &nbsp; &nbsp; inputs:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; liaison_comments: '{{b.liaison_comments}}'&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; liaison_date_closed: '{{b.liaison_date_closed}}'...

carolmcconnell · Answer

Nevermind, I found the problem.&nbsp; On the update record action, I had it pulling the date from the searched record and not the updated record.&nbsp;

Forum Discussion

Pipeline message-Skipped because set values are the same as in source object.

Related Content

Three Words of Advice on Pipelines

Pipeline Not Triggering

AI Smart Builder for Creating Apps and Streamlining Pipelines

Pipeline API Post

Pipelines: Lookup newest record?