[Mondrian] Non existent members

Matt Campbell mkambol at gmail.com
Wed Jun 17 16:22:09 EDT 2009

We have an issue with non-existent members in our application and I'm
curious if anyone has any suggestions.  We use Cognos.  Immediately prior to
executing a report, Cognos will fire a series of queries to validate that
all members explicitly referenced really do exist.  For example, Cognos may
execute a query like the following to determine whether [Apr 2002- Mar 2003]
actually exists.


 MEMBER [Measures].[calculated] AS '1'


 {[Time Period: Incurred Rolling Year].[All Time Period: Incurred Rolling
> Years].[Apr 2002 - Mar 2003]}  ON AXIS(0)





Unfortunately, we have sets of reports that a run month after month, and
some specific members may drop out of the database.  Or users may create
reports in anticipation of members that will be available in the future.  We
would like to ignore the non-existent members (i.e. do something just like
what mondrian.rolap.ignoreInvalidMembersDuringQuery does).  Unfortunately,
the validation query will not return the member [Apr 2002 - Mar 2003] (it
returns the null member), which causes Cognos to fail validation and skip
running the report.

Our preference would be to get Cognos to skip the validation step, but there
is no way to do that.  As a fall back, we are wondering if it would make
sense to create a variation on how Mondrian handles non-existent members--
rather than map the non-existent members to the null member, create a new
member with the name specified.  Other suggestions would be gladly accepted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20090617/28bf48c4/attachment.html 

More information about the Mondrian mailing list