If we want to use Ant Migration tool to fetch Salesforce Organization metadata info or to deploy some changes to Salesforce, we need to create “package.xml” manually or take help of eclipse. wildcard character (*) doesnt work with some components like report, emailtemplate, dashboard and document. Package.xml must needs to have folder name and files inside folder name. After getting package.xml from eclipse, what if some folder is added into Organization ? We need to update “package.xml” again with help of eclipse or do it manually. Therefore I wanted to automate generation of package.xml completely and came up with this article and below workaround.
I would be using Ant to generate “package.xml” with below steps
Why should I use JSON over XML ? Why JSON is given so importance these days ?
Many questions like these are asked many times by new developers. So, I decided to write this article. However last year I presented same topic and uploaded in SlideShare.
Before Winter12 release, for JSON related stuff we had to depend on external Libraries. However in Winter12, salesforce has added support for JSON natively on force.com plateform. Also, on every release Salesforce is making required changes in JSON library to make it more stable and more usable. I have shared many topics on JSON in past, on which you can have a look.