Download Salesforce Change Set package.xml

How to install an extension Open in Chrome Web Store

CRX ID

olkmefomaellbafiabkljcemiljkkbeh

Status

Live on Store

Description from extension meta

This extension will add Download button on Inbound/Outbound Change Set page allowing you to download package.xml of its components.

Image from store

Download Salesforce Change Set package.xml

Description from store

********* v8.2 (9 Sep 2024)*********
- Enhanced Options Page.

********* v8.1 (1 Feb 2024)*********
- Added security enhancements

********* v8.0.0 (12 Dec 2023)*********
- Updated manifest to v3.0

********* v6.0.0 (4 Aug 2020)*********
- Added lightning support and code fixes.

********* v5.0.0 (2 Aug 2019)*********
- Enhanced logic to display button all the times, in both inbound and outbound changeset

********* v4.0.0 (29 Mar 2019)*********
- Fixed intermittent issues of button disappearing
- Fixed issue of the button not appearing on Inbound changeset
- Added feature to generate package.xml even if the user is not on the 1st page of a list of components.

As always, do share valuable feedback. If you have any query please raise a ticket @ http://support.satrangtech.com/

To explore all our Salesforce AppExchange apps, please visit: https://satrangtech.com/apps.htm

For detailed release notes, please visit: https://docs.google.com/document/d/1jClOrTu0fP0_8iZjKbFa-V-b4_85Lpp_DrxYSiEhs14/edit

Latest reviews

Adith Krishna 2025-03-27: Custom Fields do nor have a __c or the object name . Page layout also does not have the custom object name. Custom metadata does not match workbench
Jeremiah Albright 2024-08-26: Usable as a starting point, but doesn't work out of the box. 2nd XML Line with package tag ending with : " when it should be > and certain entity types are not named properly such as CustomField as customfielddefinition, also version 47 is pretty outdated, and numerous other issues that non-Salesforce Devs wont be able to fix easily
Dipa Bhattacharjee 2022-09-27: This generates faulty package.xml
Dipa Bhattacharjee 2022-09-27: This generates faulty package.xml
Will M 2022-09-09: Seems like it still doesn't work for Custom Fields. The field names were present in the XML but no attributes.
Will M 2022-09-09: Seems like it still doesn't work for Custom Fields. The field names were present in the XML but no attributes.
Kyle Handley 2020-10-15: Good idea, some bugs.
Kyle Handley 2020-10-15: Good idea, some bugs.
Maggie Alberts 2020-09-03: Unfortunately, I didn't even get a valid XML file, much less a valid package. I just had 1 Custom Object, 12 Custom fields and 1 Process Builder. The XML was not well-formed, the tags were not right and the API names were not used.
Maggie Alberts 2020-09-03: Unfortunately, I didn't even get a valid XML file, much less a valid package. I just had 1 Custom Object, 12 Custom fields and 1 Process Builder. The XML was not well-formed, the tags were not right and the API names were not used.
Subhash Atluri 2020-07-29: This is good
Subhash Atluri 2020-07-29: This is good
Toufik 2019-09-17: Hello The add-on is missing multi-language support : for instance, when you download a package.xml in french, the type name for Apex classes is ClasseApex instead of ApexClass It seems also that it doesn't download profiles into the package file Thanks
Toufik 2019-09-17: Hello The add-on is missing multi-language support : for instance, when you download a package.xml in french, the type name for Apex classes is ClasseApex instead of ApexClass It seems also that it doesn't download profiles into the package file Thanks
Patrick Visniewski 2019-09-05: it doesn't work for custom fields or record types basically it created a generic section for each and just listed the dev/api name for each but lacked all object reference so the download of metadata skipped them completely So for example a change set with a field named "Trade" on multiple different objects just resulted in this, which failed completely because it has no information about which objects the fields are on <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <name>CustomField</name> </types> <version>44.0</version> </Package>
Patrick Visniewski 2019-09-05: it doesn't work for custom fields or record types basically it created a generic section for each and just listed the dev/api name for each but lacked all object reference so the download of metadata skipped them completely So for example a change set with a field named "Trade" on multiple different objects just resulted in this, which failed completely because it has no information about which objects the fields are on <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <members>Trade</members> <name>CustomField</name> </types> <version>44.0</version> </Package>
Huilong “Eddy” Zhuo 2019-08-13: The download button work only in classic but not in lightning platform. Thank you for creating this tool for us developers!
Huilong “Eddy” Zhuo 2019-08-13: The download button work only in classic but not in lightning platform. Thank you for creating this tool for us developers!
Maciej Szymczak 2019-08-09: This is great!
Maciej Szymczak 2019-08-09: This is great!
Jay Martinez 2019-07-15: No button
Jay Martinez 2019-07-15: No button
Chirag Joshi 2019-05-11: First of button does not appear automatically, one have to click the extension icon and then again move the page, second the field name object name are wrong in package file which is generating an error, so basically useless
Chirag Joshi 2019-05-11: First of button does not appear automatically, one have to click the extension icon and then again move the page, second the field name object name are wrong in package file which is generating an error, so basically useless
Yi Tan 2019-03-08: The concept is really good. However, I can't find button anywhere on the inbound change set page after I installed the extension. Please instruct how to use it
Yi Tan 2019-03-08: The concept is really good. However, I can't find button anywhere on the inbound change set page after I installed the extension. Please instruct how to use it
Mark Liu 2019-01-24: This is awesome... Thank you!!
Mark Liu 2019-01-24: This is awesome... Thank you!!

Extension Actions