cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Jochen365
Level: Powered On

Creating Activity Type Records With PowerApp not possible due to Metadata Error in CDM / PowerApp

I want to write a PowerApp that creates a new Activity Record in Dynamics 365 CE / CRM. Activity Records can be Phone Calls, Email Records, but also Notes containing files/attachments. They have a special field called "regarding": It specifies to which actuall record an activity record belongs. For example, this could be a lead, an opportunity or basically any custom entity. As this field can point to different tables, CRM needs not only the reference to the target record (which is a GUID), but also to the target table. This can be specified in CRM as Entity Type Name ("accounts", "leads", ...) or entity type code (1,2,3, ...). Now I try to create an activity record using PowerApps as shown below:

 

Patch(Notizen, Defaults(Notizen), {subject:"Test", notetext:"Test", _objectid_value:Gallery1.Selected.leadid, _objectid_type:"leads", filename:"img.jpg",documentbody:""})

 

The relevant fields are _objectid_value and _objectid_type. The first contains the GUID to the targetet lead, the second the entity type. However, PowerApps calls out an error: "The type of this argument '_objectid_type' does not match the expected type 'GUID'. Found type 'text'".

 

This is obviously wrong: The type in this context in CRM is not and has never been GUID. It has to be number or text. I verified this behaviour in different environements with different regarding target entities and different activity types - all wrong with the same error. It doesn't even matter whether I connect via Dynamics Connector or CDS connector.

 

Some forum/blog entries already mention this problem - for example this one:

https://www.inogic.com/blog/2019/02/populate-multi-entity-lookup-fields-of-dynamics-365-ce-in-powera...

 

The proposed solution is to turn off advanced setting "Use GUID data type instead of strings". However, this option is no longer available. Other options didn't have the desired effect.

 

Does someone know an up-to-date workaround? And could this bug please be fixed? The proxy type generator for Dynamics should simply respect the fact that regarding fields (and some others) have a string element detailing the target table.

 

Thanks in advance!

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

Follow PowerApps on Twitter

Stay Up-to-Date by following PowerApps on Twitter

Top Community Contributors for July 2019

Top Community Contributors for July 2019

Let's thank our top community contributors

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

FifthImage

Dynamics 365 and Power Platform April 2019 Release notes

Features releasing from April 2019 through September 2019!

Top Kudoed Authors
Users Online
Currently online: 67 members 3,909 guests
Please welcome our newest community members: