[Urgent] Data Cleansing Error in Control Container

Question

Hi all,

After I updated the latest version of Alteryx (version: 2024.1.1.71 Patch:2), there is an error occurred.

When I use control container to control the dependency. If the condition does not be matched, which means the remaining part in control container doesn't need to be run. While data cleansing tools in this control container will show error: 'Data Cleansing (28) DataCleansing.MultiFieldNumericMacro (308): Record #0: Tool #10: The DetourEnd tool must be combined with a Detour tool and can only accept 1 live input.'.

I have attached the error log in this post down below.

This error doesn't show in before version.

Can someone help on this? Thanks!!

TrangPham1209 · Answer

Hello,

Not sure if you still got this issue.

But me and my colleague ran into the same error as you, and my colleague discovered that putting the cleansing tool into another control container eliminates this error.

I've attached a screenshot for your reference.

Let me know if it ever works for you.

alteryx cleansing tool.png

apathetichell · Answer

Can you open a new workflow and add a data cleanse tool - trying to see if your data cleanse tool got corrupted (ie someone opened it and removed something). It happens.

If that's not the case and it's control container specific - use a multi-field formula. I strongly recommend against data cleanse because it's a memory hog and not an efficient way to clean data.

NeoInfiniTech · Answer

Hello @caiyiyun, while I cannot comment on the version you are using (2024.1.1.71), I can say that on the version I am using (2024.1.1.93), there are no problems with Data Cleansing macro.

It could be happening due to a specific bug that could have been fixed in the most recent patch.

If you are not able to update to the latest version and try again, then I would recommend that you use one of the Formula or Multi-Field Formula tools to replicate what Data Cleansing tool is doing in your workflow.

If you update to the latest patch and receive this error, it could be because of a corrupted Data Cleansing macro (although that is very unlikely).