I get these error trying to deploy just our Account.object file to another Org: BUILD FAILEDĮrror: objects/Account.object(10881,15):Cannot modify managed object: entity=Web object definition that the Migration Tool can't/won't deploy. The problem with this approach is that there are multiple fields included in the. It would be great to be able to include the Account.object file in the deployment package when there's been a new field added or modified so there doesn't have to be manually editing of the object file each time. I want to get away from new fields having to be setup manually or managed through change sets. Account.object) in the package when they have fields that can't be deployed. I've managed to get this all working with svn, the Migration Tool, and cruise control, but my main issue happens when including object definition files (e.g. My goal at the moment is to be able to automatically retrieve check-ins to our development feature release branch and then automatically deploy them into the QA Org for further testing. I'm trying to add a level of automation to our development processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |