DATETIMEPARSE: Conversion Error Limit Reached

[AmitMiller]

Hello.

I have a sample file with multiple different date formats.

I'd like to convert all the date formats to the Alteryx date format.

For this, I wanted to use the Formula tool - and have a separate formula for each format:

However, I bump into this error:

DATETIMEPARSE: Conversion Error Limit Reached

I am aware of the DateTime Parse Tool, but it's not helping me, as it can only accept one format.

I assume that the moment this error exists, the work simply stops, which is why I get only null values after the first conversion.

Any help with this? (a workaround would be to check the format of each date via regex before using the datetimeparse(). But that is way longer)

Thanks!

[DavidSkaife]

Hi @AmitMiller 

Error spotting in your code, you're missing the second dot in the format if that helps?

[AmitMiller]

Nice catch!

But this doesn't resolve the main scenario. I will still bump into enough conversion errors to reach the limit, where the conversion will simply stop.

Not sure how to remove this limit. Or change my perspective.

[dYoast]

@AmitMiller 

Could you filter out the common date formats, use the required formula and then union back together?

[PhilipMannering]

This is, I think, an impossible task as there's no way of knowing whether 01.02.2023 is January 2nd or February 1st...

However, I had a quick stab at it. And I know it doesn't work, but you might be able to edit to fit your needs.

[DavidSkaife]

I always understood the conversion error limit to be only for what was reported while the workflow was running, but you can change this in the Workflow Configuration window:

Stop processing is off by default i believe, if you're getting this stopping the workflow it must be switched on and you can up the number per location as well

[Deano478]

This should hopefully assist with what your trying to achieve however it's not a very practical exercise