Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
This is very much needed. We have four clients currently all requiring a customization to get this capability in the system.
As the status of Pauls idea is still on "NEW", I understand that it has not been taken in account by MS in the last 6 month yet.
I absolutely agree to Pauls idea, which - frankly speaking - is legally mandatory (at least for European countries)!
In general Microsoft Dynamics 365 Marketing lacks GDPR compliant out of the box solutions.
(E.g. same goes with cookie management on dynamics portal pages - but that is a different story.)
It is inevitable that changes in forms get stored at a contact only after the reconfirmation of the data subject (=contact) took place via DOI mail!
To make it even worse:
We faced the completely unexpected situation (luckily it was during tests) that, if in a marketing form an email address is used, which already exists in the Dynamics database, after submit of the form the existing data get instantly overwritten with the ones in the marketing form!
Thus, the provided DOI implementation seems to me as an unacceptable breach of data integrity and GDPR regulations.
To sum it up:
If I understand correctly, as long as this DOI is not working legally compliant, no implementation of Microsoft Dynamics marketing forms can be used even for a plain and simple email registration form (at least without heavy customizing and workarounds)!
Great idea Martin! Good luck!
it takes the same logic on sales and transfers
Allow sales over picking and Allow transfer order over picking on Work users in Warehouse management
Even if the customer accidentally create an empty field, that is not used anywhere - it remains between the valid custom values without the possibility to delete it!
This is also very important to us! It now basically stops us from continuing to use Dynamics Marketing. We've also discussed it with the product group, so let's hope they take this up quickly. If you implement a feature like 'business unit scoping', then it should work for everything. I personally don't know anybody that is not using business units with dynamics.
(Please vote for this idea)
Thanks Ivan, great tip for table browser. Hope MS will action this soon!
Indeed - Rounding Precision with more decimal places
This is a massive requirement for organisations that don't have developers, but want the applications developed within their tenancy, and not wishing to onboard a third party to do so.
yes please - important requirement