This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Find answers, ask questions, and share expertise about Alteryx Server.
It's the most wonderful time of the year - Santalytics 2020 is here! This year, Santa's workshop needs the help of the Alteryx Community to help get back on track, so head over to the Group Hub for all the info to get started!
I'm having an issue disabling part of my work-flow and still using it on server.
I have one part of my workflow that isn't needed anymore (will be needed again in the future). So my thought was to just put those objects in a tool container and disable that container then in the future I can just enable them again. When I do this and run the workflow on my desktop via designer it works fine. Unfortunately when I upload that workflow back to the server it seems to run all the tools within that disabled container. Is that intended? Is there something else I should be doing to temporarily disable part of my workflow on the server?
If the tool container is disabled, it should remain disabled when ran no matter how it is executed. You already mentioned what my next comment would have been which was ensure that you replaced the workflow loaded to the Gallery with the updated version.
You could ensure the container is disabled on run by using an Action tool to set Disabled="True" on the container properties.
Thanks Charlie. I think I was a little quick to run the workflow right after publishing. I published again and then it worked as I expected. I'm assuming it must have kicked off an "old" version of the workflow the first time I tried.