Share
Report
2We're trying to export all customizations from Production Org to Development Org to use as our dev environment. Both are on the same rollup. The problem is that the Production Org we want to export from has managed solutions from other ISVs. We do not want to purchase licenses to import the managed solutions to the Development Org, so we have eliminated the managed solutions components by manually removing them from the xml file. Is this the recommended approach? In the future, we will be exporting the customizations from Development Org to the Production Org. Will this cause any issues with the managed solutions we have eliminated from the xml file?
Also, we are experiencing some errors regarding crm created entities/fields:
Error 1. On RecurringAppointmentMaster entity: Updating Appointment.subject.Length but it's not valid for update. Original value:700. New value:400. - In both the Prod and Dev orgs, the subject length is 200, so I'm not sure what this error is referring to.
Error 2. On Service entity: The evaluation of the current component(name=Entity, id=8f9d8c85-8523-4017-8afb-002661a8ddbb) in the current operation (Update) failed during managed property evaluation of condition: The evaluation of the current component(name=Entity, id=8f9d8c85-8523-4017-8afb-002661a8ddbb) in the current operation (Update) failed during managed property evaluation of condition: Microsoft.Crm.BusinessEntities.AttributeManagedPropertyCondition
There are no 3rd party components linked to the service entity
Error 3: On entity relationship opportunity_customer_accounts : Cannot update RequiredLevel of attribute CustomerId to SystemRequired
I did notice that in the prod org, the requirement text says "System Required" and in the Dev org, the system requirement text says "Business Required", but not sure why the difference or best approach to fix.
Thanks for any advice.
*This post is locked for comments
All responses (
Answers (
