Macro not saving as workflow dependancy

[CSmith16]

Hello,

We have been facing some issues recently where pushing something into prod breaks the workflow because of incorrectly saved workflow dependencies. These are new workflows built from scratch and when being built were all done locally and not saved to the gallery. Our macros should be saved to the workflow directory and are not and thus do not actually ush the work made into production. How do we change the pathways to be saved to the workflow directory?

This is an example of how it is working now (Incorrect)

Spoiler

 And this is it when it is saved correctly:

Spoiler

 

 

[Erin]

Mystery solved. Thanks @apathetichell !

[CSmith16]

Hey thanks for the response lol. When you say project directory you mean the location of where the workflow is saved? Or do you mean something differently? 

[Tony_Castillo]

@apathetichell I experience the same issue. Are you suggesting to create multiple versions of a macro and store in different locations? Apologies but I am not tracking the difference between the project directory vs macro directory and how this creates scalable solutions. 

[apathetichell]

First off - apologies @CSmith16 - sorry didn't see your question.

second - explanation - you have a macro default directory. It's usually part of the Alteryx root program. If a macro you build is saved here (along with the native Alteryx macros like Multi-Field Binning) it is not considered a specific Alteryx workflow dependency. It will not be uploaded to Server as a depdency. The fix is one of two things:

1) don't save it in your macros default directory.

2) sync your Server's macro default directory to include the macro.

for 2) you would need to be the server admin and directly access the server.