Key Updates in Dynamics 365 F&O for Version 10.0.39

Here’s a concise summary of the platform updates in Microsoft Dynamics 365 Finance & Operations version 10.0.39 (March 2024):

1- Additional Languages Available:

• Six new languages are now accessible for user selection: Spanish (Bolivia), Spanish (Dominican Republic), Spanish (Ecuador), Spanish (Guatemala), Spanish (Peru), and Spanish (Venezuela). To set your preferred language, navigate to User options > Preferences > Language and country/region preference.

2- New Vendor Invoice Center:

• A revamped workspace replaces the existing Vendor Invoice Automation workspace.
• Provides an intuitive view of invoices at different processing stages.
• Upcoming releases will introduce detailed drill-down lists and Copilot integration for exception handling.

3- Document Type Settings for Transferred Invoices:

• Customers can now decide which document type to apply to transferred documents from Invoice Capture.
• Document type settings can be configured across legal entities.

4- Default Financial Dimensions on Cost Invoices:

• Default financial dimensions (Business unit, Cost center, and Department) from Invoice Capture now appear on the header of cost invoices.
• Streamlines the invoice process and ensures correct approval routing.

Remember that some features may be available as part of a preview release, and the content is subject to change. For more details, refer to the official documentation.

How to fix Error: "Common Language Runtime detected an invalid program" in D365FO

Recently, we upgraded our environment, which resulted in one of our customizations, previously working flawlessly, throwing the "Common Language Runtime detected an invalid program" error. During the debugging process, we identified a piece of code, to be the root cause of the error.

Error Screenshot:

Code Snippet Causing The Error:

Error Fix: To resolve this issue, I stored the result of DateTime::Now in a variable and then accessed the Ticks property from that variable. This approach eliminated the error, and the code now functions properly as it did before.

Note:

I understand the fix may seem unusual and nonsensical to some, but regardless, it worked. 😊

Unlocking Worker Insights: Exploring Data Retrieval from Various Tables via HcmWorker in D365FO

During the development or customization in the Human Resource Module, we often required access to various tables' data to use in different functionalities. In this blog post, I've endeavored to consolidate all the relevant tables that provide data for the Human Resources module's displays and operations.

Note: The tables data below have been selected based on the HcmWorker table.

Get HcmWorker Table from Personnel Number: HcmWorker hcmWorker = HcmWorker::findByPersonnelNumber('00006');

Get Active HcmEmployment Table from HcmWorker Record Id: HcmEmployment hcmEmployment = HcmEmployment::getActiveEmploymentsByWorker(hcmWorker.RecId);

Get DirPerson Table from HcmWorker: DirPerson person = hcmWorker.DirPerson();

Get DirPersonName Table from DirPerson Record Id: DirPersonName dirPersonName = DirPersonName::find(person.RecId);

Get HcmPersonPrivateDetails Table from DirPerson Record Id: HcmPersonPrivateDetails personDetails = HcmPersonPrivateDetails::findByPerson(person.RecId);

Get HcmPositionWorkerAssignment Table from HcmWorker Record Id: HcmPositionWorkerAssignment positionWorkerAssignment = HcmPositionWorkerAssignment::getActivePositionWorkerAssignment(hcmWorker.RecId);

Get HcmPositionDetail Table from HcmPositionWorkerAssignment Position: HcmPositionDetail hcmPositionDetail = HcmPositionDetail::findByPosition(positionWorkerAssignment.Position);

Get HcmPositionHierarchy Table from HcmPositionWorkerAssignment Position: HcmPositionHierarchy positionHierarchy = HcmPositionHierarchy::findByPosition(positionWorkerAssignment.Position);

Get HcmPositionWorkerAssignment Table from HcmPositionHierarchy ParentPosition: HcmPositionWorkerAssignment parentPositionWorkerAssignment = HcmPositionWorkerAssignment::findByPosition(positionHierarchy.ParentPosition);

Get LogisticsPostalAddress Table from DirPerson Record Id: LogisticsPostalAddress logisticsPostalAddress = DirParty::primaryPostalAddress(person.RecId);

Get HRMCompFixedEmpl Table from HcmWorker Record Id and HcmPositionWorkerAssignment Position: HRMCompFixedEmpl fixedCompensation = HRMCompFixedEmpl::findMostRecentFixedCompensation(hcmWorker.RecId, positionWorkerAssignment.Position);

Get JmgEmployee Table from HcmWorker Record Id: JmgEmployee employee = JmgEmployee::find(hcmWorker.RecId);

Get HcmPersonDetails Table from DirPerson Record Id: HcmPersonDetails hcmPersonDetails = HcmPersonDetails::findByPerson(person.RecId);

Get HcmPositionType Table from HcmPositionDetail Position Type: HcmPositionType positionType = HcmPositionType::find(hcmPositionDetail.PositionType);

That's all for now. I hope you find this information helpful.

How To: Customize BankPaymentAdviceVendV2 SSRS Report

In D365FO, there are two versions available for bank payment vendor invoices. However, in the latest version, Microsoft has made it mandatory for users to utilize the Bank Payment Advice V2 report, as shown in the image below.

In this blog, we will discuss how to customize the BankPaymentAdviceVendV2 report step by step.

