Your D365 Emails Deserve Better Than Plain Text | Build Professional HTML Email Templates in Dynamics 365 Finance & Operations ERP notification emails have a reputation problem. Approval alerts, violation notices, document-ready pings — most of them look like they were built in 2004: plain text, no branding, maybe a logo if you're lucky. It doesn't have to be that way. If you've built a notification email in Dynamics 365 Finance & Operations, you've likely faced this question: where does the header banner, the logo, and the footer icons actually come from — and how do you make the email actually look good without turning it into a maintenance nightmare? A common first instinct is to hardcode the whole email as an HTML string in X++, with the images either linked to a random hosted path or (worse) embedded as long Base64 strings baked directly into the code. It works, but it's fragile: every rebrand or logo tweak becomes a code change and a deployment, the cl...
Error while Restoring DB After Dynamics F&O Version Upgrade "An unexpected failure occurred: Data plan execution failed with message One or more errors occurred. (One or more errors occurred. (One or more errors occurred. (Violation of PRIMARY KEY constraint 'I_15464SETTINGKEYINDEX'. Cannot insert duplicate key in object 'dbo.FINANCIALREPORTINGSETTINGS'. The duplicate key value is (5637144576, DisableMaps). The statement has been terminated.)))."
Dear Dev Team, We usually encounter this type of error after upgrading Dynamics versions. The simplest and most reliable way to resolve it is to restore or import the database using a temporary name , and then rename it back to AxDB afterward. Failed Execution : you will get the error message. "An unexpected failure occurred: Data plan execution failed with message One or more errors occurred. (One or more errors occurred. (One or more errors occurred. (Violation of PRIMARY KEY constraint 'I_15464SETTINGKEYINDEX'. Cannot insert duplicate key in object 'dbo.FINANCIALREPORTINGSETTINGS'. The duplicate key value is (5637144576, DisableMaps). The statement has been terminated.)))." Correct approach The key step is to temporarily rename AxDB to AxDBLocal during the import. C:\SqlPackageExe>SqlPackage.exe /a:import /sf:C:\DB\qfz-erp-stgbackup.bacpac /tsn:LOCALHOST /tdn:AxDBLocal /p:CommandTimeout=18000 /TargetEncryptConnection:False Later use below script to ...