You’re offline. This is a read only version of the page.
Hi.
Our company are in the process of taking ownership of the CRM development process of our CRM 2011 onpremise environment from a 3rd party vendor.
The existing system has a series of managed solutions installed on it (using the 3rd party vendors publisher).
To test the development process, on DEV (a copy of Live) - we created a new Managed solution (using a newly created publisher with a different prefix for use by ourselves).
We made several changes to existing entities.
Then we exported our solution as managed and attempted to import to UAT, getting the error below (the reported savedquery is on the out of the box account entity).
I have seen a few reported reasons for this but most seem to be using the same publisher.
I have a feeling this error may be because our managed solution uses a different publisher than the ones installed already on DEV/UAT/PROD.
Any ideas how to fix this?
Thanks
A managed solution cannot overwrite the SavedQuery component with Id=f2a2f6d4-d862-e111-bf4e-0050568e0011 which has an unmanaged base instance.
The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged SavedQuery component on the target system,
and now a managed solution from the same publisher is trying to install that same SavedQuery component as managed.
This will cause an invalid layering of solutions on the target system and is not allowed.
*This post is locked for comments
But are you sure the earlier vendor solution is managed , it seems like it's part of the unmanaged in target org.
Hi. Thanks for the reply.
I haven't actually changed any of the views on the system at all - but obviously adding the account entity will result in all of its views existing in the customizations.xml file.
The only difference is that I have used a different publisher for my solution (as the publisher previously used was created by a third party vendor and want to use one with our own prefix).
Any thoughts?
Hi. Thanks for the reply.
I haven't actually changed any of the views on the system at all - but obviously adding the account entity will result in all of its views existing in the customizations.xml file.
The only difference is that I have used a different publisher for my solution (as the publisher previously used was created by a third party vendor and want to use one with our own prefix).
Any thougts?
Hello,
Can you confirm if the view you have changed is already part of your target system which is imported in target system using unmanned solution ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (