The Datastore Merge worker appends datastores together creating a new merged datastore, which can be saved in the platform or be used on the workflow.
The Datastore Merge worker must receive specific parameters in order to execute properly. When parameters are not set correctly it may cause the worker to not work as expected. This worker parameters is separated in the following tabs: Input and Output.
The Input tab contains parameters which are consumed by the worker, in order to execute it's calculations or actions.
1.3 Data Source
Add new datastore field by clicking on the Add Source button.
Set the datastore data source using Fixed Datastore, Get Latest or Upstream Data variants.
Set the research workspace of the data source datastore using Fixed Workspace variant.
1.3.3 Merge Direction
Set the direction to merge the datastores using Fixed Value variant.
The Output tab contains parameters that defines the worker execution results, and how it will be provided to downstream workers.
Set the datastore name using Template Text or Upstream Data variants.
Set the workspace in which the merged datastore will be saved on the platform using Fixed Workspace.
Select the datastore date using Fixed Date or Upstream Data variants.
Set the datatore tags using Fixed Tags or Upstream Data variants.
2.5 Storage Mode
Select if the result datastore will be saved on the platform, update an existing datastore or be a transient one through the following options: Transient or Create.
Once the worker finishes it's executions succesfully, it will return a result object containing the merged portfolio to the workflow, which can be used by downstream workers. Below you can see an example of the Portfolio Merge's result object hierarchy.
- Datastore (portfolio)
- ID (string)
- Name (string)
- Tags (list of strings)
- Date (date)
- Data (list of lists)