Generate error on empty Financial Dimensions in D365FO

When working with Human Resources and Finance integration in Dynamics 365 Finance and Operations (D365FO), ensuring financial dimensions are properly defined on employee records is critical for accurate reporting and budgeting. In this blog, we'll look at how to enforce required dimensions using a validatedWrite event handler on the HcmEmployment table.


We'll use an event handler on the HcmEmployment table's validatedWrite method to check for the presence of specific dimensions on the DefaultDimension field.


[DataEventHandler(tableStr(HcmEmployment), DataEventType::ValidatedWrite)]

    public static void HcmEmployment_onValidatedWrite(Common sender, DataEventArgs e)

    {

        HcmEmployment HcmEmployment = sender as HcmEmployment;

        DimensionAttributeValueSetStorage dimAttrValueSetStorage;

        DimensionAttribute dimensionAttribute;


        // List of required financial dimension names

        List dimensionNames = new List(Types::String);

        dimensionNames.addEnd("BusinessUnit");

        dimensionNames.addEnd("Department");

        dimensionNames.addEnd("Budget");

        dimensionNames.addEnd("Projects");

        dimensionNames.addEnd("Worker");


        dimAttrValueSetStorage = DimensionAttributeValueSetStorage::find(HcmEmployment.DefaultDimension);


        // Loop through each required dimension and check if it's present

        ListEnumerator enumerator = dimensionNames.getEnumerator();

        while (enumerator.moveNext())

        {

            str dimName = enumerator.current();

            dimensionAttribute = DimensionAttribute::findByName(dimName);


            if (!dimAttrValueSetStorage.containsDimensionAttribute(dimensionAttribute.RecId))

            {

                throw error(strFmt("Financial dimension '%1' is required.", dimName));

            }

        }

    }

It checks if each of the required financial dimensions is present in the DefaultDimension value set.

If any required dimension is missing, it throws an error.

Conclusion:

Validating financial dimensions programmatically ensures better data integrity and aligns HR records with your organization’s financial structure. Using event handlers is a clean and extensible way to inject validation logic without customizing core logic.

Comments

Post a Comment

Popular posts from this blog

JSON-Based HTTP POST Request from X++ to Retrieve an Access Token

In today's connected systems, integrations between Dynamics AX and external APIs are essential. One common scenario is retrieving an access token from a remote API for authentication. In this post, I'll show you how to make a POST request with JSON from X++ and handle the response. We'll walk through a complete example where we send credentials to an API and parse the response to retrieve an access token. Prerequisites To follow along, you should have: Basic familiarity with X++ Access to System.Net and System.IO namespaces via CLR Interop A configured HRMParameters table to store credentials X++ code: System.Net.HttpWebRequest                 request; System.Net.HttpWebResponse              response; System.IO.StreamWriter                       streamWriter; System.IO.StreamReader              ...
Read more

Calling an External API from D365FO Using X++ to Retrieve a Token

In many Dynamics 365 Finance & Operations (D365FO) integrations, we need to authenticate with an external system before making API calls. The authentication is usually done by sending credentials (such as email, password, and API token) to the endpoint, which returns a JWT (JSON Web Token) or similar authentication token. In this post, I’ll share how I implemented an X++ method that: Sends login details to an external API in JSON format. Reads the API response. Deserializes the JSON into a usable object. Includes error handling for robust integration. Requirement Connect to an external REST API, send authentication details stored in the HRMParameters table, and retrieve an authentication token for use in subsequent API calls. Approach Use CLR Interop to call .NET classes from X++. Build a JSON request body using strFmt . Send the request via System.Net.HttpWebRequest . Read the API’s JSON response. Deserialize it into a custom ResponseTokenData clas...
Read more

Restricting Date Selection in Dynamics 365 FO using X++

Scenario Recently, I had a requirement in Dynamics 365 Finance & Operations to restrict the user from entering a transaction date that: Is greater than the current date (future date restriction). Is earlier than 2 days before the current date (past date restriction). In short: Allowed date range = From 2 days ago to today . Any date outside this range should trigger an error message and reset to today’s date. Solution Approach For this requirement, I used the addDays method in X++. The  addDays method allows us to easily calculate a date by adding or subtracting days from a given date. Syntax: addDays(_t, _value) _t : A utcDateTime value representing the starting date and time. _value : Number of days to add (positive) or subtract (negative). Example: DateTimeUtil::addDays(DateTimeUtil::utcNow(), -2); This returns the date & time 2 days before the current date. Implementation in Form Data Field Event We can handle the validation when the Tr...
Read more