V_String Settings and Memory Limit Reached message

[Rob48]

I have 2 somewhat related questions that are probably quick and easy answers.  I've upgraded to  2022.3.1.508 this week and noticed when I run a workflow and happen to check a tool output that comes after a disabled container (I frequently disable containers to quickly generate and review partial results and isoloate bugs) the results box gives me the message "Memory limit reached.  Use a Browse tool to view full results."  I get that there would be no results, but this seems like an odd message since in the previous Alteryx version I ran the message would be something like "No data available."  It doesn't make any sense that Alteryx would see this as a memory issue rather than a simple processing issue.  Is this an indicator that I should adjust my memory settings, or just accept that the message is not quite accurate and let it go?

Second question has 2 parts. When setting up a flow out of my source files when I run them into a select tool early on I notice most of the fields come in as V_String or VW_String, and the sizes are set at either 255 or far less depending on the data coming in.  I like to have all my data fields defaulted to V_String unless I need them in a different format so I typically spend alot of time in Select tools manually changing all my text fields to V_String and the sizes to the max of 2147483647.  I just don't like to see later on in my flow a select tool with 1/2 the fields at 2147483647 and the other 1/2 at 255.  

My question is this:

1. is there a quicker way to convert a large number of fields to V_String / 2147483647 besides manually at the start? and

2. If data already comes in as V_String but the size is at 255, am I wasting my time changing the size to 2147483647 since (I assume) Alteryx will adjust if later in the flow the data in that field requires a larger size?

Thank you!

[DanielG]

@Rob48 - no idea about the question on the first part referencing a disabled container.  I'd chalk that up to being on an older version since you are a few years behind. (I feel your pain there, as I am also on a 2022 version.  

For string lengths, just use the Auto Field Tool.  That should make the strings the smallest possible size for the strings that are passed through.  That way you don't have to oversize your fields manually.  When working with small datasets, it really is not much of a performance impact, but it is good practice to make everything as efficient and streamlined as possible.

[flying008]

Hi, @Rob48 

FYI.

[Rob48]

I guess Auto Field is new to my version so I haven't used it yet.  I like the solution that flying008 shows (which is the one I started using recently) b/c I like to have everything in all my flows defaulted to V_String so i don't have issues later if I need to use a join tool and the data types don't match.   I'll probably accept flying008 as the solution but I want to leave this thread open for a day or two so I can see other suggestions.  Thanks!

[DanielG]

Some additional information can be seen here:  https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Discussions/Data-type-String-V-String-V-WS...

Not that V-string is limited to what characters it can house, so if you were to ever receive something with an "out of scope" character I believe the workflow would just make the field null.  which when dealing with millions of rows, might not be ideal.  Perhaps VW_string is better option for you, still using @flying008 's solution.