how to implement feature of unknown dynamic field for macros

Question

how to show/ apply similar method which the macro to included the new/unknown fields like select tools.

i have a sort column macro. where to sort the columns by name. however, it normal that have new field in later of time.

so i dun want to manual update, where is not make any sense.

my current method is do it the reverse way, where only pick the column not to sort.

sort fields by name.yxmc

AncientPandaman · Answer

@KGT okay, i think you confuse on who is user.

user -> who ran the macro via server.

when user ran the workflow, he can't see the macro configuration.
so i need a method to handle these new field in workflows. (where "*unknown" field will help here. to bring the new field name in to the macro.)

and yes, non-macro ways are definitely work.

but now i try to build some macros for exploration purpose, and it easier for new alteryx developer to use.

So the case i written above is just one for the situations, it will lot more of case where unknown field should be handled.

eg:

1. data cleansing tool to covers unknown columns.

2. sort data within rows (3,1,2 -> 1,2,3) without change the header name

3. sum data within rows

4. concat multi-row into headers

5. demote header into rows

where "*unknown" field will make them to cover more situation instead of one-off/ fixed columns.

@apathetichell good idea to use dynamic select. I can create another option to use textbox to input expression into dynamic select.

apathetichell · Answer

If this is is a situation where you're using months -> specifically and you want to apply a sort order -> you would create a logic to map your month column names to a month value -> and then perform a sort/reordering using some combo of field info or transpos, field info -> and then dynamic rename where you take your columns names from the right datastream (which has a map of month/ month in numeric order) -> you can then dynamically select/sort. I'd also recommend looking at dynamic select to filter for fields which match specific dynamic requirements -> and then dynamic rename to create a static name (like 'most recent month') -> you can then use that static name in a summarize tool.

KGT · Answer

I'm not sure I understand the issue here. Your list box is connected to the Q of the Macro Input and so it will load with the list of fields from whatever is connected to the Macro Input. So, the user will be able to choose from the actual list of fields.

If you do not want the user to pick, then you need to create that rule for them. An easy way to take an unknown number of fields and order them is to transpose those headers, summarize and then sort the name column and record ID. You now have a lookup table that you can use to rename, re-order etc and it's dynamic.