Comments
It would be a great advancement to allow Dynamics to operate seamlessly with the Azure Information Protection (AIP) classifications. Needing to access tracked emails via Outlook due to D365's inability to read emails that have Azure Information Protection (AIP).
This means one of two things
- People stop using Azure Information Protection (AIP) when they should be using it
- People have to break their flow within D365, to navigate out to Outlook, then back in again. In a Kaizen sense this is creating transportation and waste.
A dynamic header and footer is really needed where you can put in data from related records and e.g. a company logo. (similar to the rich text editor you have for the Email template)
We did this with a custom development for the header, but footer is not so easy to implement the way we did it.
This is very annoying and we have this issue here in NZ with several Customers.
An alternative solution would be to add more English display languages to be selectable by the users. https://myaccount.microsoft.com/settingsandprivacy/language
A current workarround is the following Powershell:
Install-Module MSOnline
Connect-MsolService
Get-MsolUser -UserPrincipalName Demouser1@onmicrosoft.com | Set-MsolUser -PreferredLanguage "en-NZ"
This will get the correct language, when Updating Users from Microsoft 365. However, I don't know, if setting the display language to a language that is not in the list, has other implications.
Examples
This fetchxml, using "under", was generated with the current UI (xml formatting modified to pass the malicious input filters):
fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false"
entity name="account"
attribute name="name" /
attribute name="accountid" /
order attribute="name" descending="false" /
filter type="and"
condition attribute="accountid" operator="under" /
/filter
/entity
/fetch
But this fetchxml, using "above", cannot be generated with the UI (xml formatting modified to pass the malicious input filters):
fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false"
entity name="account"
attribute name="name" /
attribute name="accountid" /
order attribute="name" descending="false" /
filter type="and">
condition attribute="accountid" operator="above" /
/filter
/entity
/fetch