Macro - What Type to Use

I have a list of about 20 tables I want to push though 3 joined tables (macro). These tables (data dictionary) retrieve the field names and descriptions, etc for the 20 tables.

I could see a use case for an output (yxdb) for each of the tables and a use case where the are unioned to a single yxdb.

Macros are something I do not have in my tool box yet. There are so many repetitive processes I could apply this approach to.

Your thoughts,

Thanks!

Puff

Macros

Accepted answers

Thableaus

@stapuff

Imagine a Batch Macro like this. With an Output Tool at the end, no Macro Output at all

And then, a workflow would have a list of the tables that would go as your Control Parameter.

Your Batch Macro would have no output at all in your main workflow. But at the end, if you have 3 tables for example, you would have 3 outputs, because each iteration would generate a .yxdb file inside your macro. So it would be a single file for each.

Understand what I mean?

If you need more examples, please let me know.

Cheers,

All comments

Thableaus

Hi @stapuff

If you want to do the same process for the 20 tables you're working on, I recommend you to use a Batch Macro.

The Control Parameter Interface Tool will be your best friend and probably what you would use to update each table each time.

And you can either have an option to end your macro with an Output tool (that meaning you would generate an yxdb for each table) or you can end it with a Macro Output (which would union every table output in a single dataset) and then in your workflow, you would connect the Macro Output to an Output tool to generate a single .yxdb file.

Cheers,

stapuff

I appreciate your response. I thought that was going to be the answer, but I didn't see a option to output to a single file for each.

Thank you for your response. I am grateful for your guidance.

Puff

Quick Links

This months top contributors

mceleavey 383

mbarone 337

Hollingsworth 335

LanisC 335

RithiS 280