BusinessObjects Board

Objects.Item(Index) order

sdk development
#1

Hi,

In the Objects.Item(Index) where Index = 1 gives you access to the Object (1) in the collection of Objects. I thought that the Index in this case would be the order of the objects in the object panel, but this is not correct. Does anyone know what the Index refers to, is there any logic to this Index?

Thanks

JTAMBLYN :canada: (BOB member since 2003-05-28)

report metadata
#2

The index takes two forms. One is numeric, and probably represents the order that the objects were created. The second is the actual name of the object (as a string). Either can be used to address an object.

The order of display within a class is controlled by a position field that is stored in the repository tables, but is unfortunately not available to the SDK.

Dwayne Hoffpauir :us: (BOB member since 2002-09-19)

#3

Hi Dwayne,

I’m actually trying to automate the documentation of the Aggregate Navigation matrix. It seems to be working but is very slow as I’m loading all objects in the sheet first and then if an alias has incompatible objects I loop through the objects in the spreadsheet. So if an alias/table has 400 - 500 incompatible objects you can imagine how long it takes when there is no logic to the index of the object in the collection vs the order to which the objects are in on the spreadsheet. The order of the objects in the spreadsheet matches the order in the object panel. Currently I’m looping through checking whether the name of the incompatible object matches the name of the object in the spreadsheet. SLOW :sleeping: So I was hoping there was some logic to the index in the collection and maybe I could sort the objects in the spreadsheet first and then sort it back to the way the objects are shown in the universe (object panel)

JTAMBLYN :canada: (BOB member since 2003-05-28)

#4

While you are “loading” the objects, are you by chance “touching” the .LOV property? Even if just “touching” the .LOV.Name property, it actually RUNS the query behind the LOV! That would slow things down tremendously.

Dwayne Hoffpauir :us: (BOB member since 2002-09-19)

#5

Hey Dwayne,

I’m not touching the LOV this time, you had actually given me this advice in another thread (thanks again). Issues seems to be this, I have lets say 14 tables that have incompatible objects, most of these tables have somewhere around 400 - 500 objects that are incompatible, and the universe itself has 650 objects. The way I am comparing these objects seems to be the problem, its fast but has too many iterations as you can imagine from the above scenario if just looping through the object names in the spreadsheet comparing to the object name in IncompatibleObjects. I’ll have to do a bit more thinking and some more investigation :yesnod: Let’s see what I find.

JTAMBLYN :canada: (BOB member since 2003-05-28)

#6

Sorry for the redux :oops: … the memory is not what it used to be :roll_eyes: !

Can you mock up a small spreadsheet that demonstrates the end result? That may help me visualize a possible quicker algorithm.

Dwayne Hoffpauir :us: (BOB member since 2002-09-19)