Import From CSV
- 12 Jan 2023
- 1 Minute to read
- Print
- DarkLight
Import From CSV
- Updated on 12 Jan 2023
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Step Details | |
| Introduced in Version | 4.0.0 |
| Last Modified in Version | 7.12.0 |
| Location | Database |
The Import Excel or CSV step loads tabular data from CSV or Excel-formatted files. The function of this step is to import an excel or CSV file into a data type. The assumption is that the datatype being imported has properties that correspond to the columns of the excel file.
Properties
Inputs
| Property | Description | Data Type |
|---|---|---|
| Import File | The csv file containing the data to be imported | FileData |
| Type Name | Name of the Data Type being used for the import. The step requires the full type name in order to be used. | String |
Common Errors
Object reference not set to an instance of an object
The step requires the fully qualified name for a datatype in order to be used, for example PerformanceTesting.ExampleList. The input is case sensitive and must match exactly
Exception Message:
Exception Stack Trace: DecisionsFramework.Design.Flow.ErrorRunningFlowStep: Error running step Import From CSV 1[ImportFromCSV] in flow [Testing]: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at DecisionsFramework.Design.Flow.CoreSteps.DataBase.ImportFromCSV.Run(StepStartData data)
at DecisionsFramework.Design.Flow.FlowStep.RunStepInternal(String flowTrackingID, String stepTrackingID, KeyValuePairDataStructure[] stepRunDataValues, AbstractFlowTrackingData trackingData)
at DecisionsFramework.Design.Flow.FlowStep.Start(String flowTrackingID, String stepTrackingID, FlowStateData data, AbstractFlowTrackingData trackingData, RunningStepData currentStepData)
--- End of inner exception stack trace ---Was this article helpful?
