Retrieving Worker Personal & HR Details in D365FO Using X++

 

Introduction

In HR and payroll modules of Dynamics 365 Finance & Operations, it’s common to retrieve detailed employee information — from personal details like marital status and gender, to financial dimensions and reporting structure.

In this post, I’ll share how I query D365FO tables to get:

  • Personal details (marital status, gender, birth date, etc.)

  • Age calculation

  • CNIC details

  • Financial dimensions (Department, Business Unit)

  • Reporting hierarchy (Who the worker reports to)


Getting Personal Details of a Worker

Fetch details like marital status, gender, birth date, number of dependents, and ethnic origin.

select hcmPersonDetails
    where hcmPersonDetails.Person == hcmWorker.Person
    join dirPartyTable
        where dirPartyTable.RecId == hcmPersonDetails.Person
    join hcmPersonPrivateDetails
        where hcmPersonPrivateDetails.Person == dirPartyTable.RecId
    join hcmEthnicOrigin
        where hcmEthnicOrigin.RecId == hcmPersonPrivateDetails.EthnicOrigin;

Calculating Age

date _asOfDate = HcmDateTimeUtil::currentDate();
age = yearDiff(_asOfDate, hcmPersonPrivateDetails.BirthDate);


Fetching CNIC Details

Retrieve the worker’s CNIC number and expiry date.

select firstonly IdentificationNumber, ExpirationDate 
from hcmPersonIdentificationNumber
    where hcmPersonIdentificationNumber.Person == hcmWorker.Person;

Getting Financial Dimensions

Fetch Default Dimension for Worker

select worker, defaultDimension 
from hcmEmployment
    where hcmEmployment.Worker == hcmWorker.RecId;

Get Department Dimension


select dimensionAttributeValueSetItem
    where dimensionAttributeValueSetItem.DimensionAttributeValueSet == hcmEmployment.DefaultDimension
    join dimensionAttributeValue
        where dimensionAttributeValueSetItem.DimensionAttributeValue == dimensionAttributeValue.RecId
    join dimensionAttribute
        where dimensionAttributeValue.DimensionAttribute == dimensionAttribute.RecId
        && dimensionAttribute.Name == 'Department';

To get the Business Unit dimension, simply replace 'Department' with 'BusinessUnit'.

Finding Reporting Position

Identify the position (and person) to whom the worker reports.
select * from hcmPositionWorkerAssignment
    where hcmPositionWorkerAssignmentReportsToPosition.Worker == hcmWorker.RecId;




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