Finance | Project Operations, Human Resources, ...

Importing attachments using the "Customer attachments" data entity

(0) Share

Report

Posted on by Scott_K

I have the same issue described in Daniel Zook's post on January 14, 2021 and have attempted all of the steps outlined but the process fails with the message below.

Results. 'FileContents' is required when attaching a file

Results. validateWrite failed on data source 'DocuRefEntity (DocuRefEntity)'

Some observations I have made are

1. The field FileContents is visible in the entity definition and the mapping

2. The field mapping for FileContents does not show in the mapping of an export project

3. Adding a new EntityMap node to the manifest file appears to allow me to add the mapping on the import project but there is a data type issue

The message appears to indicate that the FileContent field is required, but there appears to be no way include it.

Product details

Has anyone been able to use the "customer attachments" entity to import file attachments?

Thank you

I have the same question (0)

All responses (9)

Answers (0)

André Arnaud de Cal... 300,970 Super User 2025 Season 2 on at

Like (0)

Report

Hi Scott,

Usually, when I have issues importing data, I try to do an export first. In this case, the file contents are not added during the export. If you try to export product attachments, you will see an additional resources folder in the data package. This is not available in the customer attachments entity.

You can check LCS issue search for possible known issues or contact Microsoft Support.

Was this reply helpful? Yes No
Scott_K 5 on at

Like (0)

Report

Andre,

Thank you for your response! I have tried exporting the "Customer attachments" as a data package and do not get a "Resources" folder. I also cannot find any other attachment entities such as product attachments to test. I did come across an article that suggests custom entities must be developed to handle attachments. If I am mistaken, would you mind providing me with the names of some other standard attachment entities that I can look for?

As for LCS, I did find an issue specifically related to the Customer attachments entity, but it appears to suggest that the issue has been resolved. I am currently using version 10.0.22.

Thank you,

Scott

Was this reply helpful? Yes No
Scott_K 5 on at

Like (0)

Report

I found the Product document attachments entity and was able to export a package that includes a Resources folder that includes the attached files (in another sub folder)

The Customer attachments entity exports a package but it does not have a Resources folder. There are customer records with file attachments, so its not a matter of not having any files. It seems to me that the entity is still broken in version 10.0.22. Is anyone able to confirm that this entity works for them? If so, what version of DFO are you using?

Thank you,

Scott

Was this reply helpful? Yes No
André Arnaud de Cal... 300,970 Super User 2025 Season 2 on at

Like (0)

Report

Hi Scott,

Yesterday, I tested it with a 10.0.24 (preview) environment. That has the same behavior as mentioned above. I would suggest to contact Microsoft Support.

Was this reply helpful? Yes No
Scott_K 5 on at

Like (0)

Report

Andre,

I appreciate your feedback! It appears that Microsoft may have provided a new entity named "Customer V2 attachments" as a solution to the problems with "Customer attachments". This new entity appears to be working.

Thank you,

Scott

Was this reply helpful? Yes No
dmartinezuy 39 on at

Like (0)

Report

Scott

Did you solve the problem? I try to use "Customer V2 attachments" also and the problem continue. It's imposible to assign something to "Filecontents"

kind regards

Daniel

Was this reply helpful? Yes No
Suggested answer

Scott_K 5 on at

Like (1)

Report

Daniel,

Yes, the field "FileContentsFileName" should be populated with the file name and extension as in the following example:

The package needs to have 2 nested subfolders. The first is named "Resources" and the second is "Customer V2 attachments" (the entity name). The package should look like this:

I hope this helps!

Was this reply helpful? Yes No
dmartinezuy 39 on at

Like (0)

Report

Thanks for your return.

I think it's working with your help, at least the first test was ok

Thanks for your time

Daniel

Was this reply helpful? Yes No
Suggested answer

Parag Chapre 12,254 Most Valuable Professional on at

Like (2)

Report

Hi Daniel,

I was searching for the same, but I found a blog post which explained this in detailed.

dynamicsplus.com.au/.../

Was this reply helpful? Yes No