Hi all,
I have an issue and would like your input on whether this solution is possible.
Hi @dominictran ,
Here's the thing. If you want to use an interface tool (in this case a single file browse) in your workflow and you don't want this to be an analytic app, then this workflow will be a macro. You will then have one workflow/parent macro and within that different nested/children macros (part1, part2 etc).
Now your "children" macros cannot have a file browse tool in them, because then you won't be able to change the filepath "globally" to all of them, but you will have to go to each macro and configure the interface. What you can use instead is a control parameter, which will replace the filepath with whatever feed in to the macro's input
Child macro sample :
Parent macro:
If you do want your main/parent workflow to be an actual workflow and not a macro, you will then have to delete the file browse interface tool used above and everytime you want to run this standard workflow, you can update the filepath in the text input tool manually.
Parent standard workflow:
Hope that helps,
Angelos