Create Data Source Table Step – create-datasource
Type | Description |
---|---|
| Creates a Data Source based on user's data. |
Data Requirements
In the package directory in the data folder, this step requires:
DataSource folder (keeping the structure and naming conventions as provided by Packaging Tool).
This folder contains a full definition of the Data Source; the package only maps those fields selected by the user.
Specific Attributes
Attribute Name | Description | example | required |
---|---|---|---|
| Name of a Data Source defined in the "data" folder in the package. The data source will be used as a template for creation process. | TXStandardData | true |
| Specifies a list of fields which must be linked with users's data. Information about fields has to be stored in the data folder in a format defined by Packaging Tool. Each field must contain:
Dynamic path allows you to define a Data Source and its field whose name should be fetched and used. The process will fetch the Data source, iterate through fields and find the field which has an inner property with a name defined by "fieldName" set to a value defined by "fieldValue". | "mandatoryFields": [
{
"name": "UniqueId",
"label": "UniqueId",
"description": "Transaction unique identification"
},
{
"name": "ProductId",
"label": "Product Id",
"description": "Id of a product",
"type": "STRING",
"dynamicPath":
{
"dsUniqueName": "Product",
"fieldName": "sourceField",
"fieldValue": "sku"
}
}
] | true |
| List of fields which must be linked with users's data. Information about fields has to be stored in the data folder in a format defined by Packaging Tool. Each field must contain:
Groups
Optional fields can be grouped so that users can set logical groups for them and UI respects this.
Dynamic path allows you to define a Data Source and its field whose name should be fetched and used. The process will fetch the Data Source, iterate through fields and find the field which has an inner property with a name defined by "fieldName" set to a value defined by "fieldValue". | "optionalFields": [
{
"type": "group",
"name": "group 1",
"fields": [
{
"name": "OtherOnInvoicePromotions",
"label": "OtherOnInvoicePromotions",
"description": "",
"type": "STRING"
}
]
},
{
"name": "Currency",
"label": "Currency",
"description": ""
}
] | false |
| Allows to specify fields based on previous skipped/non-skipped steps. It contains an array where each object has:
| "conditionalFields": [
{
"condition": true,
"steps": [
"customer-master"
],
"mandatoryFields": [
{
"name": "CustomerId",
"label": "CustomerId",
"description": ""
}
]
}
] | false |
| Similar to optional fields. The only difference is that users are advised to fill in these fields for better Accelerator result. Each field must contain:
Dynamic path allows you to define a Data Source and its field whose name should be fetched and used. The process will fetch the Data Source, iterate through fields and find the field which has an inner property with a name defined by "fieldName" set to a value defined by "fieldValue". |
| false |
| Definition of demo data:
| false | |
| Definition of example file:
|
| false |
| If set to true, a modal dialog with mapping options appears after the mapping step, with these options:
|
| false |
| Allows to set a default Data Source currency. |
| false |
| Allows the user to specify a custom field in UI. The default is false. |
| false |
Example
PlatformManager version 1.75.0