Classification Rule Builder: Force output to lowercase (RegEx)

Avatar

Avatar
Shape 100
MVP
AndrewWathen
MVP

Likes

574 likes

Total Posts

320 posts

Correct reply

15 solutions
Top badges earned
Shape 100
Bedrock
Springboard
Seeker
Contributor
View profile

Avatar
Shape 100
MVP
AndrewWathen
MVP

Likes

574 likes

Total Posts

320 posts

Correct reply

15 solutions
Top badges earned
Shape 100
Bedrock
Springboard
Seeker
Contributor
View profile
AndrewWathen
MVP

13-10-2016

Some versions of Regex include a "\L" syntax that allows a string to be forced to lowercase.

 

This would be really useful as at the moment the classification that is created reflects the case of the original input - which can lead to messy looking values in reports.

 

For example...

 

Input value:

website.com/PROMotion

 

RegEx:

^(.+)(\/.+)$

 

Mapping rule:

$2

 

Results in:

"/PROMotion" appearing in the report, where as I would prefer "/promotion" to appear in the report

 

Note: this is about the output, not the matching criteria - aware we can already do case insensitive matching

3 Comments

Avatar

Avatar
Coach
Employee
ericmatisoff
Employee

Likes

152 likes

Total Posts

281 posts

Correct reply

78 solutions
Top badges earned
Coach
Contributor
Shape 10
Shape 1
Ignite 5
View profile

Avatar
Coach
Employee
ericmatisoff
Employee

Likes

152 likes

Total Posts

281 posts

Correct reply

78 solutions
Top badges earned
Coach
Contributor
Shape 10
Shape 1
Ignite 5
View profile
ericmatisoff
Employee

14-10-2016

I love this idea. Great suggestion @AndyW 

Avatar

Avatar
Contributor
MVP
joshd7227840
MVP

Likes

275 likes

Total Posts

241 posts

Correct reply

70 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Contributor
MVP
joshd7227840
MVP

Likes

275 likes

Total Posts

241 posts

Correct reply

70 solutions
Top badges earned
Contributor
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
joshd7227840
MVP

21-10-2016

@AndyW - Actually no, we cannot do case-insenstive matching.  CRB is case-sensitive. 

 

A couple years ago when CRB first came out, the regex tester popup (where you enter in the regex and a single key to test against) was case-insensitive.  But when you go to the rule tester (where you enter in multiple keys to show classification results), that was case-sensitive.  And if you actually run the rule, the actual process is also case-sensitive.  

 

This was a bug I reported to Adobe when it first came out.  I asked them if they could either make a flag to specify case-senstivity, or failing that, make everything case-insensitive. Their reponse was to make everything case-sensitive.  Which really sucked.  Because now I have to do dumb workarounds for values like this: ^[Ff][Oo][Rr][Mm]$

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,333 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,333 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

27-10-2020

 
Status changed to: Archived