Skip to main content

Use temporary table as form datasource in D365FO

In this article, we will learn how we can use the temporary table as a form datasource in D365. In our scenario, we will populate the temporary table at runtime and bind it with the form datasource. firstly, we will pass an argument on the clicked event and write the form datasource  init  method to populate the data in it.  In our scenario we will work on the CustTable form, we will populate the customer group in the temporary table which we create on the selected customer while clicking the button. Step 1:  Create a new table of type TempDB and add two new fields i.e., CustGroupId and CustGroup. Step 2:  We will create a new form with the pattern (List Type), then add our previously created temporary table as a datasource, and then drag both the fields CustGroupId and CustGroup on the form grid part. After the form creation, we will also create the display menu item of type  form  and use our form on it. Step 3:  We will create an extension of the form ' CustTable ' and creat

Use temporary table as form datasource in D365FO

In this article, we will learn how we can use the temporary table as a form datasource in D365. In our scenario, we will populate the temporary table at runtime and bind it with the form datasource. firstly, we will pass an argument on the clicked event and write the form datasource init method to populate the data in it. 

In our scenario we will work on the CustTable form, we will populate the customer group in the temporary table which we create on the selected customer while clicking the button.

Step 1: Create a new table of type TempDB and add two new fields i.e., CustGroupId and CustGroup.

Step 2: We will create a new form with the pattern (List Type), then add our previously created temporary table as a datasource, and then drag both the fields CustGroupId and CustGroup on the form grid part. After the form creation, we will also create the display menu item of type form and use our form on it.

Step 3: We will create an extension of the form 'CustTable' and create a new FormButtonControl named 'HMCustGroup' in the button group 'btngrpCustomerAccounts'.

Step 4: Now we will pass the customer records on the button clicked method. It can be done either by creating a chain of command or by an event handler. We will provide both approaches but personally, I would prefer to use the chain of command.

Firstly we will create a class extension of form control \and pass the arguments to our custom form HMCustGroup
[ExtensionOf(formControlStr(CustTable, HMCustGroup))]
internal final class HMCustGroupTemp_Extension
{
    public void clicked()
    {
        FormControl     formControl = any2Object(this) as FormControl;
        FormRun         formRun = formControl.formRun();
        FormDataSource  formDataSource = formRun.dataSource(formDataSourceStr(CustTable, CustTable));
        Args            args = new Args();
        CustTable       custTable;
        MenuFunction    menuFunction;

        next clicked();

        custTable = formDataSource.cursor();
        args.record(custTable);

        menuFunction = new MenuFunction(menuItemDisplayStr(HMCustGroup), MenuItemType::Display);
        menuFunction.run(args);
    }
}

Secondly, we will copy the OnClicked event of FormButtonControl and paste it in a custom class along with our customized code.
internal final class HMCustGroup
{
    [FormControlEventHandler(formControlStr(CustTable, HMCustGroup), FormControlEventType::Clicked)]
    public static void CustGroup_OnClicked(FormControl sender, FormControlEventArgs e)
    {
        Args            args = new Args();
        MenuFunction    menuFunction;

        CustTable       custTable = sender.formRun().dataSource(tableStr(CustTable)).cursor();
        args.record(custTable);

        menuFunction = new MenuFunction(menuItemDisplayStr(HMCustGroup), MenuItemType::Display);
        menuFunction.run(args);
    }
}
Step 5: We will override the init method of datasource in our custom form to bind a temporary table to populate at runtime. Furthermore, I have used the code snippet below.
public void init()
{
    HMCustGroupTemp tempTable;
    CustTable       custTable;
    CustGroup       custGroup;
    super();
    
    if(element.args().menuItemName() == menuItemDisplayStr(HMCustGroup))
    {
        custTable = element.args().record();
        custGroup = CustGroup::find(custTable.CustGroup);

        tempTable.CustGroupId = custGroup.CustGroup;
        tempTable.CustGroup = custGroup.Name;
        tempTable.insert();

        HMCustGroupTemp.linkPhysicalTableInstance(tempTable);
    }
}

Result: After that, we build and synchronize the solution and test our final outcome.

Go to Account receivable -> Customers  -> All customers
Select a specific customer and press the Customer Group button, as we can see selected customer group is 30

As of now we can see the ID and description of customer group '30' are populated on our custom form:


Comments

Popular posts from this blog

Deploy Package to LCS for Dynamics 365 Finance & Operation

In this blog, we will learn how to extract deployable packages from the Azure DevOps Pipeline and then deploy the specific package to the LCS Standard Acceptance Testing (UAT) Environment. Extract Package from Pipeline and Upload to LCS Step 1 : Go to Azure DevOps ->  Pipelines ->  Recent ->  10.0.37-Gated Build Step 2 : Go to recent check-in Step 3 : Go to published Step 4 : Click on AXDeployableRuntime_7.0.7068.67_2023.12.6.1.zip Step 5 : After downloading the Deployable package Go to Lifecycle Services -> Asset library Step 6 : Go to Software deployable package Step 7 : Navigate and select Software deployable package and select the  + button to add the package to the folder and confirm. Refresh the screen and wait for the package to get validated, the tick will appear once validated. Note: The package will be successfully uploaded to the LCS Environment after the above step. Now we will deploy this package to the Standard Acceptance Testing (UAT) environment. Deploy Pack

Using Complex Ranges on Date Fields in Query

In some of the scenarios,  we want to filter out the from-date and to-date ranges on the basis of different fields and  we are not getting the outcome in which we want to apply the AND/OR clause between date ranges on different date fields and we cannot acquire this result using out-of-the-box query classes. So we have applied complex date ranges to get the desired outcome: void initQuery() { Query                          query; QueryRun                queryRun; QueryBuildDataSource      qbdsProjPeriodLine; QueryBuildRange rangePeriodId; query = queryRun.query(); qbdsProjPeriodLine = query.dataSourceTable(tableNum(ProjPeriodLine)); if (periodFrom && periodTo) { qbdsProjPeriodLine.addRange(fieldNum(ProjPeriodLine, PeriodFrom)).value(strFmt('((%1.%2 >= %4) && (%1.%3 <= %5))',                                  qbdsProjPeriodLine.name(),