This post explains the process of creating sales orders in Dynamics 365 for Finance and Operations via a web service API. It describes the structure of data contracts for sales orders and lines, as well as the validation and processing methods used to integrate with external systems effectively.
This post explains how to retrieve the caller form name in an event handler class in Dynamics 365 for Finance and Operations. It addresses the business requirement of adding a query range based on the caller form. The provided X++ code demonstrates how to implement the OnInitialized event handler for a form datasource.
This post demonstrates how to read and write text files to Azure File Share using C# code. The solution includes using the ATLAS_AzureFileShareService class in Dynamics 365 for Finance and Operations to connect with Azure File Share. Methods for getting, moving, and uploading files are provided within the code.
This content demonstrates how to obtain a worker’s email address based on a specific purpose, such as “Purchase Order,” within Dynamics 365 for Finance and Operations. It includes a solution involving an extension class of the HcmWorker table to achieve this, using a provided code example for reference. The method can be called to initialize a temporary table buffer.
This X++ code demonstrates how to retrieve the owner name of a dimension value in Dynamics 365 for Finance and Operations. The business requirement is to show the cost center owner name in a report. By using the provided code, the cost center dimension value owner can be obtained and used to initialize the temp table buffer.
This post demonstrates how to persist a custom field added to the New released product dialog form to the table in X++ in Dynamics 365 for Finance and Operations. The solution extends the EcoResProductCreate form and uses chain-of-command to add the new fields to the data2Controls container. The code provided illustrates this extension.
This post explains how to make a standard field mandatory on a form in X++ within Dynamics 365 for Finance and Operations. The business requirement is to enforce a field that is optional in Standard Dynamics. The solution involves extending the PurchCreateOrder form using chain-of-command to make the Buyer group field mandatory on the form datasource.
This X++ code creates default dimension records for specific dimension values in Dynamics 365 for Finance and Operations. The solution involves using a class called ATLAS_LedgerDimensionHelper, which includes a method named getDefaultDimension. This method takes dimension values as input and creates default dimension records using the provided values.
This content demonstrates how to obtain financial dimension value descriptions in X++ for Dynamics 365 for Finance and Operations. The business requirement is to display these descriptions in an inquiry screen. The provided solution involves using a specific code to achieve this functionality.
This X++ code demonstrates how to filter procurement categories in Dynamics 365 for Finance and Operations. The business requirement is to only allow tangible procurement categories to be selected. The provided solution uses a custom class extension to filter and display only tangible categories when selecting procurement categories or adding products to a purchase order line.