Macro running prior than what was supposed to

Hi Everyone,

I looked for this issue but I did not find any answer.

I built my own macro to open an Excel file and create a Table object. It is running as expected if I have a simple workflow but the problem is when this macro is running prior to the file being created. I tried to use "Block Until Done" and it is not working.

When I run my workflow, the first thing that is running is my poor macro...

What should I do in this case?

Alteryx - Workflow.jpg

Macros

Accepted answers

danilang

Hi @andrefc

I think that the macro runs before the rest of the workflow because there's nothing to stop it. Since the top stream, starting with the text input is not dependent on anything that comes from the main workflow(the bottom stream), it can run whenever.

Try adding a blocking tool that will stop the top stream from running by linking it to the bottom.

Here the Append Fields tool will act as blocking tool essentially stopping the top stream of the macro until there is data available on the bottom. To minimize the impact, the Sample tool takes only the first row from the bottom stream and the Select after it takes only one field, effectively adding one extra column to the top.

There are other, more elegant, ways to handle this, including moving the File browser to the main workflow and passing the file name into the macro, but this should work for you

Dan

andrefc

Thank you, @danilang !!

I tried to use Append right after running the C command but didn't work properly.

I changed a little bit your suggestion, using record count instead, so I don't need a specific column coming through the input and it's working as expected! Thanks again for your and @andyuttley help!

Alteryx - Workflow.jpg.png

All comments

andyuttley

Hi @andrefc

That's strange. In my experience 'block until done' is really useful, though if I'm wanting to reference a file I'm writing to in the same workflow, I'd normally choose to break the process out into separate 'chained' processes. I do this using the Runner / Conditional Runner tools available in the CREW macro pack:

https://community.alteryx.com/t5/Engine-Works-Blog/Crew-Macro-Pack-2016-Q2-Release/ba-p/26482

This will ensure the file is written before your macro tries to reference it (as they're completely separate processes)

- have you got these tools / have you used them before?

If it's not possible to use the runner macros (CREW) - is it possible to include a version of your workflow, even with dummy data, to test and debug? Alternatively, I'm happy to send a runner tool example over if you've not used them before

Hope that helps

Andy

andrefc

Thanks for your quickly reply, @andyuttley!

I think I am doing something completely wrong with my macro. I am pretty new with Macros, but the only thing this guy does is, it calls a VBS file based on the input info, but I need this process to be in the middle of a workflow, so I need to have an input and output, so the workflow can continue without any problem.

The only way I was able to do this without any interference was connecting the Macro Input directly to the Macro output... Is there any other way to get it solved?

Appreciate your help!

CreateTableOnce.yxmc

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703