Case sensitivity issue using Impromptu with Costpoint

[iguanadon]

I am conjuring up the great minds of Impromptu to guide me (actually to save me from hours of searching for an answer).

Dave Griffin, I'm willing to bet you have the answer on the tip of one of your brain cells.

I have reports gathering data from Costpoint by Project. Apparently in some of the journal entry uploads, some of the project numbers are coming up in lowercase if they have an alpha character in them. My Impromptu reports are grabbing the rows of data just fine whether in upper or lowercase, however, when the data is grouped for summing or whatever, that's when it splits it out into separate groups.

Is there any "setting" within Impromptu to ignore case sensitivity entirely?

Example. Project 08858.001.T13 and 08858.001.t13

Build a filter to bring in 08858.001.T13 and it brings it in even if it's t13 (which I'm very grateful for), but then it creates 4 separate rows when grouped on Proj. (It creates a grouping until it hits a different case, groups those together til it comes across a change in case again, and switches back and forth until it runs out of rows of raw data by the way)

Thanks in advance, sorry for the long winded explanation.

Scott

 

[griffindm]

Scott,

There is no application setting to have Impromptu ignore case. What you can do, however, is define those case-sensitive data elements in your report with an Upper function, so that the report converts them to upper case before filtering, grouping, or sorting. To do this, just add the element (such as project) to your report, and immediately change it's data definition to use the Upper function. Then make sure all of your use of that element refers to the report object, rather than a catalog reference of the same data element. This will solve your issues, as all operations will operate on the column as if it were in only upper case.

Hope this helps,

Dave Griffin




The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
Want good answers? Read FAQ401-2487 first!

http://www.decisionsupportgroup.com

 

[iguanadon]

Thanks Dave, yes, I was hoping to avoid using the "upper" function because I'd have to check all 1700 of my imr's to see if they have grouping on the project number.

I'm trying to get my system admins to try to get everything in upper during the upload process so it's a moot point on my end.

Thanks for the quick reply and confirmation that there wasn't something I could do with an Impromptu setting or ini change.

Scott