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.
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 am aware there is a post already on this problem, however, my workflow contains no union tool as is discussed in the other post and still I get this problem. I have no idea how to get my workflow to run.
Sorry, I am a bit of a noob still especially when it comes to certain terminology. When you say 'reading the yxdb in a seperate module' do you mean can I open the file in a different workflow? If so then yes I was able to browse/output the file. If not can you elaborate please.
Still got the same error when recreating it, even when we recreating the input file. But I think I realised why, the generalise was being used on a file that had already been processed by the tableau polygon macro so I think that may have been why it was giving an error (although the error doesn't really indicate this at all). You think so too?
Note: I found another possible cause of this error. I had a situation where a function tool created a VString with a huge maximum character count, and even though most of those characters were null, cutting down the size to something like 20K allowed my flow to go. It was failing at join time until I truncated the maximum length.