You’re offline. This is a read only version of the page.
Announcements
311
In my model-driven app, I'm trying to use Xrm.Navigation.openForm, passing in parameters to set some field values. One of the fields is a "customer" type field named "Payee" whose system name is "cr01_payee". I understand that to set a value for customer fields, you add 3 parameters, like this:
formParameters["cr01_payee"] = result._cr01_payee_value;
formParameters["cr01_payeename"] = result.cr01_Payee_account.name;
formParameters["cr01_payeetype"] = "account";
This works great until I add another parameter for a field named "Payee Type" who's system name is "cr01_payeetype". The entry for this field uses the same parameter name as the 3rd entry for the Payee field and causes errors:
formParameters["cr01_payeetype"] = 100000001; // Choice field
Without creating new fields with different systemnames, any one know a way I can set both values in the parameters without the conflict?
Nope. This is one among many reasons why I have everyone on my dev teams suffix every lookup field with "id" so the usage becomes unambiguous.
"cr01_payeeid";"cr01_payeeidname";"cr01_payeeidtype";"cr01_payeetype"
Some teams I've seen also suffix other field types, such as "code" after every optionset and "num" after every numerical, though I feel that with the exception of lookups this is not generally a meaningful value-add.
Share
Report
All responses (
Answers (
