Dynamics 365 Finance & Operations Talk

Compare Records D365FO & AX 2012

How to compare two records buffer field to field.

public static container compareRecords(Common _record1, Common _record2)

{

SysDictTable dictTable = new SysDictTable(_record1.TableId);

SysDictField dictField;

FieldId fieldId, extFieldId;

container ret;

int i, j;

;

if (_record1.TableId != _record2.TableId)

return conNull();

for (i=1; i<=dictTable.fieldCnt(); ++i)

{

fieldId = dictTable.fieldCnt2Id(i);

dictField = new SysDictField(_record1.tableId, fieldId);

if (!dictField.isSystem())

{

for (j=1; j<= dictField.arraySize(); ++j)

{

extFieldId = fieldId2Ext(fieldId, j);

if (_record1.(extFieldId) != _record2.(extFieldId))

{

ret += [extFieldId, _record1.(extFieldId), _record2.(extFieldId)];

}

return ret;

}

For Demo purpose you can use below code in job/runnable class.

static void demoCompareRecords(Args _args)
{
    VendTable vendTable_1 = VendTable::find('ABC'); 
    VendTable vendTable_2 = VendTable::find('XYZ'); 
 
    container   con;
    int         i;
    ;
 
    con = MyClass::compareRecords(vendTable_1 , vendTable_2 );
 
    for (i=1; i<=conLen(con); i+=3)
    {
        info(strFmt("%1, %2 ,%3"
                   ,fieldId2Name(tableNum(VendTable), conPeek(con, i))
                   ,conPeek(con, i+1)
                   ,conPeek(con, i+2)
                   )
             );
    }
}

Pass field value from SalesTable to CustTrans in AX 2012 & D365FO

Pass field value from SalesTable to CustTrans in AX 2012 & D365FO

AX 2012

Following are the steps to pass the value from Sales Table to custtrans.

1) Create a new field (If not already existing)

2) Create the parm method for that field on CustVoucher class

3) Assign value to this parm method in SalesInvoiceJournalPost.postCustVend() method by using the salesTable buffer

4) Add the code for assigning the variable value(or the parm method value) in CustVoucher.initCustVendTrans() method

And now post an invoice and go to custTrans table to check the field value.

Source AX-2012

D365FO

Add the field in SalesTable

Add the field in CustTrans

Create Extension class of SalesInvoiceJournalPost

Override postCustVend method using coc

[ExtensionOf(classStr(SalesInvoiceJournalPost))]

final class SLD_SalesInvoiceJournalPost_Extension

{

    /// <summary>

    ///   Performs the customer related postings.

    /// </summary>

    protected void postCustVend()

    {

        CustTrans                   custTrans;

        Name                        ecomMethodOfPayment = this.salesTable.SLDTenderTypeName;        // getting E-Com method of payment from Sales order

        next postCustVend();

        // getting the customer transaction

        custTrans                   = CustTrans::findByVoucher(this.custInvoiceJour.LedgerVoucher);

        custTrans.selectForUpdate(true);

        // updating the customer transaction

        ttsbegin;

        custTrans.SLDTenderTypeName = ecomMethodOfPayment;

        custTrans.update();

        ttscommit;

    }

}

Please feel free to contact me if you are facing any issue during implementation of this blog.

Settle Clearing Entries (Postdated Check) Status

Recently I face the issue that after posting of payment journal status of a post-dated check was not changed from Open to Post. I have lots of R&D in this but no luck,

So I write a batch job where will change the status of custVendPosted check for me.

LedgerJournalTable _ledgerJournalTable;

LedgerJournalTrans _ledgerJournalTrans;

CustVendPDCRegister custPDC;

Counter _counter=0;

while select forUpdate custPDC

where custPDC.PDCStatus==PostDatedCheckStatus::Open

&& custPDC.MaturityDate > systemDateGet()

exists join _ledgerJournalTrans

where custPDC.LedgerJournalTrans==_ledgerJournalTrans.RecId

exists join _ledgerJournalTable

where _ledgerJournalTrans.JournalNum==_ledgerJournalTable.JournalNum

&& _ledgerJournalTable.Posted==NoYes::Yes

{

_counter++;

custPDC.PDCStatus=PostDatedCheckStatus::Posted;

ttsBegin;

custPDC.update();

ttsCommit;

}

info(strFmt("Total Number %1 of records updated on %2.",_counter,today()));

Form Data Source Field Method Override D365FO

In this demo, I will show to create an extension class of form data source Field class and override method through COC.

Here is the annotation code to create COC

[ExtensionOf(formDataFieldStr(FormName, DataSourceName,DataFieldName))]

In this demo, we are using the HcmWorker form and creating Extension of DirPerson Data source field Personal Title..

[ExtensionOf(formDataFieldStr(HcmWorker, DirPerson,PersonalTitle))]

In actual code, you can find the method in the Hcmworker form

[DataField]

class PersonalTitle

