The contains function does not appear to handle underscore characters?

Question & Answer
, , ,
1

When using the contains function or the contains option on a filter it does not appear to handle a substring with an underscore in it…

Example
mycol="apply_value,here@example.com,another"
contains(mycol, “here@example.com”) will return a 1
contains(mycol, “apply_value”) will return a 0.

Has anyone else encountered this?

Even more basic example
contains(“test_value”,“test_value”) - returns 0
contains(“test-value”,“test-value”) - returns 1

2 Likes
2

Hey @howard , welcome to the QuickSight community!

This looks like a bug to me. Could you raise a support ticket with the AWS team? . Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!

1 Like
3

Thanks @duncan - just submitted.

2 Likes
4

I just ran into this 30 minutes ago… It used to work right? I am not seeing things. I can’t get contains or startsWith to for any text after the first _.

5

Hi, I have encountered same issue with contain function that can not handle underscore

6

same for me, suddenly the _ is not working

7

+1, facing the same issue

8

FYI… I submitted a ticket to AWS for this on Friday and have an open case. Here’s an excerpt from their reply. I’ll send an update when I receive one.

I have taken ownership of this case and will be owning it to ensure you are assisted.

I went through your case and replicated the behavior you found with the contains() function.

I also observed that if an underscore is present in the substring, the function is unable to locate it.

That being the case, I have reached out internally to the team to report the behavior.

I will reach back to you as soon as I have any updates from the internal team on the same.

Thank you for your patience in the meantime.

1 Like
9

Hi all, this is a known regression from a recent QS code change. The team is working on the fix, expeciting to resolve the issue by the end of the week. Sorry for the inconvenience.

1 Like