Step: 1
Create an extension of BankPaymentAdviceVendV2Tmp Table.

Step: 2
Create an extension of the BankPaymentAdviceVendControllerV2 class and write a COC for the getReportName() method. Design your new custom report to replace the out-of-the-box report.

Step: 3
Create an extension of the BankPaymentAdviceVendDPTransferQueryGenerator class and write a COC for addInsertionFeilds() and addProjectionFields() methods to initialize and map your custom fields, if any.

addInsertionFields Method: In this method you need to initialize your custom fields

addProjectionFields Method: In this method you need to map the fields of BankPayAdviceVendTmp (V1) in the same sequenece as provided in addInsertionMethod. It is simply assignment of the value through version 1 table to version 2 table.

Note: If you have customize field in BankPaymentAdviceVendV2Tmp table then you also need to extend BankPaymentAdviceVendTmp, so that you can map it in addProjectionFields method. Otherwise you won't pass the values in fields.

Step: 4
Now subscribe the getDefaultReportFormatDelegate() method and under VendPaymAdvice enum add the highligted code. 

Step: 5
Duplicate the OOTB BankPaymAdviceVendV2 report.

Step: 6
Override insert() method event handler (onInserted) of BankPaymentAdviceVendTmp table, so you can assign value in version 1 table and map it in projection fields method as show in step-3 image.

Step: 7
Now just we need to select report format design from Print management setup (Account Payable -> Setup -> Forms).

That is all you need. Cheers!

Focus on Troubleshooting

This post is intended for those who have started their career in D365FO as Technical Consultants.

In my experience, the approach to programming a from-scratch application differs from working on an already-built product with thousands of lines of code. Since we work on D365FO, which has an extensive codebase, our approach varies from starting development from scratch.

When working on a product, the key skills that should be emphasized are debugging and troubleshooting. The ability to find errors efficiently is crucial. In my view, to excel in Dynamics as a technical consultant, focusing on debugging is essential. You need to understand where the backend code for forms or reports, which run on the user interface, is located. Learn to backtrack from there, and if an issue arises, understand how to debug it. For instance, in the "info" class "add" method, all the info, warnings and errors are generated throughout Dynamics. By placing breakpoints and using the call stack, backtrack to understand the flow of the code.

Repeating this process of debugging will enhance your debugging skills, providing a better understanding of the Dynamics backend structure. The more you engage in debugging, the clearer your understanding of Dynamics will become, leading to improvement in your overall skills.

I hope that this will be beneficial advice. 🙂

Benefits and Usage of 'Add Developer Placeholder' Option in D365FO Task Recorder

Function: The "Add Developer Placeholder" feature in Dynamics 365 Finance and Operations is a powerful tool within the Task recorder functionality. Its primary function is to allow users to insert a placeholder step into the recorded steps list. Unlike other steps, the placeholder step remains discreet during task guide viewing, playback, and maintenance of a recording. This feature essentially acts as a silent note to developers without cluttering the user interface or affecting the recorded process.

Reference: Microsoft Dynamics 365 Documentation

Usage and Benefits: The utility of the "Add Developer Placeholder" option becomes apparent in scenarios where a recorded process demands custom development or additional logic beyond the standard capabilities of Task recorder. For instance, if a step requires data validation or specific calculations not inherent to the standard business process, the placeholder serves as a virtual signpost. By incorporating these placeholders, users effectively communicate to developers that certain elements of the recorded process necessitate further customization.

Reference: Task Recorder Quick Reference

This functionality ensures a seamless collaboration between users and developers, streamlining the customization process by providing clear insights into the specific requirements. The "Add Developer Placeholder" feature thus stands as a testament to the user-centric design philosophy of Dynamics 365 Finance and Operations, offering a nuanced solution for businesses seeking both efficiency and customization in their workflows.

D365FO Effortless Deployments: Building Your DevOps Pipeline

In this blog, we will explore the creation of a pipeline to automate the process of generating deployable packages in DevOps. This method of creating deployable packages is not only swift but also time-saving. It eliminates the need to manually build and sync your models, allowing for automated package creation. Furthermore, it sparing you the effort of manually executing each step.

Before we get started make sure that pre-requisite nuGet packages and relevant components are added to your VM from where you want to connect your pipeline for deployable package.

If it is not installed, check it out this blog (Azure DevOps Setup for Deploying Dynamics 365 F&O Package).

Note: The folder paths provided below are according to my environment. Please fill in the folder path according to your setup.

Step-1:
Open DevOps and click on "Pipelines," then select "Import Pipeline" as attached below.

Note: Download pipeline.

Step 2:
Browse the pipeline provided by Microsoft to upload the relevant resources.

Step 3:
After importing the JSON file, it will create resources. Now, you just need to fill in the values highlighted in the screenshots below, according to your project's naming conventions.

Note: Fill in only the highlighted fields and leave the remaining fields blank.

Note: When you imported the pipeline above, below resource was not added. You need to add this manually by clicking on the "+" (add) sign. Click it and add the "Copy Files" resource.

Step 4:
Save your pipeline. You can also choose to save and run the pipeline simultaneously, as demonstrated below.

Pipeline is successfully created and you now can run it as show in below image.

That is all you need to do. Cheers!