Flow Designer: Copy Attachments Not Working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2020 06:38 PM
I have a flow that triggers when a record is added to a custom table of mine.
When that record is created, the flow needs to create a new record in the sys_data_sources table, and once that new record exists, i need to copy an attachment from the trigger record and add it to the new record on the data sources table.
I continue to get the following error:
Here is what the flow design looks like currently:
Once i'm able to get this attachment added, then i'll be creating a custom action to effectively kick off this data being loaded as an import set and the loaded/transformed.
This is my first go with Flow Designer, so any help is greatly appreciated. Thank you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-03-2021 06:24 AM
Hi Leachy23,
You need to enter sys_attachment.list in the Filter navigator.
Cheers,
Cheski
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2022 08:36 AM
To echo Bobby's reply, I too am having an issue getting more than one attachment to copy over to the new record.
The trigger is from the Service Catalog, and user attaches 2-5 images on the form.
An email is generated in Flow Designer for those images to be reviewed by a manager, but currently only the first image is coming over.
The attachmentList recognizes all the attachments:
[{"sys_id":"8e24a621db1741508c70c1391396194f","file_name":"Capture-01.PNG","file_size_in_bytes":"39911"},{"sys_id":"812466addbd341508c70c13913961987","file_name":"Capture.PNG","file_size_in_bytes":"21441"}]
But the Attachment Sys ID is only pulling: 8e24a621db1741508c70c1391396194f
Please help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2024 02:04 AM
I just had a reqierement to copy attachments from the Work Order to the Work Order Task when a new Work Order Task is created.
I ended up using this flow: