If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

how to suppress nulls

Started by ry1633, 15 Aug 2016 10:00:21 AM

Previous topic - Next topic

ry1633

Hi all,

In a query subject I'm working on I have 4 columns:  test ID, product code, establishment code, and status.    When my users pull these into a report, they don't want to see any results where the 1st field (Test ID) is blank.  How can I achieve this?   I may have encountered this before, but have forgotten. (it's Monday morning after a long weekend :) )

ry1633

just tried this with a Filter on the field something like [table Name].[Test ID] is not null  - and that seems to be ok.  Is that a decent way to do it, or is there a better way?

MFGF

Quote from: ry1633 on 15 Aug 2016 10:16:57 AM
just tried this with a Filter on the field something like [table Name].[Test ID] is not null  - and that seems to be ok.  Is that a decent way to do it, or is there a better way?

To quote Mr Punch...

"That's the way to do it" :)

MF.
Meep!

Lynn

Or else address it at the source by either removing data if it truly has no value or modelling over a view that has done the filtering.

MDXpressor

I agree with Lynn,

The closer to your source system you can apply the 'removal' of those records, the better. 

  • If the records are irrelevant junk, get rid of them from the database. 
  • If they serve a purpose not relevant to your BI Deployment, filter them out of the Query Subject in the Framework Model. 
  • If the are relevant to some of your BI, but not most, then create a filter object in your model that people can just drag into place.

The farther you get from source when making changes, the more your authors will end up repeating (read: wasting) effort.
No, a proof is a proof. What kind of a proof? It's a proof. A proof is a proof, and when you have a good proof, it's because it's proven.

-Jean Chretien