Managed Solutions - Alternate Keys and Managed Properties issue

(0) Share

Report

Posted on by Felipe Barboza de Lima

Hello everyone,

I'm facing some issues trying to import a managed solution into a CRM org, after creating an Alternate Key for an entity that has all the Managed Properties (IsCustomizable property) set to false.

Error message: EntityKey is not supported for non-customzable and intersect entities

At the moment, I am setting all the managed properties to true for that specific entity in order to import successfully, which is not desirable for an ISV. I cannot see a reason for a validation like this, so I am assuming that this is an issue. Does anyone know or have an idea about this?

Version: MS Dynamics 365 on-premise (v8.2.0)

Any feedback will be really appreciated.

Thanks,

Felipe

*This post is locked for comments

All responses (5)

Answers (0)

Felipe Barboza de Lima 15 on at

Like (0)

Report

RE: Managed Solutions - Alternate Keys and Managed Properties issue

Hi Goutam, thanks for your reply.

I've already read this article and there is no details about the issue from this post.
gdas 50,091 Moderator on at

Like (0)

Report

RE: Managed Solutions - Alternate Keys and Managed Properties issue

Hi Felipe ,

You can check here -

https://msdn.microsoft.com/en-us/library/gg309297.aspx?f=255&MSPPError=-2147217396
Felipe Barboza de Lima 15 on at

Like (0)

Report

RE: Managed Solutions - Alternate Keys and Managed Properties issue

Thanks for your reply.

That's exactly what I'm doing, but anyway, this is not desirable and I cannot see a reason for that.
Community Member on at

Like (2)

Report

RE: Managed Solutions - Alternate Keys and Managed Properties issue

An update, the reason the workaround is working is because CRM does not override the "Can be customized" on the entity when the new version of the solution is imported.

So the actual fix or workaround is to set everything to False except "Can be customized" when you have an alternate key created on the entity if you need to deploy it as a Managed solution.
Community Member on at

Like (0)

Report

RE: Managed Solutions - Alternate Keys and Managed Properties issue

We had the same exact issue popping up when we tried to install a CRM managed solution with alternate keys that has "Can be customized = false" on an entity into a new clean CRM instance.

The workaround now is to install a version of the managed solution with "Can be customized = true" and then update it with a new managed solution that has "Can be customized = false". CRM does not complain when it is an update. Not ideal for a ISV.