There are tons of properties you can set in your design objects.
In fact, I discovered a ‘new’ one this week thanks to my friend David.
#Oracle #SQLDev Data Modeler users please up vote my feature request to allow additional “display as” componentshttps://t.co/2fIbVXmIn9:::
— david schleis (@dschleis) October 12, 2016
Display as…what’s he talking about?
Oh, this.
But what if the set of values we give you for a table or column property aren’t enough? What if you want to document something else?
Enter the User Defined Properties. Note: this is new for version 4.1
Right-click on your design and open your design properties.
And now we can define our custom properties for our design.
I went with a custom list here. But I could have also went with simpler inputs for the property, namely:
- text
- numbers
- dates
Hit save.
Open your table properties, go to the Columns page.
So that’s for columns. But I can set custom properties for tables as well.
Displaying Custom Table Properties in your Diagrams
Just enable it.
So I just showed you this for tables and columns, but you have a lot more flexibility than just that.
Search too!
So once you set these, you can search on them as well.
Advanced Search, and add the property to your search parameters.
And of course, you’ll want this new user defined property in your reports. Just create a custom report template and add your property.
9 Comments
Hi Jeff,
Thanks for the great article.
We can set the dynamic properties using below commands-
table.setProperty(prop_name, prop_value)
table.getProperty(prop_name)
Could you please suggest any method to set/get User defined properties?
Thanks,
Neetesh
Can the User defined properties be set on Views as well? I can see the UDP on tables but not on my views.
Hi Jeff,
Is it possible to get User Defined Properties and their values through the API to use them into Transformation scripts and User DDL Transformation scripts
From the developer:
Every object has methods to get/set UDp/Dynamic properties:
That works for UDP and dynamic properties. In “Table template – uses column name” script there is an example of setting property:
col.setProperty(p_name,column.getObjectID());
For follow-ups, please consult the forums.
Hi Jeff, I am trying to use the Naming Standard Templates for generating the name of the Surrogate Key Column. For this template when you look at the available variables (by clicking on on Add Variable), there is a variable {table singular} for which the description is ‘singularName’ dynamic/UD property of Table. I therefore created a User Defined Property names ‘singularName’ and populated this with the singularName for the entity/table. However when I engineer to a relational model, this singularName is not being used to generate the Surrogate Key Column name… Any idea why?
Hi Jeff, thanks for this post. I am trying to generate a data dictionary with additional user defined properties and found this post very useful. However, the recipe here doesn’t seem to work on 17.2. Can you update the post with 17.2 version?
If it’s not working in 17.2, it’s a bug. No feature changes for 17.2, just bug fixes.
How about a demo of using SQLcl instead of Sqlplus for running scripts after patching with OPatch.
I’ve never used OPatch before, so I’m probably not the best person to do that.