Microsoft Dynamics 365 and GDPR

The General Data Protection Regulation, or GDPR, is fundamentally about protecting and enabling the privacy rights of individuals. Read more about Microsoft’s commitment to security at the Microsoft Trust Center.+

For Dynamics 365 applications and services, the following white papers provide an overview of the GDPR and suggest an approach for how you can think about both enhancing your data protection capabilities as well as how you may want to think about complying with the GDPR as expressed in four stages – Discover, Manage, Protect and Report.

Customer Engagement

Dynamics 365 for Sales

Dynamics 365 for Customer Service

Dynamics 365 for Field Service

Dynamics 365 for Project Service Automation

Finance and Operations, Enterprise edition

Dynamics 365 for Finance and Operations, Enterprise edition


Dynamics 365 for Retail


Dynamics 365 for Talent

Finance and Operations, Business edition

Coming soon


Microsoft Dynamics NAV – coming soon

Microsoft Dynamics C5 – coming soon

source –

Microsoft Dynamics 365 and GDPR

What is new on Dynamics 365 for Finance and Operations 7.3 Platform 12

Hi all,

I’m back with the blog and as a first post I would like to share the new features on Dynamics 365 for Operations 7.3 Platform 12.

What’s new or changed in Dynamics 365 for Finance and Operations, Enterprise edition 7.3

I would like to highlight the new feature below that for me will make a big improvement on the customers and on the product.

Notifications in Point of Sale

In today’s modern retail environment, the store associates are assigned various tasks such as helping customers, running transactions, performing stock counts, or receiving orders in the store. Point of Sale (POS) client empowers the associates to do these and much more, all in one application. With various tasks to be performed in a day, there is a need to notify the associates when a task requires their attention. To address this requirement, we have created a notification framework that utilizes the notification capability in POS. For this release, the notifications can be enabled for POS operations only, and out of the box, the notifications can only be enabled for the order fulfillment operation. However, the notification framework is extensible and enables developers to easily plug in custom code for any operation. We have also provided the ability to configure role-based notifications that empower the retailers to easily define who should receive what notifications.

Payment SDK and Retail POS handlers

Payment SDK – We added the support for sending custom error messages from the payment SDK to POS. Previously POS transformed all the messages to standard error message defined in the POS. Now you can send custom messages and error code to easily troubleshoot payment errors.

POS view extension – Support has been added for extending the POS Picking and receiving screen to add custom columns.

POS APIs – New deposit override APIs have been added to support overriding the deposit through code for scenarios, such as layaway.

POS overridable request handlers – We added a new handler in POS for extensions to override the logic and automate serial number entry. If an extension requires the modification of serial number entry in POS, you can override the new Get serial number handler. For example, in POS, a dialog box captures the serial number but you can automate the flow by calling an external webservice or autogenerated serial number and then override this request.

Sample extensions – In addition to the existing samples, we added the following samples to the Retail SDK to help with extensions.

  • Retail proxy extension for store hours and cross loyalty samples.
  • Custom column sample for the Picking and receiving screen.
  • POS serial number automation sample
  • Additional POS API samples.

Demand forecast entries data entity enabled for Data management framework

Data management framework (DMF) is now enabled for the Demand forecast entries data entity (ForecastDemandForecastEntryEntity), which makes it possible to integrate with third-party systems.

In addition, each demand forecast entry is uniquely identified by a sequence number (entity field ForecastEntryNumber). For all integrations consider this unique identifier, even if it doesn’t exist in the source or third-party system.


What is new on Dynamics 365 for Finance and Operations 7.3 Platform 12

D365Ops: Using event handler on protected and private methods

Hi everyone, some classes on AX have their methods as “protected” and this blocks the possibility of the use of “event handler”.

Some of those classes you should analyse and to make the minimum possible of the use of “customization” i’ll show a easy way to make a method hock-able for event handlers.

One of the classic event handlers that we cannot use are on the NumberSequence classes.

Let’s take a look at the NumberSeqModuleRetailParameters, this class have the method “loadModule” that are usually customized to create new number sequences for the Retail module.
With AX7 we should always try as maximum as possible use Extensions and EventHandlers to don’t have customizations to be merged in future updates, etc, but in this case the method are “protected” witch don’t give you the option to create event handlers.


Customize the class, before the declare of the method use the attribute Hookable = true as below:

Continue reading “D365Ops: Using event handler on protected and private methods”

D365Ops: Using event handler on protected and private methods

D365Ops: Display method on table extension

On Dynamics 365 for Operations we don’t have the option to create methods on table extension, so we should use the extension class to do that. The example below will show how to create a display method on the table extension class and use on a form extension.

First create your table extension class and your display method following the example below:

public static class MyCustTable_Extension
    [SysClientCacheDataMethodAttribute(true)] //This attribute will cache your display method.
    public static display Name myDisplayName(CustTable _this)
        return _this.nameAlias() + "myDisplayName"; //Do here your display method as usual.


To use your display method on the form, create your new field on the form extension and use the property as below:

Continue reading “D365Ops: Display method on table extension”

D365Ops: Display method on table extension

D365Ops: Access “form controls” from a “form extension” via “Event Handler”

With the new form extension capability on AX7 we cannot create methods and change the iteration with the new controls (form controls) on the form extension. One basic example are enable and disable a new button control based on the Activate method of a Datasource, that was common on AX2012.

To do that without customization, you have to create your new button on the form extension and use Event Handler on the Activate to enable\disable the button. See the example below:

I created a new form extension (i’m using the CustTable form). I added a button and copy the event handler “onAtivated” of the CustTable datasource and paste on a new eventHandler class.

The code below will access the control:

Continue reading “D365Ops: Access “form controls” from a “form extension” via “Event Handler””

D365Ops: Access “form controls” from a “form extension” via “Event Handler”

D365Ops: Using table event handler

Event handlers can be use to fire up your code without the necessary to customize and interfere on core logic and elements.

On the example below i’ll create an event handler that will initialize my new fields that I created using extension on the CustTable.

Find the method that you want to create the event handler, right-click and choose if you want to create a Pre or Post event handler.


Create a new classe and use the paste the eventHandler to create your method.

Continue reading “D365Ops: Using table event handler”

D365Ops: Using table event handler