Salesforce Pipeline and Task: CSV Upload Wizard How To
In Opsera, there are 2 methods used to run a Salesforce pipeline. Either get the components from the org to the git branch using the sync-sfdc-repo Task or move your components from a git branch or an org to another Salesforce org in Salesforce pipeline. The following documentation explains the process of uploading a CSV file in the Salesforce wizard.
CVS Upload Requirements
Before uploading the csv file, be sure it meets the following requirements:
Headers should match as compared with sample CSV File Template below
Component Qualified API Name should be given under the Component Name column in a CSV Upload file
Allowed Commit Action values are Added, Removed, and Modified (If empty we consider it as Modified)
View this sample CSV file template for correct formatting:
For a list of supported components and the syntax for each component types, view the following document:
CSV Upload
1. To navigate to the CSV Upload:
a. Navigate to the SFDC Pipeline and select “Start Pipeline” or
b. Navigate to a sync-sfdc-repo Task, select “Run Task”, select branches and select “Run Task” again. To view more detailed process on this, view SFDC Org Sync documentation.
2. Click on XML/File Upload Process tab
3. For Pipeline - Select the Source Org: From SFDC or From GIT
4. Drop the CSV file directly into the upload box or click on the upload box to make a file selection.
5. Select the Desired CSV or XML.
6. Click Process File.
A table including the CSV File Content is then generated:
If the CSV File Content Action column contains blank values, as in the table above, the Action type is considered “Modified”.
7. Click Proceed with Selected File to validate the above components against the org. The validation checks to see if the components are present in the org.
All of the components that ARE present in the org will be displayed in the Validated Files table. The components that are NOT present will be displayed in the Invalidated Files table.
Only the files included in the Validated Files list will be included in the XML package creation.
8. Click Proceed to confirm that you would like to proceed with the operation.
View the compiled XML package the next page. As you can see below it only included the Valid Files.
9. Click Proceed to extract the components from the XML package into the selected git branch.
The Pipeline Wizard has now started.