What is a one sentence summary of your feature request?
Create a button to Import a CSV file to attach Metadata to a JIRA ticket or a Change Request
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
We use Copado for deployment and they are not able to generate an XML file. We are able to create a report that includes the:
-list of impacted metadata
-APi names of impacted metadata
Then we can export it to excel or CSV
Can you add a feature just like “import XML package” that would be to import an CSV.
What should the CSV (Salesforce report) have.
How do you currently solve the challenges you have by not having this feature?
Currently there is no solution. We have to manually input the User story metadata components into Netwrix Salesforce.
Upload any supporting images that you think should be considered in this idea.
Hi @rnaik, Welcome to the Community! My understanding is that Copado does generate the standard Salesforce XML package files that should be usable with our Change Request.
Since this functionality is already available through Copado’s XML output, we won’t be moving forward with support for CSV imports. That said, if you’re not seeing the XML packages where you expect them, it may be worth reaching out to Copado support for some guidance—they should be able to help confirm where those files are produced and how best to access them.
Of course, if you run into issues importing the XML into Netwrix Platform Governance/Strongpoint, our team would be happy to walk you through the process: https://www.netwrix.com/support.html
We really appreciate your input and the chance to better understand your workflow as it helps us keep the product aligned with how our customers are working.
@Valerie.Callahan Thank you for your response. We are currently using Copado CI/CD to create user stories and add metadata components for deployment. However, Copado lacks the functionality to export these components as an .xml package. @AndreDupont from Netwrix and I have already consulted Copado support about possible options. Currently, the only solution we see is exporting the .csv file from the report.
Hi @rnaik Thank you for sharing the details and confirming your current setup with Copado. I understand the gap you’ve identified around exporting metadata components as an .xml package, and I appreciate the time you and @AndreDupont have already spent investigating this with Copado support.
At this time, we don’t have plans to move forward with an enhancement in this area unless we see broader interest from additional customers. We’ll continue to monitor demand, and if it becomes a more common need, we’ll certainly revisit the request.
