{"id":5595,"date":"2016-08-18T04:54:21","date_gmt":"2016-08-18T04:54:21","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=5595"},"modified":"2016-08-18T04:54:21","modified_gmt":"2016-08-18T04:54:21","slug":"dynamically-remove-xml-content-from-metadata-before-salesforce-deployment-using-xmltask-video","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/dynamically-remove-xml-content-from-metadata-before-salesforce-deployment-using-xmltask-video\/","title":{"rendered":"Dynamically remove XML content from metadata before Salesforce deployment using xmlTask – Video"},"content":{"rendered":"

Many post about deployment using ANT<\/a> has been posted on this blog like auto backup complete Salesforce instance daily<\/a>, upload Salesforce data\u00a0on FTP Server<\/a>, auto generate package.xml<\/a>, continuous integration<\/a> and so on<\/a>.<\/p>\n

While implementing real Continuous integration<\/a> in Salesforce, we need to perform various adjustments in metadata before deploying it to build server or production instance, many\u00a0automated scripts (automation) are needed. If you need to change ANT scripts or metadata frequently, then it means continuous integration or deployment process in your Salesforce project is not yet fully matured.<\/p>\n

There could be multiple situation where we don’t want some component to be deployed on production and example\u00a0<\/strong>of\u00a0one of them is\u00a0List view<\/em>.\u00a0<\/strong><\/p>\n

When we include any custom or Standard object as a part of ANT deployment<\/a>, it also includes listview<\/em>\u00a0created on that object. It is very common, that developer changes or creates multiple listviews<\/em> for data analysis purposes. In that case, Listview created by customer could we overwritten after deployment and believe me, as a developer or consultant you don’t want to make customers unhappy \ud83d\ude42 .<\/p>\n

In this post, we will discuss how we can tweak Salesforce metadata dynamically in ANT with the help of xmlTask<\/strong><\/a>.<\/p>\n

build.properties<\/strong><\/p>\n

\r\nxmlTaskjarFile=xmltask.jar\r\nroot.dir=C:\\\\Users\\\\Jitendra\\\\Desktop\\\\Blog Demo\r\n<\/pre>\n
In above file,\u00a0root.dir\u00a0<\/em>contains complete path till working folder and\u00a0xmlTaskjarFile<\/em> contains name of jar file downloaded from here<\/a>. This jar file is placed in same location where build.properties exists.<\/p>\n
Build.xml<\/strong><\/p>\n
\r\n<project name="Deployment Scripts" default="removeListViews" basedir="." xmlns:sf="antlib:com.salesforce">\r\n \t   \r\n    <property file="build.properties"\/>\r\n    <property environment="env"\/>  \r\n\t\r\n\t<target name="removeListViews">   \r\n\t\t\r\n\t\t<taskdef name="xmltask" classname="com.oopsconsultancy.xmltask.ant.XmlTask" classpath="${xmlTaskjarFile}"\/> \t\t\r\n\t\t<xmltask source="${root.dir}\/src\/objects\/Account.object" dest="${root.dir}\/src\/objects\/Account.object"> \r\n\t\t\t<remove path="\/:CustomObject\/:listViews"\/> \r\n\t\t<\/xmltask>   \r\n\t<\/target> \t\r\n<\/project>\r\n<\/pre>\n
As shown in above\u00a0build.xml\u00a0<\/em>file, we have defined target by name\u00a0removeListViews.\u00a0<\/em>This target can be called before Salesforce deployment target. It removes any listview found by using\u00a0XPath<\/a>\u00a0from Account Object. Don’t forget to make a note of\u00a0\/:\u00a0<\/em>before\u00a0CustomObject.\u00a0<\/em>I struggled a lot to identify why node is not being removed.<\/p>\n
Download<\/a>\u00a0example of this post.<\/p>\n