I need to get the output from two different universe - one from Order details for customers and other from Customer details.
I tried to put the ‘Inlist’ condition in my customer query to give me only those customers who have orders against them. The order details need to be run for the whole year broken down by date and customer number.
I tried running it in 4 lots (one for each quarter) but it keeps failing and gives “too many values in query filter” error every single time.
The solution for this type of query is to use an exists correlated sub-query to generate the list of orders. IN/NOT IN LIST is not designed to handle huge lists.
If you write it in SQL first then create it in BO it is easier to do
I read it and assumed they were different universes built on the same database or at least in the same server and could be accessed in a single query.
If they are in completely separate databases and this is being done as Query on Query results in a couple of DPs I think that you could well be stuffed. You cannot pass huge long lists that way and expect either BO or your RDBMS to perform
Hi nutty,
Try using merged dimension ,post merged use the dimension from Master query in report and drag and drop the measure from other Data Provider.
This should work by tweaking and prototyping data on report level.
I was asking because it seems like a fundamental design flaw in the universe that these two fact tables would be in the same database but not in the same universe.
What do you mean by that, keep throwing code at it until it works?
Strange customer.
nwdb’s first answer is correct for the short term but I would seriously consider evaluating the universes to try and understand why you’d have orders and customers in two different universes.
(BOB member since 2005-10-26)
