You said,
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? If you are actually comparing the RID of one table and the RID of another table, they will almost never match.
When I did the connected table from the Escalation QB to the Network QB I brought in the id of that record. So when the record is updated in the Network QB, I do the match on that record id. It's called record id in the Escalation QB and DNT Record ID in the Network QB. So, they should always match. Matching it not the issue, because it retrieves the correct record but it's not upating it.
Here is the YAML. I changed a few things for privacy.
# Update DNT Escalation QuickBase
#
# Account slugs:
# - quickbase[123generic]: Realm Default Account <None>
---
- META:
name: Update DNT Escalation QuickBase
enabled: true
- TRIGGER quickbase[123generic] record on_update -> a:
FILTERS:
- AND:
- 'liaison_closed_date set '
inputs-meta:
export_fields: '"Liaison Closed Date, Liaison Comments, DNT Record ID" <11,
12, 6>'
table: '"Dental Network Operations: DNT Escalations" <123generic>'
trigger_fields: '"Liaison Closed Date" <11>'
- QUERY quickbase[123generic] record search -> b:
FILTERS:
- AND:
- id equals {{a.dnt_record_id}}
inputs-meta:
export_fields: '"Liaison Comments, Liaison Date Closed" <167, 168>'
table: '"DNT Escalation: DNT Escalation" <123generic>'
- b<>LOOP:
- DO:
- b<>ACTION quickbase record update -> c:
inputs:
liaison_comments: '{{b.liaison_comments}}'
liaison_date_closed: '{{b.liaison_date_closed}}'
...
Nevermind, I found the problem. On the update record action, I had it pulling the date from the searched record and not the updated record.
