Vote for your favorite Qlik product ideas and add your own suggestions.
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:
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.
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.
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?
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.
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.
@ShireyJW - re-opening this idea. Please update the post to include the idea being suggested.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.