Remote Process Sync: Attachment sync making incident form fields empty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2023 10:15 PM
Hi all,
We have set up a remote process sync between two instances for our client and it works perfectly fine until you only upload an attachment and don't make any updates to form fields.
When only uploading an attachment the incident record on the inbound instance will have all of it's form field values changed to empty/deleted whilst the attachment successfully copies across
When only making updates to the form fields or uploading an attachment then making updates to the form fields that's when the inbound incident record retains all of it's form field values and also has the attachment successfully copy across
My question is, is there a configuration error or a reason as to why the remote process syncing of only attachments is causing this behaviour?
Outbound subflow: Attachment action
Inbound subflow: Attachment action
Thanks,
Lindy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2024 01:42 AM
Hi,
my recommendation is to create flow variable, use the flow logic to set this flow variable somewhere at the beginning and check if the incoming payload contains anything in the "changed_fields" object.
And then use condition and run the update of the fields only if the changed_fields actually contained anything meaningful.