Override standard Lookup and construct tree structure in Category Id field. and Process while Modifying KGSPMICategoryHierarchy field

Override standard Lookup and construct tree structure in Category Id field. and
 Process while Modifying KGSPMICategoryHierarchy field



class KGSPMIEcoResProductParametersEventHandler
{
    /// <summary>
    /// Created by Naren on 11/12/2019
    /// Project: KGSPMIProdMasterToMagento
    /// Override standard Lookup and construct tree structure in Category Id field.
    /// </summary>
    /// <param name="sender"></param>
    /// <param name="e"></param>
    [FormControlEventHandler(formControlStr(KGSPMIIntegrationParameters, MagentoHiearchy_MagentoCategory), FormControlEventType::Lookup)]
    public static void MagentoHiearchy_MagentoCategory_OnLookup(FormControl sender, FormControlEventArgs e)
    {
        FormControlCancelableSuperEventArgs event = e as FormControlCancelableSuperEventArgs;
        FormControl                         productCategory = sender.formRun().design().controlName(formControlStr(KGSPMIIntegrationParameters, MagentoHiearchy_MagentoCategoryHierarchy));
        EcoResCategoryHierarchyId           ecoResCategoryHierarchyId = str2Int64(productCategory.valueStr());
        if(ecoResCategoryHierarchyId)
        {
            EcoResCategoryHierarchy  categoryHierarchy  = EcoResCategoryHierarchy::find(ecoResCategoryHierarchyId);
            EcoResCategory::lookupCategoryHierarchy(sender,categoryHierarchy);
        }

        event.CancelSuperCall();
    }
    /// <summary>
    /// Created by Naren on 11/12/2019
    /// Project: KGSPMIProdMasterToMagento
    /// Process while Modifying KGSPMICategoryHierarchy field.
    /// </summary>
    /// <param name="sender"></param>
    /// <param name="e"></param>
    [FormControlEventHandler(formControlStr(KGSPMIIntegrationParameters, MagentoHiearchy_MagentoCategoryHierarchy), FormControlEventType::Modified)]
    public static void MagentoHiearchy_MagentoCategoryHierarchy_OnModified(FormControl sender, FormControlEventArgs e)
    {
        FormDataSource              ecoResProductParamters_ds = sender.formRun().dataSource();
        FormControl                 productCategory = sender.formRun().design().controlName(formControlStr(KGSPMIIntegrationParameters, MagentoHiearchy_MagentoCategoryHierarchy));
        EcoResCategoryHierarchyId   ecoResCategoryHierarchyId = str2Int64(productCategory.valueStr());
        if(ecoResCategoryHierarchyId)
        {
            ecoResProductParamters_ds.object(fieldnum(KGSPMIIntegrationParameters, MagentoCategory)).setValue('');
            ecoResProductParamters_ds.object(fieldnum(KGSPMIIntegrationParameters, MagentoCategory)).allowEdit(true);
        }
        else
        {
            ecoResProductParamters_ds.object(fieldnum(KGSPMIIntegrationParameters, MagentoCategory)).setValue('');
            ecoResProductParamters_ds.object(fieldnum(KGSPMIIntegrationParameters, MagentoCategory)).allowEdit(false);
        }  
    }
}

Comments

Post a Comment

Popular posts from this blog

Data entites method calling sequence in D365FO

Data entites method calling sequence in D365FO Here is a sequence of method’s calls during export: 1. initValue 2. validateField 3. validateWrite 4. update 4.1. doUpdate 4.1.1. persistEntity 4.1.1.1. doPersistEntity 4.1.1.1.1. initializeDataSources 4.1.1.1.1.1. initializeEntityDataSource Note: initializeDataSource is called once for each DataSource in Entity. 4.1.1.1.2. mapEntityToDataSources Note: initializeDataSource is called once for each DataSource in Entity. 4.1.1.1.3. saveDataSources 4.1.1.1.3.1. updateEntityDataSource 4.1.1.1.4. mapEntityToDataSource (maybe for another record) 4.1.1.1.5. saveDataSources 4.1.1.1.5.1. updateEntityDataSource for update operation and (insertEntityDataSource for insert) 4.1.1.1.5.1.1. mapDataSourceToEntity 4.1.1.1.5.1.2. doSaveDataSource 4.1.1.1.5.1.2.1. updateDataSource 4.1.1.1.5.1.2.1.1. preupInsertDataSource 4.1.1.1.5.1.2.1.1.1. validateWrite of table 5.0 postLoad Plus: postLoad This method is called during the exp...
Read more

How to Extend Sales Order Update Functionality to Custom Fields in D365 Finance and Operations

Image
How to Extend Sales Order Update Functionality to Custom Fields in D365 Finance and Operations by Bill Thompson | Feb 6, 2019 | Dynamics 365 for Finance and Operations , Dynamics AX My colleague Jeremy Dobler wrote this nice article on how to extend sales order update functionality to custom fields in AX 2012 . In this post, I’m going to show how to implement sales order update functionality to custom fields in Dynamics 365 Finance and Operations, and what changes are necessary when comparing to Dynamics AX. Sales Order Update Functionality D365 Finance and Operations vs. Dynamics AX New Fields Jeremy’s article states the following: “Once you have added the fields to the SalesTable and the SalesLine table and exposed the fields on the SalesTable form, add the new custom field to the HeaderToLineUpdate field group on the SalesTable Table.” In D365FO, the new fields will need to be added via a table exten...
Read more

To generate dimension and find the account value - KGSPMIDimensionUtility

KGSPMIDimensionUtility /// <summary> /// Utility class for Dimensions. /// </summary>   class KGSPMIDimensionUtility { public static RefRecId generateDynamicAccount( LedgerJournalACType _type, str _account) { DimensionDynamicAccountServiceProvider dimensionDynamicAccountServiceProvider; DimensionAttributeValueContract ledgerContract; DimensionStorageResult dimensionStorageResult; DimensionDynamicAccountContract contract; contract = new DimensionDynamicAccountContract (); contract.parmAccountType(_type); contract.parmCompany(curExt()); ledgerContract = DimensionAttributeValueContract ::construct(enum2Str(_type), _account); contract.parmPrimaryDimensionAttributeValue(ledgerContract); dimensionDynamicAccountServiceProvider = DimensionDynamicAccountServiceProvider ::newForDynamicAccountContract(contract); dimensionStorageResult = dimensionDynamicAccountServiceProvider.resolve(); return dimens...
Read more