parent.Xrm Deprecation in version 9

(0) Share

Report

Posted on by Balasaheb

700

Hi,

We have created custom html page, in that we used parent.Xrm till now is it working but as per Microsoft parent.Xrm is deprecated in version 9. So what is the alternative for this.

Thanks!

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (0)

Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (0)

Report

Hello,

Can you please provide urls where:

1. Microsoft mentioned that parent.Xrm is supported construction before 9.0.

2. Anouncement of deprecation in v9.0

Was this reply helpful? Yes No
Balasaheb 700 on at

Like (0)

Report

Hi Andrew,

Below is the link where Microsoft metioned about it.

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

Thanks!

Balasaheb

Was this reply helpful? Yes No
a33ik 84,331 Most Valuable Professional on at

Like (0)

Report

Thanks,

What's your scenario? What do you want to access? Xrm.Page or Xrm.Utility?

Was this reply helpful? Yes No
Balasaheb 700 on at

Like (0)

Report

Hi,

We want to acess both Xrm.Page and Xrm.Utility. but we can skip Xrm.Utility because have option in above mentioned url.

We want client url and userid, user language etc.

Thanks!

Was this reply helpful? Yes No
Suggested answer

Tomas Prokop 590 on at

Like (1)

Report

Hi, there is an update for this in docs:

Use of the Xrm.Page object as a static access to the primary form context is still supported to maintain backward compatibility with the existing scripts. Based on the feedback, we understand that the usage of Xrm.Page is high, and it won’t be removed as soon as some other client API methods listed in this section. We encourage you to use the new way of getting form content where possible.

Although Xrm.Page is deprecated, parent.Xrm.Page will continue to work in case of HTML web resources embedded in forms as this is the only way to access the form context from the HTML web resource.

Was this reply helpful? Yes No
Suggested answer

Pawar Pravin 5,237 on at

Like (0)

Report

Hi ,

Can you please debug and check once ?
I'm using it for v9.0 only and its working fine for me as well.

ex.

var lookupItem = parent.Xrm.Page.getAttribute("contact").getValue();

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi,

As per Microsoft website, CRM V9 will support Xrm.Page. But It will be removed in the future.

The alternative API is "ExecutionContext.getFormContext"

Steps:

1. Click on "Pass Execution context as first parameter" in the Event Handker properties

(see image below)

2. Then get the Execution context as a function parameter

eg: function SampleFunction(executionContext){

3. Create formContext variable

var formContext = executionContext.getFormContext();

4. Replace Xrm.Page with formContext

// var asset=Xrm.Page.getAttribute("sample_asset");

var asset = formContext.getAttribute("sample_asset");

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Microsoft will publish an alternative at the time of removal. As of now we are still good to use Xrm.Page

Was this reply helpful? Yes No
Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (0)

Report

Hi everyone,

Microsoft have published a replacement Client API called getFormContext and information on it is available here. Xrm.Page will continue to be available and supported until its official removal in a future major release of Dynamics 365.

Was this reply helpful? Yes No
Zhenyu Wang on at

Like (0)

Report

So, what is the replacement of parent.Xrm.Page?

I don't think parent.ExecutionContextObj.getFormContext() has value.

Maybe there is another methold?

Was this reply helpful? Yes No