![]() There's one more file we need to create that's required by the tool, build.xml. Now that we have a directory with both files in it, and we have versions of those files that basically do nothing, let's get ready to run the tool. But the template's destructiveChanges.xml contains placeholders-but still basically does nothing.ĭrozBook:xede-sf-template tgagne$ cat del/package.xmlĭrozBook:xede-sf-template tgagne$ cat del/destructiveChanges.xml The package.xml file is the same empty version as before. It seems odd to me, but the migration tool requires both the destructiveChanges.xml AND a package.xml to reside there. The repo includes a directory named "del" (not very imaginative) and inside it are the files destructiveChanges.xml and package.xml. ![]() rwxr-xr-x 1 tgagne staff 563 destructiveChanges.xml Each repository is forked from xede-sf-template.ĭrozBook:git tgagne$ ls -lR xede-sf-template The former is new and the latter is NOT the same file that usually appears in the src/ directory.Īt Xede, we create git repositories for our projects. In a few minutes we'll execute "ant undeplo圜ode," but we've a few items to take care of first.įor me, the first problem was where to put the files destructiveChanges.xml and package.xml. ![]() So how do we execute destructive changes? The short answer is using Salesforce's migration tool. The only difference between them is still the tag. In package.xml we're synchronizing a class and in destructiveChanges.xml its a class we want to remove from our org.Īs a percentage, the two files are more similar now than they were before. Let's look again after we add a class to each. The only difference between them is destructiveChanges doesn't have a tag. The easiest way to see how they're identical is to look at what each of them looks like empty. The difference between them is package.xml enumerates the stuff you want to synchronize between your org and your development environment and destructiveChanges.xml enumerates the items you want to obliterate (or delete) from whatever org you point it at. Both files have nearly identically formats. If you're familiar with developing on the Salesforce platform using Maven's Mate or Eclipse, you're probably already familiar with package.xml. from an org, or from multiple orgs you've probably come across documentation about destructiveChanges.xml. If you've ever had a need to remove a bunch of custom objects, fields, pages, classes, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |