function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Hithesh SaicharanHithesh Saicharan 

Migration issue from sandbox to dev org during package creation

I am planning to create a managed package. Since managed packages cant be created in sandboxes , I created one dev org and tried to move the Profiles and Objects from my sand box to Dev org. But I am always getting below error.
  
18.  objects/Case.object (Case.Language) -- Error: Could not resolve standard field's name. (line 1292, column 13)
19.  profiles/Caseworker.profile -- Error: Unknown user permission: OverrideForecasts
20.  profiles/Intake Worker.profile -- Error: Unknown user permission: AIViewInsightObjects
21.  profiles/Provider Community.profile -- Error: Unknown user permission: OverrideForecasts
22.  profiles/Public Community.profile -- Error: Unknown user permission: OverrideForecasts
23.  profiles/Supervisor.profile -- Error: Unknown user permission: ApproveContract

 
Best Answer chosen by Hithesh Saicharan
VinayVinay (Salesforce Developers) 
Hi Hithesh,

For error 'Could not resolve standard field's name' enable Data.com on destination org.

Unknown user permission error check below references.

https://pavelslepenkov.info/posts/p737
https://theweekendcode.wordpress.com/2019/09/10/deploying-an-entire-salesforce-project-part-2/

Hope above information was helpful.

Please mark as Best Answer so that it can help others in the future.

Thanks,

All Answers

VinayVinay (Salesforce Developers) 
Hi Hithesh,

For error 'Could not resolve standard field's name' enable Data.com on destination org.

Unknown user permission error check below references.

https://pavelslepenkov.info/posts/p737
https://theweekendcode.wordpress.com/2019/09/10/deploying-an-entire-salesforce-project-part-2/

Hope above information was helpful.

Please mark as Best Answer so that it can help others in the future.

Thanks,
This was selected as the best answer
AnudeepAnudeep (Salesforce Developers) 
Probably you have different versions of Salesforce on different orgs or different features enabled.

You can just manually remove permission that doesn't exist on the target organization from each file where it is present

Note: This is not something you can do via ANT and you will have to enable it prior to doing your deployment.  An option would be to remove the OverrideForecasts permission from your XML and then do your push.

Let me know if this helps, if it does, please mark this answer as best so that others facing the same issue will find this information useful. Thank you