# Dimension member case sensitive issue

**URL:** <https://community.eazybi.com/t/dimension-member-case-sensitive-issue/11991>\
**Category:** Questions & Answers\
**Created:** [March 9, 2023, 6:17pm UTC](https://community.eazybi.com/t/dimension-member-case-sensitive-issue/11991 "2023-03-09T18:17:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![priyavenugopal](https://community.eazybi.com/letter_avatar_proxy/v4/letter/p/e68b1a/32.png) [@priyavenugopal](https://community.eazybi.com/u/priyavenugopal)\
**Post date:** [March 9, 2023, 6:17pm UTC](https://community.eazybi.com/t/dimension-member-case-sensitive-issue/11991/1 "2023-03-09T18:17:34Z")

</div>

Hi EazyBi experts,

I’m a beginner to EazyBi Reporting. Please could you help me with this below query. Thank you in advance.

We have a dimension named Component and i see that there is one component name which is actually named as ‘.Comp\_XXXXXX’ in Jira. But in EazyBi i couldnt view any results w.r.t this component filter though there are enough tickets under this component in Jira. When i tried troubleshooting, i see that there are 2 components displayed in this dimension, one as ‘.Comp\_XXXXXX’ and another one as ‘.comp\_XXXXXX’ where even if i try adding the bookmark as .Comp\_XXXXXX’ and refer it in the filter, but after the report is saved and opened again the bookmark gets changed as ‘.comp\_XXXXXX’ and not remain the same what i added ‘.Comp\_XXXXXX’. Please help me understand why this happens so and what am i missing to do to get the right component in the page filters. Thank you.

---

<div class="post-metadata">

**Author:** ![martins.vanags](https://community.eazybi.com/user_avatar/community.eazybi.com/martins.vanags/32/8905_2.png) [@martins.vanags](https://community.eazybi.com/u/martins.vanags)\
**Post date:** [March 20, 2023, 6:19am UTC](https://community.eazybi.com/t/dimension-member-case-sensitive-issue/11991/2 "2023-03-20T06:19:03Z")

</div>

Hi @priyavenugopal

eazyBI has challenges importing the same field value in different use cases as separate members in the dimension.  
When a value from multiple cases of the exact text is imported as a dimension member, the calculations can go unpredicted.

We recommend keeping just one version of the field value for import; then, eazyBI would not have problems importing the value as a dimension member and let you use this member in reports from the dimension.

OR you could use a [custom Javascript code](https://docs.eazybi.com/eazybi/data-import/data-from-jira/advanced-data-import-options/custom-javascript-code) to add some prefixes or suffixes for one the value versions and then import them as two different members for the dimension.

Martins / eazyBI