Help obtaining physical model dim level column name please

Question

I admit I haven't read all scripting posts (yet), nonetheless someone may be gracious enough to help me with understanding the object property structure involving physical model dimension level column names.
I imported the following from an 11g instance using a dictionary import (not a DDL file import) into a virgin 3.1.1 data modeler:
create table a_dim as select 1 key, 1 payload from dual;
create dimension a_dim
level level_1 is a_dim.key
The following Transformer Rhino Javascript succinctly exhibits my ignorance:
importPackage(Packages.javax.swing);
function test_get_dim_level_column_name(o)
JOptionPane.showMessageDialog(null, model.getDesign().getRelationalDesign().getSorageDesigns().toArray()[0].getDimensionSet().toArray()[0].getLevelSet()[0]);
JOptionPane.showMessageDialog(null, model.getDesign().getRelationalDesign().getSorageDesigns().toArray()[0].getDimensionSet().toArray()[0].getLevelSet()[0].getColumnSet());
JOptionPane.showMessageDialog(null, model.getDesign().getRelationalDesign().getSorageDesigns().toArray()[0].getDimensionSet().toArray()[0].getLevelSet()[0].getColumnSet().toArray()[0]);
The first result is LEVEL_1 as one would expect but the next two results are: B1ECDFB1-FE64-F728-8AB4-A5E7F098D02D rather than KEY.
I tried prosaic attacks such as getName() and I tried the abstruse things including determining that the class of this hex stringified result is: oracle.dbtools.crest.model.design.storage.oracle.LevelOracle$InlineList
My object inspection of this thingy left me clueless.

Answer 1

Re: “what are you trying to do?
- In the small: learn your object model and distill my ignorance into minimalist expositions
- In the large: The current reverse engineering from Oracle physical dimensional models to the MD model level has worked for me en masse but it seems to be unsuited for incremental development. Also subviews are not supported at the MD level. My goal is to create a transformer script to engineer selected Oracle physical model dimensions to multiple blank MD models and then manually add my subject area fact tables of interest. I expect to develop dozens, if not hundreds, of MD models.
Re: “Did you read README.rtf file in xmlmetadata\doc directory?
- No, I didn’t until this morning – it seems to be new with 3.1.1 since I don’t see it in the integrated SQL Developer Data Modeler 3.1.07 – thank you.
Re: “level.getColumns() - String is equal to level.getColumnset.toString() - it should return comma separated values (usually one) representing object ID
then when you get ID you can use model.getStorageDesign().getStorageObject( ID ) to get the object - the last is written in README.rtf file.
- Using your forum remarks and reading the README.rtf I was inspired to find my sought after “KEY” column name using:
var colid = model.getDesign().getRelationalDesign().getSorageDesigns().toArray()[0].getDimensionSet().toArray()[0].getLevelSet()[0].getColumnSet().toArray()[0];
var colname = model.getDesign().getRelationalDesign().getSorageDesigns().toArray()[0].getStorageObject(colid);
JOptionPane.showMessageDialog(null,colname);
- Thank you for helping with this indirection through the object IDs.
Some remarks en passant:
1)     Nit: getSorageDesigns should be getStorageDesigns as you likely have noted
2)     The developer workflow is clumsy – i.e. having to repeatedly open/close “Custom Libraries” slows down my iterative development. It be nice if I could leave it open
3)     In the integrated SQL Developer Data Modeler 3.1.07,: alt-T(ools) / alt-D(ata) Modeler does not allow progress into submenus
Thank you Philip.
- Kevin