cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted

Re: Access Page Context within a component

That is odd - it always has worked for me.

The other way I've seen it done is:

context.page.entityId

but apparently this isn't going to be the supported way.

Highlighted
Advocate IV
Advocate IV

Re: Access Page Context within a component

I have been using below code to access entityId and entityTypeName

context.mode.contextInfo.entityId
context.mode.contextInfo.entityTypeName

But I had to use

@ts-ignore

to make it work.

Highlighted
Frequent Visitor

Re: Access Page Context within a component

Thanks,

 

It's working. Anyway can I access the Form context in the same way ?

 

var formContext = executionContext.getFormContext();

// get formContext // use formContext instead of Xrm.Page

var firstName = formContext.getAttribute("firstname").getValue();

var lastName = formContext.getAttribute("lastname").getValue(); console.log(firstName + " " + lastName);

Highlighted
Post Prodigy
Post Prodigy

Re: Access Page Context within a component

If you have to access the fields why not use manifest file and use them in control and you can bind them back if you need manipulation to be done and then send it to fields .

Highlighted

Re: Access Page Context within a component

@zsoltzombik Using the formContext in this way isn't supported - although it does work. 

The intension is for the PCF component to be decoupled from the form and only use the parameters to pass data back and forth.

That said, some attribute types are not supported such as Lookups (coming soon), ActivityParty, Customer Fields.

 

For theses, the 'official guidance' is to use a text field to serialise the values back and forth - but that is really awkward and personally until they are supported, I think it's fair to use the form context *for those specific field types* until then - it will be easy to replace out the code once supported.

Highlighted

Re: Access Page Context within a component

It's worth re-inforcing that the the form context won't be there when embedding in Canvas Apps - perhaps stating the obvious!

Highlighted
Frequent Visitor

Re: Access Page Context within a component

Resurrecting an old thread and I've picked out Scotts post as I've tried both of these to no avail. In init, entitytypename is undefined but it's then defined in updateView - so my question is does anyone know of a way of accessing that data at init level?

Highlighted

Re: Access Page Context within a component

I'm not sure that init should have access to the actual data context - it's more an event that allows for starting any setup of your component - updateView is where the data is available for you to bind to. 

 

If you look at the description of init it does imply this:

"Used to initialize the control instance. Controls can kick off remote server calls and other initialization actions here.

   * Data-set values are not initialized here, use updateView."
 
 
Highlighted
Frequent Visitor

Re: Access Page Context within a component

My bad for not reading the description - I guess my gut was because I wanted to load a bunch of metadata in init and have it stored for regular use later on.

 

Guess I can handle it a different way, just wasn't my go to code structuring.

 

Thanks as always Scott.

Helpful resources

Announcements
secondImage

Demo-Extravaganza 2020

Check out these cool Power Apps & vote on your favorite!

secondImage

Community Highlights

Check out whats happening in Power Apps

secondImage

Community User Group Member Badges

FIll out a quick form to claim your community user group member badge today!

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Users online (10,923)