How do you tell the difference between the Unified interface and the legacy web client in a JS script

(0) Share

Report

Posted on by sbelzile

I have a script that runs in both the legacy UI and the Unified interface. In that script, I need to call some XRM function that behaves differently in the 2 UIs.

The problem is that I cannot figure out a way to tell which UI I am in via code.

How do you tell the difference between the Unified interface and the legacy web client in a JS script?

*This post is locked for comments

I have the same question (0)

All responses (20)

Answers (2)

Verified answer

Ben Thompson 6,350 on at

Like (0)

Report

The only way I'm aware of that works is to use the internal (so unsupported) Javascript function xrm.internal.isuci() .

Was this reply helpful? Yes No
gdas 50,091 Moderator on at

Like (0)

Report

Hello,

Below references will be help you to understand the changes -

crmrocks.com/.../unified-interface-with-scott-durow

community.dynamics.com/.../unified-client-form-properties-cheat-sheet

Was this reply helpful? Yes No
sbelzile on at

Like (0)

Report

Thanks Goutam, but I'm looking for something at code level.

Was this reply helpful? Yes No
Suggested answer

Ben Thompson 6,350 on at

Like (0)

Report

See my comment above for the code you need

As an aside what function is working differently on Unified Interface to the web refresh? Everything should be working the same way...

Equally could you mark the answer as verified so others can find it if they need it.

Was this reply helpful? Yes No
gdas 50,091 Moderator on at

Like (0)

Report

Not sure may be this is what you are looking for -

docs.microsoft.com/.../important-changes-coming

Was this reply helpful? Yes No
sbelzile on at

Like (0)

Report

> See my comment above for the code you need

If that was only for myself or for my company, I would see no problem using this, but the code I'm writing will be shipped to our clients. I am not uncomfortable shipping something not supported.

> As an aside what function is working differently on Unified Interface to the web refresh? Everything should be working the same way...

A few minor things:

1. The problem I currently have is with `Xrm.Navigation.openForm`. I am trying to replicate the behavior of the "email component" in the knowledge articles result list (in Case forms). In the UCI, I can pre-set the recipients of the email by passing an array of lookup values (`to` attribute), which does not work in the legacy client (the OOTB control does have different behavior at that level in the 2 UIs).

2. If I call: `Xrm.Navigation.OpenWebResource('mywebresource.html#f:@objecttype=something")`, the hash parameter is properly transferred to my webresource in the UCI, but not in the legacy web client.

3. I had problems with the encoding of the `data` parameter as well, but this one I was able to go around.

Was this reply helpful? Yes No
Suggested answer

Ben Thompson 6,350 on at

Like (0)

Report

To be honest I'm about to ship it in a product wrapped around a secondary test for Xrm.Page.context.getVersion and will happily have the argument with the product team about why I'm using it - I would prefer not to use the code but I end up with look and feel differences that I'm uncomfortable with unless I do it.

Was this reply helpful? Yes No
Verified answer

sbelzile on at

Like (0)

Report

Good. I logged an idea here: experience.dynamics.com/.../idea to get a supported version.

On my side, I removed the line that required a check, since it was not that important.

Was this reply helpful? Yes No
Nithya Gopinath 17,078 on at

Like (0)

Report

Hi Sebastian,

See: docs.microsoft.com/.../understand-clientapi-object-model

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Arun Vinoth 11,615 Moderator on at

Like (0)

Report
We are using the below snippet to identify is it UCI or not.

function isUCI(){ var globalContext = Xrm.Utility.getGlobalContext(); var t1 = globalContext.getCurrentAppUrl(); var t2 = globalContext.getClientUrl(); if (t1 !== t2) return true; return false; }

Was this reply helpful? Yes No