We got this error while trying to save the form which uses the PCF Control. This was because the name of the property was changed And the updated solution was imported, while the control on the form was still referring to the old property name. Fix is straightforward, remove the field using that control with … Continue reading “Microsoft.Crm.CrmException: Property ‘x’ isn’t declared on…
Continue Reading Nishant Rana’s Article on their blog
Microsoft.Crm.CrmException: Property ‘x’ isn’t declared on the control manifest in Microsoft Dynamics 365
We got this error while trying to save the form which uses the PCF Control. This was because the name of the property was changed And the updated solution was imported, while the control on the form was still referring to the old property name. Fix is straightforward, remove the field using that control with…
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE7 May 2024Use Filter Array action to remove values from an array variable – Power Automate
- Dyn365CE6 May 2024Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)