R Tool Messages

[jbh1128d1]

Hello,

I've created an r based macro and I'm confused on how to get the messages to appear to the user when they are using the macro?

I see on the help page the different messages, but do I have to type in every message word for word to display?  This macro shows iterations of GLMs ran and the deviance could be different every time so if I have to do it word for word, that may not work. 

Any help will, as always, be appreciated.  

[BenMoss]

Hi @jbh1128d1,

Could you share exactly what you mean by 'messages'?

Images and screen shots around what exactly you are trying to achieve will help us solve your problem!

Ben

[jbh1128d1]

Hi @BenMoss.  Thank you for the reply. 

Here are some screen shots.  Basically, once my data is running through the r tool, I'm getting messages of the decrease of deviance by iteration for the GLMs.  That's one example.  Another example that I couldn't reproduce but sometimes comes up is the warning messages before the error messages.  

See screen show below.  This shows up if I open the macro and run it but will not show up when I'm using the macro on another set of data.  At the end of the day, I would like any message the r tool produces to show when using the macro. 

[BenMoss · Accepted solution]

There are a couple of things you can do here.

First of all the user could, from within Alteryx Designer, go to their workflow configuration panel (click anywhere on the white space of the canvas ensuring the configuration pane is open) then go to 'Runtime' then towards the bottom of this panel is an option to 'Show All Macro Messages' this will make these messages visible to others.

I believe this is how the above should work but I'm not 100% with this, it may in fact be talking strictly about the 'message tool'.

A second option would be to actually write this detail to a dataframe and then have this as a separate macro output, this will allow them to view it as if it was it's own flow of data, and perhaps transform it if they wish.

Ben

[jbh1128d1]

Thank you @BenMoss