An Alteryx macro “is a workflow or group of tools combined into a single tool that you can insert into another workflow.”
Macros are very useful when processes require repetitive tasks by standardising common tasks, keeping workflows tidy, and can be relatively easy to share. After creating a macro, the macro can be used within other workflows without the need to recreate the analytic process each time.
There are 3 types of commonly used Macros: Standard, Batch, and Iterative.
Learn more about them through one of the blogs from our consultants at the Data School here!
The file extension for macros is .yxmc.
The way to share macros may depend heavily on the end user for the workflow you’re building. After creating the macro(s), here’s 3 ways you can share them and the pros and cons for each way:
1. Share the .yxmc file via email
Pros:
- Easiest and most straightforward way to share a macro
- Can send the file directly to the recipient without any additional setup
- Can open the file in Alteryx Designer and start using the macro
Cons:
- Updates aren’t automatic – If the macro is updated, the updated file needs to be sent to the recipient
- Will create issues if macro input uses a file input and files are not attached or sent as a packaged file
2. Publish to the Alteryx Gallery (to a server)
Pros:
- Easy to share and provide access
- Can set permissions to control who has access to the macro
- Version control
Cons:
- Updating the macro requires users to re-download
- The recipient needs to have access to the Alteryx Gallery to download the macro
- If the macro contains sensitive data, it might not be appropriate to publish it to the gallery
3. Sharing a .yxmc file via network drive
Pros:
- Updating the macro automatically updates it for all users
- Allows you to share macros within a team or organization
- The recipient can easily access the macro from the shared location
Cons:
- The recipient needs to know where to find the macro in the shared location – changing such as renaming, deleting, or moving the network file paths will cause errors
- Macro may not be accessible across VPN
- If the macro contains sensitive data, all people with access to the shared location will be able to see it