UPDATE: The latest version of the Attachment Management solution has the ability to specify the entities that will utilize the solution. Be sure to “un-select” the adx_webfile entity and the ensuing disaster described in this post will be avoided. 🙂
Original Post here…
A while back I wrote about Microsoft Dynamics 365 Attachment management solution from Microsoft AppSource as a way to move email and note attachments to Azure to conserve space.
I discovered an issue with the solution that will adversely affect your Dynamics 365 Portal installed on the same tenant.
I needed to make some updates the theme.css file for my portal. I made the changes in an editor and then attached the file to the Webfiles record in Dynamics 365. If you have worked with the Dynamics 365 Portals you know that files like CSS and images are stored as note attachments to portal Web File records.
Before updating the theme.css file, the portal appeared normal:
However, after updating the theme.css file I got this:
It appeared that I messed up editing the theme.css file; which is extremely likely as I am actually NOT any kind of CSS expert, I know just enough to be dangerous.
I re-downloaded, made a few adjustments and uploaded, still the same issue! I refreshed the portal cache (here’s how) and I even restarted the portal from Office 365. The Portal still had issues rendering.
I finally decided to restore the original CSS file… however, the portal was still messed up (again after many refreshes and restarts)
I wasn’t sure at all what the issue could be… I tried recreating, double checked every setting until I remembered that this Dynamics 365 instance had the Attachment Management solution installed and configured. The app will copy ALL attachments to Azure, including Portal files!
I went into Dynamics 365 customization and disabled the Attachment Management plug-ins and then re-added the theme.css file. BOOM. Problem solved (for now). The Portal reads the attachments, not from Azure, so it never was able to find my updated theme.css file.
The Attachment Management solution will only move attachments to Azure when they are added or updated, and not existing files. Since the portal was setup before I setup the Attachment Management, I never noticed until I needed to change some files.
I reported the problem to AppSource support so hopefully this gets properly fixed in the future. In the meantime you will need to disable the plug-ins before doing any kind of portal work involving CSS or image files or just not use the Attachment Management app at all and look at other 3rd party solutions.
If you do use, remember to to re-enable the plug-ins when done.
Hope this helps!
Nick Doelman is a Business Solutions MVP and is currently trying to investigate where the summer went. Nick will be at CRMUG Summit and will not turn down any offers to have a beer and chat about Dynamics 365, Hockey or Powerlifting.