This extension will add Download button on Inbound/Outbound Change Set page allowing you to download package.xml of its components.
Total ratings
2.73
(Rating count:
15)
Review summary
Pros
- Good idea for generating package.xml
- Useful for developers to download metadata
- Concept is appreciated by users
Cons
- Generates faulty and malformed XML
- Fails to include proper attributes for Custom Fields
- No support for multiple languages
- Download button only functions in Classic, not Lightning
- Does not work correctly for Custom Fields or Record Types
Most mentioned
- Faulty package.xml generation
- Issues with Custom Fields
- Download button visibility problems
- Lack of multi-language support
- Not well-formed XML
Upgrade to see all 27 reviews
Recent reviews
Recent rating average:
2.30
All time rating average:
2.73
Upgrade to see all 27 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
Date | Author | Rating | Lang | Comment |
---|---|---|---|---|
2024-08-26 | Jeremiah Albright | en | 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 | |
2022-09-27 | Dipa Bhattacharjee | This generates faulty package.xml | ||
2022-09-27 | Dipa Bhattacharjee | en | This generates faulty package.xml | |
2022-09-09 | Will M | Seems like it still doesn't work for Custom Fields. The field names were present in the XML but no attributes. | ||
2022-09-09 | Will M | en | Seems like it still doesn't work for Custom Fields. The field names were present in the XML but no attributes. | |
2020-10-15 | Kyle Handley | Good idea, some bugs. | ||
2020-10-15 | Kyle Handley | en | Good idea, some bugs. | |
2020-09-03 | Maggie Alberts | 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. | ||
2020-09-03 | Maggie Alberts | en | 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. | |
2020-07-29 | Subhash Atluri | This is good |
Upgrade to see all 27 reviews