This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
As more and more users become familiar with macros it is useful to know the potential ways of scaling and sharing these insights within your business.
Here are just a few ways to achieve this aim!
Push latest macros to users/automatically ensure that users are using the latest version
Alteryx Designer Desktop
Working with colleagues and sharing macros?
Within the Alteryx designer you can create your own macro ‘Parent Category’. When specifying a file path, you can choose either a local or a network/mapped drive. If you are building macros within a team and looking to share or update macros dynamically, having a mapped location will allow you to reflect any changes on everyone’s machines.
As a best practice when overwriting a macro it would be best to update the Meta-data tab (Within workflow properties tab) within the macro to add initials or details of what has changed. This can help you track who edited each version. Unfortunately, if you choose to use an overwrite function, you will be unable to control the version of the macro overtime.
Therefore, you may choose to add “V1” etc. to the macro when saving it to the network location. This macro parent category could then be used as a development location and then you could have another macro parent category where you publish production ready macros.
The Alteryx Server can adopt a similar outline to that of the Alteryx Designer however, it has a greater flexibility in terms of version control. When building a macro you can publish it with a description.
Then when a change is made to the macro you can press the save icon and add another description.
Within the gallery this is then reflected when you click on the macro and click on the version number. You then have the capability of running & publishing up and down versions.
Include macro pack as part of installation procedure for new users
You could zip all the macros together and get a user to extract them to their own macro folder (mentioned above).
Or to the Admin (C:\Program Files\Alteryx\bin\RuntimeData\Macros) or Non-admin (C:\Users\%USER%\AppData\Local\Alteryx\bin\RuntimeData\Macros) folders.
If you use the metadata tag when building the macro workflow it can land in that parent category as well.