Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesConsider, for a moment, Standard Macros as old-school Subroutines in which you would have a library of Subroutines that could be invoked from numerous code sets. Each Subroutine could have any number of arguments, and when the Subroutine is invoked, the calling code provides the arguments and their values to the Subroutine.
You can do this in Alteryx - but with a very large but. The source field names being passed to the Standard Macro have to be the same field names the Standard Macro is expecting. To make the Standard Macros more "library friendly" - allow the calling workflow to alias fields in the dataset for the sole purpose of sending them to the Macro.
Example: Standard Macro that returns a Vendor ID based on a Location and Item Number.
Macro Input: Location ID, Item Number
Calling Workflow has: Purchase Location and Item Code
The Macro on the calling workflow would have a mapping:
Data Set Object | Macro Input Object |
Purchasing Location | Location ID |
Item Code | Item Number |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.