File name as a parameter in export

Slimani

Hello,

I hope you're all fine :o)

In a workflow, we use a dataset (which has as source a file), later in the workflow we export the result. Is it possible to use the file name of the datatset as an export file name ?

Or at least, could we create a function which do:

1- use the file name as parameter

2- export the result (of a step of the workflow) using that parameter

FYI: here is our use case:

We have a workflow used by many persons, each person is working on a different input dataset file, each person use a datadropzone path to refresh the workflow dataset. We want to distinguish the execution result of the workflow, this is why we though that using in the export file the same name of the input file could be a solutoin

Thanks a lot for your help.

Best regards

Ali

Josh Boxer

Hi Ali

It is possible to use a column value, including a metadata column such as filename, as a workflow parameter value:

https://community.experianaperture.io/discussion/829/use-a-value-in-your-data-as-the-export-file-name

this makes sense if files are being dropped programmatically and Workflows run automatically.

In your case, rather than using a dropzone the users can supply the file when running the workflow:

They can also supply 'Parameters' such as their initials or the filename before running the Workflow

Slimani

Hi Josh,

Thank you for your reactivity

Our current Aperture version is 2.8.8..27

I guess that your screen shot is form a newest version than mine this is why I'm not able to see the menu "Sources", nor "Parameters

Few more words regarding our use case: we need to let our end users (consumer role) to trigger the running of workflows and let them uploading them selves their input file, this is why we thought about datadrop zone

Thank you Josh

Josh Boxer

Hi Ali

No this is not new functionality so you definitely have access.

For the Parameters, create/edit a Workflow Parameter and check the box 'Configurable on runtime'

https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/get-started/create-a-workflow/#workflowparameters

For the Sources, on each Workflow Source step you can check the box 'Can supply source when executed'

https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/get-started/create-a-workflow/#source_replaceablesources

Consumer users do not have the ability to view (or run) workflows, so yes maybe dropzone will be the best option

Finally it is possibly to execute a workflow using a file from API https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/extend-data-studio-functionality/use-the-rest-api/#execute-and-manage-workflows