> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# csvExport

> This operation exports file(s) from the build Oracle SaaS environment or your SCM repository, waits for all exports processes to complete, and then do

This operation exports file(s) from the build Oracle SaaS environment or your SCM repository, waits for all exports processes to complete, and then downloads results as a single zip file artifact. The csvExport operation can only be used with a FlexDeploy package-based deployment project of type Oracle SaaS FSM.

Artifact is a single zip file containing zipped CSV or json File Packages.

As of 6.5.0.20, 7.0.0.11, 8.0.0.6, and 9.0.0.0, this operation will export some files as json files, and others as CSV files. Both can be uploaded successfully by the import operation. The types of files that are now downloaded as JSON instead of CSV are a subset of Value Sets and Lookups. The JSON download is much faster and smaller than the CSV one is. The resolves several issues that customers brought up where value sets and look ups were not exported properly due to file size restrictions in the export process.

### Value Sets are downloaded as JSON now instead of CSV if the following criteria are met:

![image-20240916-171053.png](https://mintcdn.com/flexagon-llc-ce77a95c/NkeZh5D-Nf8j_WaD/images/fd111/12596417609.png?fit=max\&auto=format\&n=NkeZh5D-Nf8j_WaD\&q=85\&s=54ca810611a6f730c831a5d42e7f7bc3)

* The `Type` is set to `Value Set`

* The `TaskCode` is set to `FND_MANAGE_VALUE_SETS`

* The `ValueSetCode AttributeValue` is set to the ValueSetCode of the ValueSet that you wish to download.

These criteria are met for the auto-discovered Value Sets.

### Lookups are downloaded as JSON now instead of CSV if the following criteria are met:

* The `Type` is set to `Lookups`

* The `TaskCode` can be set to any of the following: `FND_MANAGE_SET_ENABLED_LOOKUPS, FND_MANAGE_COMMON_LOOKUPS, or FND_MANAGE_STANDARD_LOOKUPS`.

* The `Lookup Type` is set to the LookupType of the Lookup that you wish to download.

These criteria are met for the auto-discovered Lookups.

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Oracle SaaS FSM Account</td><td>`FDFSM_CLOUD_ACCOUNT_CODE`</td><td>No\*</td><td>Oracle SaaS cloud account will be required on either the plugin input or Target. If a value is set on both then, the plugin input will take precedence.You can manage the Oracle SaaS cloud account via the **Integrations > Cloud** page.See [Configuring Oracle SaaS Cloud Account](https://docs.flexagon.com/flexdeploy-10-0-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-saas-fsm-plugin-guide/configuring-oracle-saas-cloud-account.md) for additional details.</td></tr></tbody></table>

# Inputs

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Input Name**</th><th>**Input Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Oracle SaaS FSM Account</td><td>`FDFSM_INP_CLOUD_ACCOUNT_CODE`</td><td>No\*</td><td>Oracle SaaS FSM Account will be required on either the plugin input or Target. If a value is set on both then, the plugin input will take precedence.See Special Considerations below for instructions on how to create Oracle SaaS FSM account.</td></tr><tr><td>API Timeout</td><td>`FDFSM_INP_TIMEOUT`</td><td>No</td><td>Maximum amount of time (seconds) to wait for export process to complete after it is started. Defaults to 900 seconds (15 minutes).</td></tr><tr><td>Stop on Error</td><td>`FDFSM_INP_STOP_ON_ERROR`</td><td>No</td><td>If unchecked, the export process will continue with the remaining package files even if a failure occurs; however, the overall build will still be marked as failed. By default, this option is enabled (true), meaning the operation will stop immediately if any package file fails.If you're using this operation to sync CSV data with SCM, unchecking the option allows successfully exported package files to be synced despite individual failures.This is available **@Since 9.0.0.6**.</td></tr><tr><td>Save Export Result File</td><td>`FDFSM_INP_SAVE_EXPORT_RESULT_FILE`</td><td>No</td><td>Saves a comparison result file to the reports directory as a JSON file. The JSON file provides a summary of the comparison process and represents the table shown in the Comparison Details section of the user interface.</td></tr><tr><td>Save Export Report File</td><td>`FDFSM_INP_SAVE_EXPORT_REPORT_FILE`</td><td>No</td><td>Saves a comparison report file to the reports directory as a HTML file. The HTML file provides comparison reports for each of the business objects that were processed. For each business object, a report each for Only in Configuration 1, In Both With Mismatch, and Only In Configuration 2, as applicable is provided.</td></tr><tr><td>Save Export Summary Report File</td><td>`FDFSM_INP_SAVE_EXPORT_SUMMARY_REPORT_FILE`</td><td>No</td><td>Saves a comparison report file to the reports directory as a HTML file. The HTML file provides a summary of the process results, which displays a list of all the processed business objects, and whether their processing completed successfully, or with errors.</td></tr><tr><td>Filter Criteria Preview Mode</td><td>`FDFSM_INP_FILTER_CRITERIA_PREVIEW_MODE`</td><td>No</td><td>When enabled no artifacts, CSV file package(s), will be generated. Instead before and after zip files will be provided in FD\_REPORTS\_DIR along with diff and unified diff files to validate filter criteria behavior. Make sure this is disabled at build time if you wish to deploy setup changes. Defaults to false.</td></tr></tbody></table>

# Artifacts

This operation produces artifacts that will be stored in the artifacts repository.

# Endpoint Selection

This operation will select all available endpoints associated to the Target.

# Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

# Special Considerations

## FSM Setup Task Export Reports

CSVExport can generate additional reports and log files which are viewable and downloadable from workflow execution → reports tab. The .log file will always be a generated report. Keep in mind, the contents of the .log file will also be outputted to the plugin log file. Additional reports that can be generated include:

* \<TASK\_CODE>\_ProcessResultsSummaryReport\_\<EXPORT\_DATE\_TIME>.html - A high level overview of the number of objects exported and the execution time

* \<TASK\_CODE>\_ProcessResultsReport\_\<EXPORT\_DATE\_TIME>.html - A high level overview of the objects exported by business object and the execution time for each

* \<TASK\_CODE>\_ProcessResult \_\<EXPORT\_DATE\_TIME>.json - The response body from the Export API after export has completed. This is generally not used but provided regardless.

To include any of the additional reports, you must enable those in the csvExport workflow operation.

![Image](https://mintcdn.com/flexagon-llc-ce77a95c/NkeZh5D-Nf8j_WaD/images/fd111/12596417612.png?fit=max\&auto=format\&n=NkeZh5D-Nf8j_WaD\&q=85\&s=35acddd377a852d3900cb2f2f1c39a21)

Example reports:

XLE\_MANAGE\_LEGAL\_REPORTING\_UNIT\_ProcessLog\_20231208\_123744\_0831.log

```
The export operation was initiated calling the export API as indicated below. Export operation: submitTaskCSVExport.Request ID: 7,176,630. Status: In progress. Submitted By: CURTIS.FEITTY. Process Date: 12/8/23 6:36 PM.

The implementation project Manage Legal Reporting Unit_20231208_063617_114 was exported successfully.

Business object: Legal Reporting Unit. Status: In progress. Status details: 
	Detail Object: LegalLocation. Status: Completed successfully. Status Details: A total of 98 rows were processed. 0 rows of them failed and 0 rows completed with warnings.. Started: 12/8/23 6:36 PM. Ended: 12/8/23 6:36 PM.

Business object: Legal Reporting Unit. Status: Completed successfully. Status details: 
	Detail Object: LegalEntityData. Status: Completed successfully. Status Details: A total of 2 rows were processed. 0 rows of them failed and 0 rows completed with warnings.. Started: 12/8/23 6:37 PM. Ended: 12/8/23 6:37 PM.
	Detail Object: LegalLocation. Status: Completed successfully. Status Details: A total of 98 rows were processed. 0 rows of them failed and 0 rows completed with warnings.. Started: 12/8/23 6:36 PM. Ended: 12/8/23 6:36 PM.

Total Objects Processed: 1

Total Objects Succeeded: 1

Total Objects Failed: 0

Total Objects with Warnings: 0

Total Objects for External Loading: 0

Request ID: 7,176,630. Status: Completed successfully. Submitted By: CURTIS.FEITTY. Process Date: 12/8/23 6:37 PM.

```

XLE\_MANAGE\_LEGAL\_REPORTING\_UNIT\_ProcessResultsSummaryReport\_20231208\_123744\_0831.html

![Image](https://mintcdn.com/flexagon-llc-ce77a95c/NkeZh5D-Nf8j_WaD/images/fd111/12596417606.png?fit=max\&auto=format\&n=NkeZh5D-Nf8j_WaD\&q=85\&s=1b1bb005c4273b3164d2f6da601a53e4)

XLE\_MANAGE\_LEGAL\_REPORTING\_UNIT\_ProcessResultsReport\_20231208\_123744\_0831.html

## How to find Task Code for a Setup Task?

To initiate the export or import process, Oracle endpoints requires providing a code for the task. Following these instructions to find the Task Code. We are assuming you have access to FSM resource.

1. Click Navigator > My Enterprise > **Setup and Maintenance**.

2. In the Setup and Maintenance work area, click **Manage Setup Content** from the Tasks panel tab.

3. To search for the code of a task

   1. On the Manage Setup Content page, click **Manage Task Lists and Tasks**.

   2. In the Search field, select **Tasks** and click **Search**.

   3. In the search results, click the name of the task.

   4. On the Task page, look for value that appears against **Code**.

   5. Copy the code and use it where necessary
Input Name	Input Code	Required	Description
Oracle SaaS FSM Account	`FDFSM_INP_CLOUD_ACCOUNT_CODE`	No\*	Oracle SaaS FSM Account will be required on either the plugin input or Target. If a value is set on both then, the plugin input will take precedence.See Special Considerations below for instructions on how to create Oracle SaaS FSM account.
API Timeout	`FDFSM_INP_TIMEOUT`	No	Maximum amount of time (seconds) to wait for export process to complete after it is started. Defaults to 900 seconds (15 minutes).
Stop on Error	`FDFSM_INP_STOP_ON_ERROR`	No	If unchecked, the export process will continue with the remaining package files even if a failure occurs; however, the overall build will still be marked as failed. By default, this option is enabled (true), meaning the operation will stop immediately if any package file fails.If you're using this operation to sync CSV data with SCM, unchecking the option allows successfully exported package files to be synced despite individual failures.This is available @Since 9.0.0.6.
Save Export Result File	`FDFSM_INP_SAVE_EXPORT_RESULT_FILE`	No	Saves a comparison result file to the reports directory as a JSON file. The JSON file provides a summary of the comparison process and represents the table shown in the Comparison Details section of the user interface.
Save Export Report File	`FDFSM_INP_SAVE_EXPORT_REPORT_FILE`	No	Saves a comparison report file to the reports directory as a HTML file. The HTML file provides comparison reports for each of the business objects that were processed. For each business object, a report each for Only in Configuration 1, In Both With Mismatch, and Only In Configuration 2, as applicable is provided.
Save Export Summary Report File	`FDFSM_INP_SAVE_EXPORT_SUMMARY_REPORT_FILE`	No	Saves a comparison report file to the reports directory as a HTML file. The HTML file provides a summary of the process results, which displays a list of all the processed business objects, and whether their processing completed successfully, or with errors.
Filter Criteria Preview Mode	`FDFSM_INP_FILTER_CRITERIA_PREVIEW_MODE`	No	When enabled no artifacts, CSV file package(s), will be generated. Instead before and after zip files will be provided in FD\_REPORTS\_DIR along with diff and unified diff files to validate filter criteria behavior. Make sure this is disabled at build time if you wish to deploy setup changes. Defaults to false.