I'm having a problem ensuring that macro components are included in workflows that I export. Our organization stores many of our macros in a commonly accessible network folder, and then includes that location as MyMacros in each alteryx installation. I am aware that macros stored in a MyMacros folder (any folder accessible natively from within alteryx) is not included when a workflow is exported.
We have a teammate who is not local and needs to access some of these macros, but is not on the network. Some of our macros are nested and include several other macros from our MyMacros folder. When I attempt to export a workflow containing the outer macro, none of the nested macros are included in the output and the exported workflow will inevitably fail when unpackaged remotely.
I've tried copying the MyMacros folder to another location, but the macro path is absoloute and not relative. Moreover, macros do not show up in the workflow dependency options and therefore cannot have their path changed to relative. When we send the files, even if we send all of the macros, our nested macros will not work due to the hardcoded file paths.
Anyone have a quick solution to this? The only thing I can think of is to remove the MyMacros folder from the config file, close and reopen alteryx, and then package the workflow in that way (which should include the nested macros as they are no longer in a local macro folder). This is a little clunkier than I'd like, and I wondered if anyone else has had similar problems. Thanks in advance!