Hello,
I have a challenge with a workflow containing a macro when uploading on Alteryx Gallery, giving me the below error:
I have downloaded a while back a macro with several macros built in for Dynamic Calculation (transforming a text with a formula into a calculation).
The workflow worked very well in Alteryx Designer, but when I tried to upload it into Alteryx Gallery, it gave me the error that it cannot find the in-built macros (level 2 & 3).
That was because I was not able to see them under "Workflow Options --> Manage workflow assets". I have found here that I need to make available the option of Assets - Auto-detect assets". I did that for all the macros, but then I have this error.
Please bear in mind that if I try to delete the macro and readd it in Alteryx Designer, it works very well in Designer. When trying to upload on Alteryx Gallery, something changes because it cracks everything - I cannot run it either in Designer.
Could anyone advise what I should do? I am uploading the Macro used.
The error is coming from the last Macro:
One level above - This is from Macro "DynamicFormula"
I do not know if the below notification has anything to do, but this appears when opening last macro - DynamicFormula.yxmcbatch (it shouldn't based on what is written, but I wanted to mention it as well):
Would highly appreciate any support!
Thank you!
@apathetichell - when I go to load it to the server, I select it from the "Manage Workflow Assets" . I then have the option to choose it, but knowing it is an Alteryx tool and not one of my own, I wouldnt select it. But if if was my KREW macro (which was local, or a self-developed macro which was local) I WOULD check the box to package it up. Just need to do the workout I referenced earlier ahead of time if it is a macro, in macro in macro situation to make sure the workflow has all the parts pre-packed. Or perhaps I have just been doing it wrong for years. Which is ENTIRELY possible. I am not claiming I am right here, just trying to learn if there are better ways to do it.
O.k. - my memory is that some tools behave differently here than others. See GSheet which does not show up in export worklow. It could be encrypted macros in your macros directory vs public macros.