Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Macro wont open. "Question tool load error, tool id missing associated question data"

JDeJong
8 - Asteroid

Need some help here.  This shouldn't happen:

 

clipboard_image_0.png

12 REPLIES 12
JosephSerpis
17 - Castor
17 - Castor
JDeJong
8 - Asteroid

Why tool ID '12'?  Seems arbitrary.

JosephSerpis
17 - Castor
17 - Castor

Sounds like the tool may have been corrupted and would of been no real reason why specifically tool id 12. 

JDeJong
8 - Asteroid

There is a bug in the Alteryx code.

 

I don't believe any of the answers given sufficiently address this problem. 

 

The workaround is to open the macro as a text file.  At the very bottom of that file there is a "Questions" section.  It is under "RuntimeProperties" and looks like:

 

clipboard_image_0.png

 

Copy this text and paste before the closing </Questions> statement:

 

<Question>
<Type>Tab</Type>
<Description>Questions</Description>
<Name>Tab ([yourtoolidhere])</Name>
<ToolId value="[yourtoolidhere]" />
<Questions />
</Question>

 

Save your file and you should be able to load the macro.

MichalM
Alteryx
Alteryx

The problem seems to have been introduced by the latest feature that allows you to convert tools - eg Convert Browse to Macro Output. The dev team is aware and working on a fix. I'll let you know when once the fix is available. 

chriscgmedia
7 - Meteor

@JakeDeJong

 

I am getting this with a batch Macro (tool 9) but my code when I look at it as a text file seems to be different. 

 

Do I need to delete my Tool 9 from here? 

JDeJong
8 - Asteroid

What does your file look like?

chriscgmedia
7 - Meteor

Made the Macro again so no worries!

justindavis
10 - Fireball

@MichalMany update on this issue? The fact that I cannot even open a macro I spent time creating anymore is maddening. And the above workaround doesn't work in my particular situation.

Labels