Sending Workflow with Locally Saved Inputs

[nperez]

Hello,

I am trying to share a workflow to a 3rd party. I exported the workflow to a package, however the other party is unable to run the workflow because the inputs/outputs are saved locally on my computer. 

What is the best way to resolve this issue and allow the other party to be able to open and run the workflow on their end? Do I need to save my inputs as a zip file and remap all of the input/output files? There are over 100 files. 

Thanks for the help!!!

[Garabujo7]

Hello @nperez , have you selected all the files when exporting?

Are you using input tools to read the files or Directory tools?

Gabriel

[Felipe_Ribeir0]

Hi @nperez 

You are using directory tool + dynamic input tool/input macro or input tool with wildcard to union all these files, right? Unfortunately the export as package does not pack the inputs in this situation. I would solve this like this:

1)Create a folder at the same location of your workflow and put all the files there

2)Inside your workflow, keep all the dependencies as relative path

3)ZIP your workflow + path and send it.

If the provided answer helped you to solve the problem/was correct, please accept it as a solution :)

Thanks.

[Felipe_Ribeir0]

Hi @nperez 

It worked?

[Carolyn]

@Felipe_Ribeir0 - You answered this question 1.5 years - THANK YOU. I couldn't figure out why I couldn't package my assets - I'm using wildcards. THANK YOU!