Regex Parse Expression Not Updating with Listbox and Action Tool for Macro

I don't know if anyone has ever run into a problem like this. I have tried every different configuration of the listbox by manually inputing my names and values or doing it in an external input (excel sheet). Whatever I do the value won't update in the regex parse expression when I run my macro. It just reverts to the default value that was in there when the macro was configured. If anyone can help I would appreciate it. Thanks!

Regex

Parse

Accepted answers

All comments

DataNath

For the manual input, the options should be on individual lines like so:

If you wanted to display the following as plain text for the user, with the correct values working behind the scenes then it'd be:

One:1

Two:2

Three:3

With NO spaces between the colon when setting up in 'Name:Value' format.

If using an external sheet, have you ensured it's in the following format (i.e. has name & value headers)?

tstowell

Hi @DataNath @Thanks for replying! My names and values for my drop down list are fine. The problem is trying to update the marked fields for the regex parse. The original macro had one marked field as RegExOut1 and then the list trying to update it has 29 marked fields. Does that make sense?

DataNath

I'm guessing you need this to be dynamic as you'll have other words in the dropdown with different expressions/# of capture groups? Or have you just acquired a macro that you're trying to change the RegEx expression for? If it's the former, I've been having a look around and can't seem to find a way of dynamically doing this.

tstowell

Yeah! It needs to be dynamic. I'm glad I'm not going crazy, I've tried everything. I will keep trying things, but thank you for responding!

DataNath

Thought as much! Are you able to provide more context? Perhaps a couple of the options that you'd like in the dropdown (in terms of the input and expressions/what needs capturing) and what the desired outcomes are? Can then try and figure out a fix (though this one seems a bit tricky!)

DataNath

@tstowell just had a re-read of your earlier messages about needing it under one column and think I've identified the real issue here - the RegEx itself. The reason Alteryx is trying to break it up into 29 is because you have the 29 lots of (). I think we need to re-look at your expression as it doesn't really make sense, especially if you really do just want it in a single column. Let's just take your first 3 capture groups for example; (.{5})(.{2})(.{17}). With the use of the wildcard (a full-stop in RegEx), you're not being specific on any level so these groups alongside each other are telling Alteryx to return the first 5 of ANY characters, then the next 2 then the next 17. In a string containing 'I love data, it's the best' this would literally return (I lov)(e )(data, it's the be), which wouldn't be an issue if you wanted them split up into multiple columns, but consolidating them under 1 would literally just return the original string (as shown below, with a single capture group), in order, as it was. Again, if you can provide a couple of example inputs/desired outcomes we can revisit!

tstowell

I can provide an example of the txt file in a little, but it comes in one column as a long string of text. I know how many fields need to be in each column and that’s why I do the (.{5}). I want it to break it into 29 (or however many) different columns. I don’t think one big expression or column would work.

tstowell

@DataNath Hello! I am attaching an example I created with my problem. The summarize contains the regex string that I am trying to put into the regex tool with a list box. I know all of the regex strings that I need and that is why I can manually fill in the list box, like we discussed before, the problem is the number of fields for the different data changes. I found a soultion by just getting rid of the list box option and just doing different input nods on the macro tool, so if you don't find a solution it is perfectly okay. Thanks again for helping.

Regex Problem Example flow.yxmd

DataNath

Hey @tstowell, cheers for this! Have had another look and really can't beat this one. There's no options for dynamically changing the number of capture groups so unless somebody can find a genius workaround I think we'll have to stick with your solution!

tstowell

All good, that’s what I thought! Thanks again!!

DataNath

Apologies for digging up an old thread here.

@grossal - took a good chunk of digging but finally found it. Not fully refreshed myself on the problem but I believe this relates to what we were discussing!

apathetichell

I don't think what you are trying to do will work - at least not that way. Let's take a step back at what you are doing:

1) you have you original workflow - a field has a single regex marked group which is parsed to a single new field.

2) You have a drop down - with 19 marked groups - these will presumably create 19 new fields.

3) Your action tool is set to update the 1 marked group with 19 new marked groups.

This does not work. You need to do two things - 1 update the regex expression. 2 - create new fields for each of those groups. You cannot do 2 - with a second action tool (perhaps editing the raw xml - but probably not worth it).

Does this mean you cannot do it? There's probably a way - I'd use a batch macro. In a batch macro you would use a regex_replace in a formula tool where you would basically identify which marked group (1-19) you were looking to extract from your field. You would then rename the field. You would then set it to union by name. Then you'd probably to clean it of some nulls().

apathetichell

I was thinking about this - and really this should be done by a detour/container/macro - with a regex tool configured for the additional marking groups. Your dropdown should be triggering that tool - not replacing the characters in that tool. This would prevent the schema additions that parsing n marking groups vs 1 marked group create.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703