{

public Common lookupReference(FormReferenceControl _formReferenceControl)

{

return DirUtility::buildAffixReferenceControlLookup(_formReferenceControl, DirNameAffixType::PersonalPrefix);

}

Here is the code through which we create extensions.

[ExtensionOf(formDataFieldStr(HcmWorker, DirPerson,PersonalTitle))]

final class Demo_Extension

{

}

Here is the code through this we override the method.

[ExtensionOf(formDataFieldStr(HcmWorker, DirPerson,PersonalTitle))]

final class Demo_Extension

{

public Common lookupReference(FormReferenceControl _formReferenceControl)

{

next lookupReference(_formReferenceControl);

return DirUtility::buildAffixReferenceControlLookup(_formReferenceControl, DirNameAffixType::PersonalPrefix);

}

Now perform build in sync on your module. enjoy

Form Data Source Method override COC D365FO

Here is the sample how can you override the form data-source event.

In this demo we have created the extension of HcmWorker form data-source (HcmWorker).

Here is the original method of HcmWorker data-source

public boolean validateWrite()

{

boolean ret;

ret = super();

if (ret)

{

partyForm.validateWrite();

}

return ret;

}

Here is the code to create form data-source extension class

[ExtensionOf(formdatasourcestr(HcmWorker, HcmWorker))]

final class Demo_Extension

{

}

Here is the code to override the data-source method through COC.

[ExtensionOf(formdatasourcestr(HcmWorker, HcmWorker))]

final class Demo_Extension

{

public boolean validateWrite()

{

boolean ret;

ret = next validateWrite();

if (ret)

{

/// do your code here

}

return ret;

}

In last perform Build & Sync.

Important

Feature available from Build 8.1 PU-20

Default parameters can be wrapped In extension classes COC

Default parameters can be wrapped In extension classes

In Build-8.1 you can override the default parameter by using class extension COC.

Code reference

There is the method in HCMWORKER table isEmployee in which you can see the default value set with _validFrom & _validto.

public HcmIsEmployee isEmployee(

utcdatetime _validFrom = DateTimeUtil::utcNow(),

utcdatetime _validTo = _validFrom

)

{

HcmIsEmployee hcmIsEmployee = NoYes::No;

HcmEmployment hcmEmployment;

unchecked(Uncheck::XDS)

{

if (prmisDefault(_validFrom) && prmisDefault(_validTo))

{

select firstonly RecId from hcmEmployment

where hcmEmployment.Worker == this.RecId

&& hcmEmployment.EmploymentType == HcmEmploymentType::Employee;

}

else if (_validFrom == _validTo)

{

select firstonly ValidTimeState(_validFrom) RecId from hcmEmployment

where hcmEmployment.Worker == this.RecId

&& hcmEmployment.EmploymentType == HcmEmploymentType::Employee;

}

else

{

select firstonly ValidTimeState(_validFrom, _validTo) RecId from hcmEmployment

where hcmEmployment.Worker == this.RecId

&& hcmEmployment.EmploymentType == HcmEmploymentType::Employee;

}

if (hcmEmployment.RecId != 0)

{

hcmIsEmployee = NoYes::Yes;

}

return hcmIsEmployee;

}

So we created extension class of Hcmworker with name of Demo_Extension and override the method using COC.

[ExtensionOf(tableStr(HcmWorker))]

final class Demo_Extension

{

public HcmIsEmployee isEmployee(

utcdatetime _validFrom,

utcdatetime _validTo

)

{

HcmIsEmployee hcmIsEmployee = NoYes::No;

HcmEmployment hcmEmployment;

next isEmployee(_validFrom,_validTo);

unchecked(Uncheck::XDS)

{

if (_validFrom == _validTo)

{

select firstonly ValidTimeState(_validFrom) RecId from hcmEmployment

where hcmEmployment.Worker == this.RecId

&& hcmEmployment.EmploymentType == HcmEmploymentType::Employee;

}

else

{

select firstonly ValidTimeState(_validFrom, _validTo) RecId from hcmEmployment

where hcmEmployment.Worker == this.RecId

&& hcmEmployment.EmploymentType == HcmEmploymentType::Employee;

}

if (hcmEmployment.RecId != 0)

{

hcmIsEmployee = NoYes::Yes;

}

return hcmIsEmployee;

}

Now perform build & Sync on your module..

New Module in Dynamics 365 for Finance & Operations

New Module in Dynamics 365 for Finance & Operations

Following are the Steps of Implementation:

Step-1 Create Extension of MainMenu.

Reference screenshot:

Step-2 Create new Menu and add two sub menu in it. enter label as per your requirement.

In demo I Use Name of new menu as FieldManagement
Reference screenshot:

Set Label
Reference screenshot:

Add new Sub-Menu
Reference screenshot:

Step-3 Create Menu reference in MainMenu Extension and set the reference of FieldManagement.
Reference screenshot:

Set reference of FieldManagement
Reference screenshot:

Step-4 Create Display method or Action or Out-Put as per your requirement.
set proper label and make it part of your sub-Menu of FieldManagement.

In demo we used display method
Reference screenshot:

Set Display menu
Reference screenshot:

Step-5 Perform Build of the appropriate module and check on UI
Reference screenshot:

Please feel free to contact me if you are facing any issue while trying to implement on this blog.