Many thanks to Marianne Wagt, James Cull, and Dave Rathbun for your responses to my question on linking multiple data providers and Dimensions vs Details.
After submitting my question to the list, I visited the list archives at http://listserv.aol.com/archives/busob-l.html and researched the subject. I found many previous postings on this (sorry, I guess I should have checked first). After reading everything, along with the minuscule amount I found on the Business Objects web site, I feel I have a healthy understanding of the concepts. I was able to get it to work by changing some of the objects to Detail objects.
Problem: I have my objects all organized into various logical groupings (Classes) such as Change Requests, Priorities, Statuses, etc. When I changed the objects in my Priorities class to Detail objects, I was prompted to select the Dimension that this object was a detail of. I selected Change Request Number which is in the Change Requests class. BO immediately moved the object out of Priorities and into Change Requests under the Change Request Number. This messes up the logical class groupings I have in my universe. I moved it back under Priorities, but then it lost its reference to the Chg Req Number dimension. Subsequently, when I used the new detail object in a report, since it didn’t know what the related dimension was, it put an additional object in the Query Results window, labeled with a Red Triangle with an exclamation point inside. This is kind of sloppy for the users to have to deal with. Question: How have you dealt with creating logical Class groupings in regards to detail objects? Do you just let all the details sit under their related dimensions? If so, wouldn’t (normally) almost everything in a single table be a detail of the primary key? (Sorry so long winded)
Roger Poole
rpoole@nswc.navy.mil
Listserv Archives (BOB member since 2002-06-25)