How to connect Check Box tool to Input tool to run workflow?

[Joker_Hazard]

Hello guys, I'm trying to connect two check box tools into different input tools. If they are active, the workflow would normally run.

I am having this error when running the app:

Any ideas on how to solve it? Thanks!

[apathetichell]

Could you explain what your formula is trying to say? Are you trying to have the different checkboxes determine what file you are bringing in ie check box 1 is STR0008R2 AND checkbox 2 is PAG108R2? I'd probably structure that as a dropdown since you can control the formatting of what goes into your input data easier.

Your formula is currently  returning a  boolean (1=1 ("true") or 1=2 "false") - formatted as a double (ie -1 or 0)... because you aren't referencing the questions (ie [#1],[#2]) you are referencing the integers 1 and 2 - but this wouldn't make much of a difference [#1]=[#1] is still True and [#1]=[#2] is still false.

[Joker_Hazard]

As you said, I'm trying to have different checkboxes. 

If box STR0008 is active, then proceed with workflow one, and if box PAG108 is active too, it should also proceed with the other workflow.

The inverse could happen, If are not active, dont proceed with the workflow. Also they could be one active and one deactive.

How can I fix this?

[apathetichell]

check box 1 - container 1 (input file 1)

check box 2- container 2 (input file 2)

I don't see why you need to try to look at the checkbox input vis a vis each other since the workflows are separate.

[Joker_Hazard]

Apathetic,

Thanks for the info. I did that, the only problem is that I did not flag "PAG108R2" and it still ran, as you can see in the result screen. 

That's the config I used in Action tools(Both Tools):

Am I missing something?

Tks

[apathetichell · Accepted solution]

You aren't flagging or changing values - you connect your action tools to detours or container boxes and activate/unactivate them based upon the checkbox. The goal isn't to change the value of what is being put into the input tool - the goal is to activate/deactivate that part of the workflow based upon input.

If you need more help - try posting something.

[Joker_Hazard]

Thank you.

I found a new interference unfortunatelly, will have to open a new thread.

There is a bug:

I am unable to continue my work with this bug maybe because my text box tool has connections between both containers.

[apathetichell]

That's not a bug - it's a tool container feature - you can't have interface tools like input data in them. you can get around this by having macros (with input data tools) or detours as I would suggest in your case. If you post something I can show you how to implement detours.

[Joker_Hazard]

Hello, Apathatic!

I have posted a new thread, so far no one could help with that. Would you mind taking a look?

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Disabled-containers-may-not-contain-in...

Thank you so much!