Answered

Retrieving the ID property of an EntityReference

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi,

I've have just started my adventures in PCF and I have come across a problem I hope someone can help with.

I have created a custom control passing in a dataset which contains an owner column. I am trying to retrieve the id of this owner, by doing the following:

let owner = this._dataset.records[recordId].getValue("ownerid") as ComponentFramework.EntityReference;

TypeScript then offers me the following options in intellisense:

So I choose "owner.id" to get the id.

However, when this code runs this "id" is not the id, but an object containing a property called "guid":

If I try to use owner.id.guid in my TypeScript file I get an error and it fails to build.

Am I doing something wrong here? I am pretty new to TypeScript so probability is high.

Thanks

Jason

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (6)

Answers (1)

Verified answer

Greg Hurlman (MSFT) Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
@Anonymous - It's not you, it looks like you've found a bug in our TypeScript type definition file. To work around it, you can modify the file in your project:

Open <project directory>\node_modules\@types\powerapps-component-framework\componentframework.d.ts.

Modify line 1257 from

id: string;

to

id: { guid: string };

This will allow the TypeScript compiler's typechecking to pass.

I am in the process of getting our type files and documentation updated to reflect runtime reality; will update the thread once those changes have gone through.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
@GregHurlmanMSFT - Looks like there is a similar issue with the entityType property, the actual property name is etn.

I updated line 1262 of the type definition from
entityType?: string;
to
etn?: string;
and it works as expected.

Was this reply helpful? Yes No
Greg Hurlman (MSFT) Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@Anonymous Yep, saw that yesterday as well, thanks! I've got a PR open to update our types; as soon as it goes in, if you update the version number of the powerapps-component-framework package to "^1.2.0" and run npm install again, you'll get the changes.

Was this reply helpful? Yes No
Bhuvita Sisodiya07 78 on at

Like (0)

Report
Copy link

Link copied!

@Greg
Is this issue still open because i am still facing the issue.

Was this reply helpful? Yes No
TekTadhg 4 on at

Like (0)

Report
Copy link

Link copied!

I'm still facing this issue when using version "^1.2.0". Has this fix gone in?

Was this reply helpful? Yes No
TekTadhg 4 on at

Like (0)

Report
Copy link

Link copied!

I was able to get around this by updating the version of "@types/powerapps-component-framework" in my package.json to "^1.3.4"

Was this reply helpful? Yes No