Attachment not synching via Data Feed
We recently upgraded to Archer 5.5 SP1 and have been seeing issues with synching attachments from attachment type fields. However, attachments are getting synched via Sub forms.In the warning, we get a message that unable to locate file though the file is present in File repository. Please let us know if anybody has got this issue after upgrading to 5.5 SP1.
Thanks in Advance.
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
Are you using an Archer Web Services Transporters (Archer-to-Archer feed)? And, if so, are you using the "workaround" to retrieve the attachments from the File Repository?
Version 5.5. SP1 now supports attachments in an Archer Web Services Transporters. You can just map the Target attachment field to the Source attachment field and Data Feed will correctly retrieve the file from the File Repository and attach it to the target record. One of our goals when we made this change was to make sure the workaround still work, because we did not want to break existing Data Feeds. We tested several scenarios but maybe you have a scenario that wasn't considered and the workaround does not work.
I would suggest removing the workaround and just map the source attachment field directly to the target attachment field and see if this resolves your issue.
Of course, this is presuming you are using AWS Transporter with the "workaround". If this is not the case then this answer will not help you . In this case, could you please attach the Data Feed configuration and I will take a look to see if I can see the problem.
I am also facing this issue in 5.5 SP1 P1.
Warning - "Unable to locate file ....." and the file does not get imported either.
I have simply mapped the source instance attachment field of "Questionnaire Comments" sub-form to target instance attachment field (again the Questionnaire Comments sub-form).
Please not the Archer instances are different. Do I need to manually sync the file repository of both instances to get it work ?
We found an issue where the attachment mapping does not work when the source attachment is in a cross-reference or subform field. This has been fixed in 5.5 SP2 P2 and 5.5 SP3. Sorry for the inconvenience.
First, it would be 5.5 SP2 P2, not "P1" that contains this fix. Yes, the latest versions always include all the fixes from previous versions. So upgrading to 5.5 SP2 P2 or 5.5 SP3 will fix this specific issue. Neither one of these versions have been released yet. 5.5 SP2 P2 is scheduled to be released in about 2 weeks, first week of May.