# User tag case sensitive and no longer wild card in the new User Sessions page?

**URL:** <https://community.dynatrace.com/t/user-tag-case-sensitive-and-no-longer-wild-card-in-the-new-user-sessions-page/34652>\
**Category:** Real User Monitoring\
**Tags:** user-sessions\
**Created:** [March 29, 2022, 2:38pm UTC](https://community.dynatrace.com/t/user-tag-case-sensitive-and-no-longer-wild-card-in-the-new-user-sessions-page/34652 "2022-03-29T14:38:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [March 29, 2022, 2:38pm UTC](https://community.dynatrace.com/t/user-tag-case-sensitive-and-no-longer-wild-card-in-the-new-user-sessions-page/34652/1 "2022-03-29T14:38:16Z")

</div>

We, or actually customer, found that with the new release enabled new Users Sessions page by default, that User Tags have to be entered exactly as they occur. In the previous page version they were not case sensitive. I don’t know if this is an handy improvement.

E.g.&nbsp;  
JOHN will neither hit John or john.  
john will only hit john, and John just John

Also, in the old page, the search string entered was enough to search in the whole name of the users.  
Now that does not seem to work. For a brief moment it appears to work after which the tool jumps back to the alphabetic results, or none.

e.g.  
Johns, would have found John Johnson previously. Now it doesn’t.  
John will only find&nbsp; **John** Johnson

Customer contact switches now back to the old page.

I’ll start a chat with support.

---

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [March 29, 2022, 3:07pm UTC](https://community.dynatrace.com/t/user-tag-case-sensitive-and-no-longer-wild-card-in-the-new-user-sessions-page/34652/2 "2022-03-29T15:07:49Z")

</div>

Have confirmed that&nbsp;in the new version to use filters one needs to enter the whole value, it no longer accepts partial values to use as a wildcard.

In my opinion this is quite a step back, the use of user id is quite crucial within this section

---

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [April 6, 2022, 9:04am UTC](https://community.dynatrace.com/t/user-tag-case-sensitive-and-no-longer-wild-card-in-the-new-user-sessions-page/34652/3 "2022-04-06T09:04:24Z")

</div>

Both the customers as myself have made en entry through the Comment option on the new page.  
I’m curious if this has chance to be picked up, or that we would need to raise an RFE to bring back the functionality “taken away” 🙂

---

<div class="post-metadata">

**Author:** ![fstekelenburg](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fstekelenburg/32/22029_2.png) [@fstekelenburg](https://community.dynatrace.com/u/fstekelenburg)\
**Post date:** [May 17, 2022, 9:10am UTC](https://community.dynatrace.com/t/user-tag-case-sensitive-and-no-longer-wild-card-in-the-new-user-sessions-page/34652/4 "2022-05-17T09:10:45Z")

</div>

By looking at the upcoming version, this appears to have been resolved.&nbsp;  
Awaiting the next Managed release update to confirm.  
(as seen in the Demo environment&nbsp;[https://yoj211.managed-sprint.dynalabs.io](https://yoj211.managed-sprint.dynalabs.io))