How to : Increase the height of the grid in D365FO forms

A common requirement in D365FO form design is increasing grid height to cut down on scrolling. This includes standard forms. Changing any property on the form desing doesnt seems to work for many cases. Where it doesnt work at design time. It can be fixed by changing the code for runtime. Below is the simple code change:

void  run()
{
    next run();
    FormGridControl periodGrid; //Grid Contorl
    periodGrid = PeriodStatisticGrid as FormGridControl; // PeriodStatisticGrid is the control name.

     if (periodGrid)

    {
        periodGrid.visibleRowsValue(15); //setting the value to show 15 records.
    }
}

Hope this will be helpful.

Comments

Post a Comment

Popular posts from this blog

How to: Get ledger dimension from string in D 365 FOE

I came across a requirement where financial dimensions were coming in XML from integration and Account number was to be determined using business logic. I had to create a general journal from this integration. So situation is : Find the account number from business login in D 365. Get the financial dimensions from integration. Create a journal line from above info. Code to do above is as follows: DimensionDynamicAccount ledgerAccount; switch(<AccountType>) { case (LedgerJournalACType::Cust) : ledgerJournalTrans.AccountType = LedgerJournalACType::Cust; ledgerAccount = LedgerDynamicAccountHelper::getDynamicAccountFromAccountNumber(<AccountNum>, LedgerJournalACType::Cust); ledgerJournalTrans.LedgerDimension = ledgerAccount; break; case (LedgerJournalACType::Ledger) : ledgerJournalTrans.AccountType = LedgerJournalACType::Ledger; ledgerAccount = LedgerDefaultAccountHelper::getDefaultAccountFromMainAccountRecId(MainAccount::findByMainAccount...
Read more

How to: Use enum values instead of integers in BI reports for Dynamics 365 finance and operations

Image
For most of the BI projects related to Dynamics 365 finance and operations, We need to use BYODW to use Power BI or any other BI tools. As we know, enum fields are stored as integers in SQL, so data populated in BYODW comes as integers instead of the enum value. To display this data either you can hardcode values in SQL statements or in BI tools. Instead, we can use SRSAnalysisEnumsEntity in Dynamics 365 F&O. It exports the data from the SRSAnalysisEnums table which holds all the enum and respective enum elements used in perspective. If the enum is missing from the list then below job can be used to insert the data in SRSAnalysisEnums table. class SRSAnalysisEnumsGenerator {     public static void main(Args _args)     {         SRSAnalysisEnums analysisEnums;         DictEnum currentEnum;         str currentEnumName;         int valueCount;       ...
Read more

How to: Import Bank statements from Azure file storage to Dynamics 365 finance and operation using Power automate (formally flow)

Image
We had a requirement for importing of bank statements in Dynamics 365 Finance and Operations using integration. We achieved this using the recurring data jobs in D 365 and Microsoft Power automate. There are basically 3 parts to all the configuration 1. Azure app for authentication. 2. Data processing group and recurring data job in D 365 3. Power automate app for the integration 1. Azure app for authentication Create an Azure app for authentication as follows:     Search for App registration on  https://portal.azure.com/ Create a new app: Copy the app id, we will need this for configuration in D 365 and flow. Create a new secret and copy it. Copy the value of the secret. Now we have all the required information from the Azure portal. Let us switch to Dynamics 365 F&O. 2. Data processing group and recurring data job in D 365 F&O Configure the Bank statement import setup using the steps mentioned in  https://docs.micros...
Read more