During a recent solution deployment from sandbox to production we encountered the following error:
You cannot complete this action for this component because of the configuration of its managed properties. : Attribute
Since the changes in this solution where quite limited, we were able to quickly identify the problem.
So what happened?
Our sandbox environment is already on the 2019 wave 2 release.
One of the changes added to the solution was the addition of a new field on pricelist item, something which wasn’t possible before this release.
Visually it’s very subtle, but before wave 2 the button is grayed out:
After wave 2 deployment:
Having a closer look at the documentation states,
“Administrators can use additional customization options on the price list item entity.”
Which is a nice addition, but one we totally overlooked during our upcoming changes review.
The solution (workaround..)
Since the 2019 release wave 2 is deployed to our sandbox without encountering any problems in the day to day tasks/usage, we opted to also apply it to our production environment. After which importing the solution went without any problem, so no more “You cannot complete this action for this component because of the configuration of its managed properties. : Attribute”.
If you make use of features that are part of the wave 2 release during development… Be prepared to deploy this release to production.Or postpone the deploy of these changes to a point your organization is ready for wave 2. While most of the features will be more clear when used this one quietly sneaked in without us realizing…
Nevertheless are the additional customization options on price list item are a great addition, which really simplified our solution design.
Let’s consider it part of the wave 2 learning. Maybe less obvious then Autopopulating lead information .But definitely a good addition for many upcoming solution designs!