Best practice error - calling methods on forms

(0) Share

Report

Posted on by AX Techie

995

Hi,

Can somebody help me in fixing the below BP error when calling the custom method in in a form eventhandler.

In source system (AX 2012) it is possible to dynamically call methods where the number and type of the parameters does not match with the method definition. This is not supported in AX 7, where the number and types of parameters have to match. Even if the parameters do match, the late bound call is extremely expensive. Mitigation: Use a class or interface hierarchy to provide a type safe fast call, or use the IS and AS operators to cast to a known type before calling.

Below is the code that I am using.

Kindly help me

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Blue Wang Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Avinash,

Have you tried setting optional parameters in your custom method so that you don't need to match the number of parameters when you call it.

docs.microsoft.com/.../using-optional-parameters

Optional parameters also apply to AX7.

Was this reply helpful? Yes No
AX Techie 995 on at

Like (0)

Report
Copy link

Link copied!

Hi Blue,

Yes I used. But getting this error when I call that method.

Was this reply helpful? Yes No
Blue Wang Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Avinash,

Could you share your custom method code?

Was this reply helpful? Yes No
AX Techie 995 on at

Like (0)

Report
Copy link

Link copied!

public void hsoGetJournalData()

{

LedgerJournalTable ledgerJournalTable;

LedgerJournalName ledgerJournalName;

FormRun element = this;

if (element.args().dataset() == tableNum(LedgerJournalTable))

{

ledgerJournalTable = element.args().record();

ledgerJournalName = LedgerJournalName::find(ledgerJournalTable.JournalName);

this.parmHSOIsRevenueReceiptJournal(ledgerJournalName.HSOIsRevenueReceiptJournal);

this.parmHSOJournalNum(ledgerJournalTable.JournalNum);

this.parmHSOIsJournalPosted(ledgerJournalTable.Posted);

}

}

Was this reply helpful? Yes No
AX Techie 995 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

Still my question is unanswered. Can you please help.

Thanks.

Was this reply helpful? Yes No
Verified answer

Martin Dráb 239,638 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

One option is moving the business logic from the form to a class. Then you can simply call methods by name and you don't need the hack with late-binding.

If you're unable to refactor your code and the form is yours, you can let it implement an interface and call methods through this interface.

Was this reply helpful? Yes No