Attachments in D365 can be various types. One type is called "Note". A Note type attachment is plain text. For example, it looks like this…
As you can see, the type is "Note", and under General/Details/Notes, there is the plain text note that is just the text "This is the note message."
Another type of attachment in D365 is called "File". A File type attachment is just like an attachment in an email message. It could be a DOCX document file, an XLSX spreadsheet, a PDF document, or any other file type at all. In my case, I'm testing the file attachment import using a DOCX file, but the type of file is irrelevant for this process.
For example, here is a File type attachment in D365.
You can see in the screen capture that the type of attachment in this case is "File", and in the Attachment fast tab it shows the file information. The file can be previewed in the "Preview" fast tab.
This is what I expect the end result to look like when I import a D365 "customer attachment" record of type "File." The challenge I'm facing is how to include the file itself in the import process. Every time I try to import a D365 attachment of type "File", I get these errors:
Results. 'FileContents' is required when attaching a file
Results. validateWrite failed on data source 'DocuRefEntity (DocuRefEntity)'
It seems like it should be possible to import the FileContents, but there is no documentation on this that I can find, and so I don't know how to populate that field.
Here is an example of the record I'm trying to import. (The FileContents is empty because there is no documentation on how to populate that field.)
Create a data export job
Add export entity: customer attachment
Enable "data package"
Run export job (click "Export Now")
Click "Download package" in export results page button bar at the top
Extract the package
Add a folder named Resources
Add the file(s) to the Resources folder that you want to import as file type attachments
Edit the Excel file.
Delete the existing entries, leaving the header row
Generate GUID using website: https://www.uuidgenerator.net/guidand put it to DocumentID column, with curly braces
Save the changes to the XLSX file
Compress all 3 files and the folder to a zip fileTheir instructions stopped their, so I made some assumptions and tried these steps to import it...
Create an Import job.
Click Import now
Thank you for your feedbacks and patience.
After further review on my end, feedback is that this is a known issue that is affecting, importing attachments via CustomerAttachmentsEntity.Here is the link for the information provided above https://fix.lcs.dynamics.com/Issue/Details?bugId=533465&dbType=3&qc=5438566630de29d6e8e118235204020ec14708a305859d1ba2a15665c9c1b2d3 and investigations are currently on-going to address this issue. You can use the 'notify me' option to receive notifications on its progress.
Furthermore, while there is no tentative date on the fix yet, I would appreciate it if you could allow us some more time for the necessary actions to be taken for a possible resolution or workaround.I understand this is not the ideal scenario for this, however, this concern is greatly noted by Microsoft going forward.
Please let me know if there are further concerns or clarification to proceed further on the case.-----------So at this point I'm waiting till this is fixed before we go live with D365. In the meantime, I've got lots of other things to do to prepare for the migration.
thanks for following up on this, I see the ticket in LCS. I am sure another factor that will affect this functionality will be whether you are storing the documents on Azure blog storage or SharePoint. My gut tells me that the import will only work for the standard OOB D365 blog storage.regards,
My name is Babajide and I am Iretijesu's Technical Lead. I am reaching out to you today, so I could thank you for all your patience and collaboration on this support request.
Over this period, we had to go through different technical authorities for further assistance and additional review, so we could make sure you received the most accurate response from our side. Kindly accept my sincere apologies for the inconvenience caused and the time you had to spend, as at this point, I can only count on your understanding that if there was any other possible workaround we would have done it right away but an investigation is currently on-going to address the stated bug.
As confirmed, Iretijesu will proceed to temporarily archive this support request as there is no tentative date on the fix yet.
Please do not hesitate to reach out to me directly in case you have any other question or concern, I will always be available in your service alongside my team.
Thank you, and keep staying safe.
If you've found this thread useful, dive deeper into User Group community content by role