Microsoft Dynamics 365 Finance and Operation Technical

    Excel Data Connector add-in in D365 F&O In this recipe, we will show you how to configure an Excel Data Connector add-in and use it to export data from Dynamics 365 for Finance and Operations and publish the updated data back in Dynamics 365 for Finance and Operations.  The Excel Data Connector app interacts with Excel workbooks and OData services created for publicly exposed data entities. Steps 1. Open a new workbook in Excel and navigate to the Insert tab. Under Add-ins, select My Add-ins, as shown in the following screenshot:            2. Under Office Add-ins, navigate to STORE, search for Microsoft Dynamics Office Add-in, and click on Add. This is shown in the following screenshot: 3. Once you've clicked, a new window will open within Excel as follows. Click on Add server information and the system will ask for account credentials. You have to sign in as the user that has access in your Dynamics 365 for Finance and Op...

Methods of Integration: DMF (Data Management Framework) Recurring Integration Business Event  Entity Store Bring Your own Database(BYOD) Azure Data Lake Dual Write OData Custom Services

 Authenticating a Client Applications We can create multiple types of apps in AAD, Here we will discuss two kinds of Applications that are separated and supported in Microsoft AAD for Dynamics 365. 1. Native Client Application: This required a redirect URL, which Azure AD user to return a token response. This flow user a username and password for authentication and authorization. 2. Web App/ API: A confidential is an application that can keep a client's password confidential to the world. It uses a client APP ID and a client secret key to prepare client credentials.  Step1: Register Your Application in Azure AD (Active Directory) : Sign in to your Azure portal. Navigate to Azure Active Directory. Go to "App registrations" and register your native client application. Note down the Application ID (Client ID) generated for your app. Configure the Redirect URI to which the authentication response should be sent. It should match the URI you specify in your app. Step2: Configu...

 Building a query object: Query objects in Dynamics 365 for Finance and Operations are used to build SQL statements for reports, views, forms, and so on. They are normally created in the AOT using the drag-and-drop functionality and by defining various properties. Query objects can also be created from the code at runtime. This is normally done when AOT tools cannot handle complex and/or dynamic queries. Build Query in X++:  Queries can also be built dynamically with X++ code. Both approaches are used in standard applications. One advantage of making the query dynamics is that it can not be public in the AOT, and is protected against unintentional AOT changes.  X++ Query Component QueryRun Query QueryBuildDataSource QueryBuildFieldList QueryBuildRange QueryFilter QueryBuildDynaLink QueryBuildLink QueryRun:  use query Run objects to execute the query and fetch data. Query:  The query object is the definition master. its own properties and has one or more dat...

 Renaming of Primary Key through Code in X++ Hi Everyone, This blog explain how to renaming of primary key through code in the Dynamics 365 for Finance and Operations. Most of you who are familiar with the Dynamics 365 for Finance and Operations applications, have probably used the standard Rename function. This function allows you to rename the primary key of almost any record. With this function, you can fix records that were saved or created by mistake. This function ensures data consistency, that is, all the related records are renamed as well. In this blog I will explain how the record's primary key can be renamed through the code. As an example, we will create a job that renames a customer account. Step :  Create a new project, create a runnable class named CustAccountRename, and enter the following code snippet. class CustAccountRename {      public static void main(Args _args)      {             CustTable...

Add lookup to Batch dialog Step 1: Creating a batch job parameter creates a contract class containing a reference to the UI builder class. Code:  [ DataContractAttribute ,     SysOperationContractProcessingAttribute (ClassStr(Name UI Builder Class))] class  Lok_CustomerPaymentContract {     LedgerJournalNameId     journalName;     [         DataMemberAttribute ,         SysOperationLabelAttribute (literalStr("As per required ")),         SysOperationDisplayOrderAttribute ('1')     ]        public   LedgerJornalNameId    parmJournalName(LedgerJournalNameId   _journalName =           journalName)   {        JournalName = _journalName;        return   journalName;   } } Step 2: Now Create UI Builder Class to customize the paramet...