error passing default parameters to a form in classic interface but not in unified interface

(0) Share

Report

Posted on by marcelxrm

I feel like I'm doing something fundamentally wrong here.

var entityFormOptions = {};
entityFormOptions["entityName"] = "connection";

var formParameters = {};
formParameters["record1id"] = node.data.id;
formParameters["record1idname"] = node.text;

if (Xrm.Internal.isUci()) {
    formParameters["record1idtype"] = node.data.typename; 
} else {
    formParameters["record1idobjecttypecode"] = node.data.typename; 
}

Xrm.Navigation.openForm(entityFormOptions, formParameters);

The above code works, but:

1) It uses a method from the Internal workspace (Why does record1idtype not work in classic interface?)

2) I'm passing a string entity name to objecttypecode instead of an actual integer object type code (which fails if I do it)

All I'm trying to do is set a default record1 lookup value when I open a new connection form. But it either doesn't work in classic or unified interface, depending on what "type" property I'm setting.

Any help is appreciated.

I have the same question (0)

All responses (5)

Answers (1)

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hello,

I don't see anything wrong in your approach. Different UI-s - different approaches. If you're looking for consistent code try to use createFrom parameter instead - no guarantees but it could work.

Was this reply helpful? Yes No
marcelxrm 20 on at

Like (0)

Report
Copy link

Link copied!

but this will get flagged when submitting to AppSource, won't it?

Was this reply helpful? Yes No
Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

It should not - technically your code doesn't do anything unsupported. In order to check that you can create solution and run App Checker against it.

Was this reply helpful? Yes No
marcelxrm 20 on at

Like (0)

Report
Copy link

Link copied!

Thanks, I'll try running solution checker against it. My only concern is that, per Microsoft docs, the use of Internal namespace functions is unsupported.

Was this reply helpful? Yes No
Verified answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Oh. You mean usage of Xrm.Internal.isUci... that's the other question. Unfortunately Microsoft doesn't provide any other way to detect what type of interface is it...

Was this reply helpful? Yes No