idea Re: Change Compose to handle case sensitive information - Status changed to: Closed - Declined in Suggest an Idea

Change Compose to handle case sensitive information

ShireyJW — Thu, 16 Jul 2020 16:08:48 GMT

Compose needs to have a setting to handle case sensitive information. Currently, the product will mis-assign descriptions to codes if the source is "case-sensitive".

We have an SAP S4 source that is sending information similar to this:

Code Description

------ ---------------

A Very Good

a Not so Bad

--------------------------

Compose is loading only one row as "a" and assigning both descriptions to it ( because it is case insensitive). Is there a way to control this behavior?

The value for this change is to correctly map all sources into the data warehouse appropriately.

Re: Case sensitive information is seen as duplicate - Status changed to: Closed - Declined

John_Teichman — Tue, 14 Jul 2020 04:45:00 GMT

Hello @ShireyJW,

I do not see an actual Idea submission. Please contact support.qlik.com or post in the Data Integration forums for assistance. Refer to the Idea submission guidelines for more details.

Re: Case sensitive information is seen as duplicate

ShireyJW — Tue, 14 Jul 2020 12:12:45 GMT

Why has this been closed? Will I be wasting my time if I edit it now? What constitutes an "actual idea submission" vs. what I submitted?

Re: Case sensitive information is seen as duplicate

John_Teichman — Wed, 15 Jul 2020 06:40:25 GMT

Hello @ShireyJW,

This was declined because the post does not suggest an idea but instead asks a support question. As mentioned in my previous comment, support issues / questions should be taken up with Qlik Support or asked via the other forums. If you want to edit this post, I will re-open it.

Re: Case sensitive information is seen as duplicate

ShireyJW — Wed, 15 Jul 2020 12:01:11 GMT

Yes, reopen it.

Support is who told me to create this idea. They also have closed my support ticket because they feel it needs to be a feature request instead.

Unfortunately, I still have a problem using the product and the suggested idea is to handle case sensitivity better.

Re: Case sensitive information is seen as duplicate - Status changed to: Open - New

John_Teichman — Thu, 16 Jul 2020 05:18:25 GMT

@ShireyJW - re-opening this idea. Please update the post to include the idea being suggested.

Re: Change Compose to handle case sensitive information - Status changed to: Closed - Declined

Tzachi_Nissim — Mon, 17 Aug 2020 11:28:49 GMT

Hi ShirleyJW,

Thank you for your suggestion. My current take on this is that this should be changed in the database to make the database case sensitive. I don't see what Compose can do otherwise. Please feel free to open this as a support case if you disagree.

Regards,

Tzachi

Re: Change Compose to handle case sensitive information - Status changed to: Closed - Declined

ShireyJW — Mon, 17 Aug 2020 14:15:44 GMT

It started as a support case... and Support told me to create this as a Feature Request. What now? (especially since you closed my feature request and support closed my issue... yet I still have a problem)...

Re: Change Compose to handle case sensitive information

Tzachi_Nissim — Tue, 22 Sep 2020 08:15:34 GMT

Hi ShirleyJW,

You can change the database collation to be case insensitive. For Compose to do this would be extremely inefficient as every lookup to find a key match will have to be using a function (uppercase to both sides). The database can do this much better. You did not explain why you cannot do this in the database using a case insensitive collation. Maybe there is something we don't understand here, so please explain this. Maybe something like SQL_Latin1_General_CP1_CI_AS where the "CI" part of the name is "Case Insensitive" comparison, which is exactly what you asked for.

Regards,

Tzachi