16

It appears that the deploy package to package.xml validation is case sensitive. If you get a is not in package.xml, double check the case of the object or field in your package.xml. The tricky part about this is that ant retrieve will work just fine, the validation only occurs when doing ant deploy or ant test


10

I'm pretty familiar with the Metadata API and deletion of Package 'definitions' is not supported presently it appears. The only thing i can think is accessing the Delete action via the page URL's, which is not ideal of course since its not supported. I did also try this in destructiveChanges.xml, it did not work sadly. I should clarify, it did not error, ...


8

Yes, GlobalPicklist has been replaced by GlobalValueSet. This is outlined in the relevant documentation and was mentioned in the release notes. Streamlined Metadata API for Picklists We bring you elegance and efficiency with a reimagined Metadata API for picklists, with no wasted elements to clutter your API calls. The new structure clearly ...


6

As per the documentation- Sample package.xml Manifest Files, it looks like you would have to specify the name of objects explicitly: Standard Objects <types> <members>Account</members> <name>CustomObject</name> </types> You cannot use an asterisk wildcard to work with all standard objects; each standard ...


6

Use the describeMetadata call to learn the folder names of each of the types. A Java sample is included: public void describeMetadata() { try { double apiVersion = 21.0; // Assuming that the SOAP binding has already been established. DescribeMetadataResult res = metadataConnection.describeMetadata(apiVersion); StringBuffer sb = new ...


6

I don't believe the intention is for the Developer Console to take over for the Force.com IDE. I had asked a similar question awhile ago after I heard the Force.com IDE may be deprecated. The response from Salesforce was that basically they were working on it, and they have. In September last year, they provided a massive update to the plugin to allow for ...


6

Is it possible just to use hub and DX cli to quickly spin up new scratch org with required configuration, create new user with password and then use it to deploy code in an old-fashioned way using package.xml and ant migration tool? Any restriction here or could we treat scratch org as normal sandbox after creation? You can make a package.xml-based ...


6

First, as I said before, don't merge directly in to master. Also, don't do crazy diffs and stuff to try and make it work this way. You're right to be concerned about automatic package.xml generation, it's a non-trivial task at best. I recommend reading A successful Git branching model (not my blog/post, just really useful!) for a better branching strategy. ...


5

Wow this is strange! I've never seen this before either, mainly because i create my project in such a way to avoid downloading this, see below. Regarding what this is, it is most interesting, more so the contents of them, typically these are contents of managed packages in your org. But looking through some in my org reveals some very interesting package.xml ...


5

You must add the CustomLabel type to your package.xml file: <types> <members>*</members> <name>CustomLabel</name> </types> Once that is saved, refresh your src file from server.


5

List view fetching for custom metadata types are bit tricky. If you retrieve a List View on a Custom Setting/Custom Metdata along with the Custom Setting/Metadata object when using Metadata API in a single transaction, the List View information is not retrieved. You have to retrieve both separately. Suppose: MetaData Object Name: MyObject__mdt ...


4

there is this awesome tool on github https://github.com/amtrack/force-dev-tool You can use following command to create a changeset: $ git diff master feature/vat | force-dev-tool changeset create vat


4

Of those I use most commonly: type path ApexClass /src/classes ApexComponent /src/components ApexPage /src/pages ApexTrigger /src/triggers CustomLabel /src/labels StaticResource /src/staticresources The rest can be found in the documentation, as noted by @sfdcfox.


3

Include your objects in that package.xml and you will be golden. Here is what your package.xml should look like: <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>Account</members> <members>AccountContactRole</members> <members>Activity</members> <...


3

After learning some simple shell commands, I wrote some shell scripts to generate package.xml dynamically based on git commit and it works well! Now we can deploy codes only when they are changed! #!/bin/bash echo "Shell Start to generate package.xml ..." metaItems=(`git diff --name-status $GIT_PREVIOUS_COMMIT $GIT_COMMIT | xargs`) echo "Shell: generate ...


3

I don't believe you can actually recreate the Change Set, as such... but I'm not sure you need to. Workbench can do both the retrieve and deploy using the package you're speaking about. You can retrieve the entire package using Workbench by going to Migration | Retrieve, and entering the change set name as the package name. You can retrieve the package, ...


2

To get Custom Labels and Validation Rules you have to add CustomLabels and CustomObject as below in the package XML. The validation rules are part of objects and when you add CustomObject you will get all the validation rules part of object configuration itself. Hope this helps. Package XML <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="...


2

Since you specifically asked for a tool, and we offer a free 30 day trial, I don't feel too spammy by suggesting you use Gearset which is a service my team and I have built to simplify release management for Salesforce. For your use case, you can do a comparison between your dev sandbox and production, and then export that to Excel. It is free, will take ...


2

See this note: You can’t retrieve the starting number of an auto-number field through Metadata API. To specify a Starting Number while deploying, add a startingNumber tag for your field to your package.xml file. For example: 42 If you deploy without specifying a Starting Number value in your package.xml file, the default starting number for standard ...


2

You've missed <name>CustomObject</name>, between types and members <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>Candidate__c</members> <members>Interview__c</members> <members>Interviewer__c</members&...


2

ConnectedApp, AuthProvider and NamedCredential are supported types to deploy by means migration tool. So answer is: yes, it is possible to migrate named upper metadata by means of ant migration tool. Check all supported types in documentation


2

Object's translations are retrieved only for object's custom metadata, which is included into package.xml For example, if package xml contains only one custom field and one page layout, then translation will be returned for that field only For example: <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"&...


2

For .homePageLayout files extracted into a homePageLayout folder if you want to retrieve a specific layout: <types> <members>Service Home</members> <name>HomePageLayout</name> </types> If you want to retrieve all layouts: <types> <members>*</members> <name>HomePageLayout</name&...


2

Yes. The Package object can update the contents of a package. The format is identical to the package.xml file. You can use Force.com IDE, Ant, Salesforce DX, etc.


2

I would use Eclipse / Mavensmate to create the package.xml file, it's the easiest way to gather all components. Tquila's Package.xml Builder is also handy.


2

It needs to be "Folder Name/Template Name", like this: <types> <members>Folder_Name/Unique_Name_Of_Template</members> <name>EmailTemplate</name> </types> This is mentioned in EmailTemplate, with a demo: <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> &...


2

Simply include Queue type in your package.xml. Then retrieve it from your sendbox and migrate to another <types> <members>NameOfDesiredQueue</members> <name>Queue</name> </types> after retrieval new file NameOfDesiredQueue.queue will be created in src/queues folder. If you want to add members, add new elements to ...


2

It's part of the object metadata that's pulled down when you extract the CustomObject entity with the Metadata API. enableReports is a top-level key under <CustomObject>: <enableReports>true</enableReports> Your package.xml must contain an entry along the lines of <types> <members>My_Object__c</members> <name&...


2

You can try with: <types> <members>Quote-Quote Layout</members> <name>Layout</name> </types> For any unpackaged object and page layout format will be <Object Name>-<Layout Name> For object and pagelayout which has namespace format look like <namespace>__<Object Name>-<namespace>__&...


2

In case if you want to retrieve layout from managed package, you need to specify package prefix as well. Below you will find 2 examples, first one is managed layout for managed object, and second one is unmanaged (custom) layout for managed object, abc__ is namespace prefix, : <types> <members>abc__object__c-abc__object Layout</members&...


Only top voted, non community-wiki answers of a minimum length are eligible