Customizing D365 with event handlers

With Dynamics 365 release we have to do most of the things using extensions and event handlers. You still have an option to over layer code. While creating new package if you choose select existing packages and modified any standard object which belongs to that package, you are doing overlaying.  In previous versions it was not a big  issue but with new release we should stop doing that and instead embrace a practice of doing customizations using extensions and event handlers.
Source code and metadata of model elements can be extended without an over-layering using extensions.
Today I will share some code snippets about how to  do few things while using event handlers
How to get Form Datasource
If you copy form event handler here is how you can get form datasource from XFormRun 

[FormEventHandler(formStr(HcmPosition), FormEventType::Initialized)]
        public static void HcmPosition_OnInitialized(xFormRun sender, FormEventArgs e)
        {

            FormDataSource hcmosition_ds = sender.dataSource(formDataSourceStr(HcmPosition, HcmPosition));
 Or 
FormDataSource                              hcmosition_ds = sender.dataSource('HcmPosition');
        }

If you copy form datasource event you can get form run object from datasource  as below. Once you get form run you can call any form method available on the form.

[FormDataSourceEventHandler(formDataSourceStr(HcmPosition, HcmPosition), FormDataSourceEventType::Created)]
        public static void HcmPosition_OnCreated(FormDataSource sender, FormDataSourceEventArgs e)
        {

            FormRun formRun = sender.formRun() as FormRun;
            
        }

Similarly you can get formrun on a from control event handler using FormControl
[FormControlEventHandler(formControlStr(HcmPosition, HcmPosition_PositionId1), FormControlEventType::Modified)]
        public static void HcmPosition_PositionId1_OnModified(FormControl sender, FormControlEventArgs e)
        {
            FormRun formRun = sender.formRun() as FormRun;

        }

To get control on a form  and make it editable or non-editable 
[FormEventHandler(formStr(HcmPosition), FormEventType::Initialized)]
        public static void HcmPosition_OnInitialized(xFormRun sender, FormEventArgs e)
        {
            sender.design().controlName(formControlStr(HcmPosition, HcmPositionNewPosition)).AllowEdit(false);
            // to get form open Mode
            OpenMode                                    openMode = sender.args().openMode();
        }

Getting  current record
Hcmposition is first datasource  on HcmPosition form  that’s why  gave 1 in datasource.

[FormControlEventHandler(formControlStr(HcmPosition, HcmPositionNewPosition), FormControlEventType::Clicked)]
        public static void HcmPositionNewPosition_OnClicked(FormControl sender, FormControlEventArgs e)
        {

            HcmPosition hcmposition = sender.formRun().dataSource(1).cursor();
        }

Using DataEventArgs to send Validation result 
[DataEventHandler(tableStr(CategoryTable), DataEventType::ValidatingDelete)]
    public static void CategoryTable_onValidatingDelete(Common _sender, DataEventArgs _e)
    {
        CategoryTable categoryTable = _sender as CategoryTable;
        ValidateEventArgs validateEventArgs = _e as ValidateEventArgs;
        boolean ret = true;

        if (categoryTable.UseInProject)
        {
            ProjCategory projCategory = ProjCategory::find(categoryTable.CategoryId);
            ret = projCategory.validateDelete();
        }

        if (ret && categoryTable.UseInExpense)
        {
            TrvCostType trvCostType = TrvCostType::find(categoryTable.CategoryId);
            ret = trvCostType.validateDelete();
        }
        
        if (!ret)
        {
            validateEventArgs.parmValidateResult(false);
        }
    }

Similarly you can use on ValidateFieldValueEventArgs  to send validation result back to Validate Field method
[DataEventHandler(tableStr(LedgerParameters), DataEventType::ValidatingFieldValue)]
    public static void LedgerParameters_onValidatingFieldValue(Common sender, DataEventArgs e)
    {
        ValidateFieldValueEventArgs ve = e;
        boolean isValid = true;
        LedgerParameters ledgerParameters = sender as LedgerParameters;
        #isoCountryRegionCodes
        
        if (ve.parmFieldName() == fieldStr(LedgerParameters, ChineseVoucher_CN) 
            && SysCountryRegionCode::isLegalEntityInCountryRegion([#isoCN]))
        {
            if ((select firstonly RecId from LedgerJournalTrans
                    where LedgerJournalTrans.LedgerVoucherType_CN != 0
                        || LedgerJournalTrans.Voucher_CN != '').RecId != 0)
            {
                // The general journal needs to be empty in order to modify the setup for the Chinese voucher system.
                isValid = checkFailed("@GLS54497");
            }
            ve.parmValidateResult(isValid);
        }
        
    }

More information about customizing using extensions can be found here


Comments

Post a Comment

Popular posts from this blog

Running runnable class through URL in Dynamics 365 for Operations

Hi Everyone , There are multiple ways you can run Runnable class. One way is we can attach it to Menu item and add it to any form and execute it using menu item. Another way is set it up you project as startup object and runnable class as startup object in Visual Studio and run it from Visual studio. Another way of running it is from your browser (IE/Chrome). https:// URL> /?cmp= &mi=SysClassRunner&cls= Parameters: Cmp = Your company name e.g USMF Cls = Your Runnable class name e.g. ShowInvoicedOrderCount https://usnconeboxax1aos.cloud.onebox.dynamics.com/?cmp=USMF&mi=SysClassRunner&cls=ShowInvoicedOrderCount Whenever you want to quickly verify anything this way is very useful and you don’t have to spent time seeing while visual studio opens diagnostic tool and load other windows.
Read more

D365FO Use of FileUpload control to Read CSV file

Image
In Dynamics Ax implementation very often we get requirement to upload data using csv files. Although  in Dynamics 365 for operations it can be easily done using data entities and data packages, in this blog we will see how can we use new FileUpload control and design classes to read, download files. In   Dynamics 365 for operations  application runs on cloud and the client is in web , so Microsoft has introduce new process to read files using Azure blob. When we upload file, that file gets uploaded to Azure blob and we have to read that file from Azure blob to retrieve data. Design classes: There are two main types of classes that developers can work with for the file upload control: Upload strategy class  – This class lets developers control various parameters that should be enforced for uploaded files, such as the types of files that a user can upload and the maximum size of a file. It also lets developers determine where and how ...
Read more

D365FO Send Report as email attachment

Hi All , Usually in any implementation project we get request to send Report as a attachment in email.  Below is code going to help you to send  report as an email attachment.  In the below code I am saving report in report archive(DocuRef table ) reading it from DocuRef table  in to bytes and converting it in to memory stream. The memory stream is further I am going to use to  send an email with Subject and body using SysMailerMessageBuilder class. You can use following methods of this class setSubject - To set Subject of the email. setBody -  To Set email body . setFrom - To set sender of the email. sendInteractive - To send interactively. sendNonInteractive - TO send non interactively Args args; SalesInvoiceContract salesInvoiceContract; CustInvoiceJour custInvoiceJourLocal; SRSPrintDestinationSettings SRSPri...
Read more