Designer Entity-Attribute 'Description' storage - where is it?

I'm searching for the Oracle Designer table that holds the Entity-Attribute 'Description' text.
I've found the Entity-Attribute 'Notes' in the CI_ATTRIBUTES table but haven't located the 'Dscription'.
I'm also having trouble locating the 'Description' text for Entities.
My intent is to move all of the text from the 'Description' to the 'Notes' and migrate the text in the 'Notes' field forward. This would be a lot of cut and paste work if done in Designer.
-Ken

Hello
this info is in the generoc cdi_text view available. Txt_type = 'CDIDSC'
Regards Erik

Similar Messages

Designer Entity-Attribute 'Description' storage - where?

I'm searching for the Oracle Designer table that holds the Entity-Attribute 'Description' text.
I've found the Entity-Attribute 'Notes' in the CI_ATTRIBUTES table but haven't located the 'Dscription'.
I'm also having trouble locating the 'Description' text for Entities.
My intent is to move all of the text from the 'Description' to the 'Notes' and migrate the text in the 'Notes' field forward. This would be a lot of cut and paste work if done in Designer.
-Ken

Please ask this question in the Oracle Designer forum: Designer
This is the Oracle Designer Headstart forum. Orade Designer Headstart is a productivity booster for Oracle Designer. Your question is about the internal structure of the Designer repository.

Logical Model - Entity Attribute?

Hi ,
Thanks in responding to my posting.
I am using SQL DM 3.0.0.665. I need your thoughs on following.
1) Do we able to select multiple entities for entity reporting? I find an option for all entities then it ask us to pick only one entity to report.
2) Are we able to build a report for all entities in a subview?
3) I see Formula (Default Value), Preferred Abbreviation and Synonyms for each attribute in Entity Details report. I am not able to find a place to fill those in attribute definitions. Where can we supply those details, so it could print in reports?
Thanks in helping us out.

I find the following for Attribute Properties in SQL DM Help
=============
Attribute Properties
This dialog box displays the properties of an attribute, which is a component of an entity in the Logical Model.
General
Name: Name of the attribute.
Synonym: Synonym for the attribute.
Preferred Abbreviation: Name that will be used for any corresponding table column during forward-engineering if the Use Preferred Abbreviations option is enabled in the Engineering dialog box.
Long Name: Long name in the format: entity-name.attribute-name.
Allow Nulls: Controls whether null values are allowed for the attribute. If this option is enabled, a non-null value is mandatory.
Datatype: Enables you to specify a domain, logical type, distinct type, collection type, or structured type as the data type of the attribute. You can click the ellipsis (...) button to specify further details for the selected type.
Entity: Name of the entity with which the attribute is associated.
Source Name: User-specified name of the source for this attribute.
Source Type: Manual, System, Derived, or Aggregate.
Formula Description: For a derived or aggregate source type, the formula for the attribute.
Scope: For a structured type with Reference enabled, limits the scope by specifying the table in which the type is implemented.
Type Substitution: For a structured type with Reference disabled, or for a structured type applied to an entity, controls whether a substitutional structured type is generated in the DDL.
Default and Constraint
Constraint Name: Name of the constraint.
Default Value: Default value for the attribute.
Use Domain Constraints: Controls whether the properties defined in Domains Administration for the associated domain are used. If this option is disabled, you can use the remaining fields to specify the database type for the constraint and the ranges or a list of values.
Constraint: Enables you to specify a constraint for one or more types of databases.
Ranges: Enables you to specify one or more value ranges for the attribute.
Value List: Enables you to specify a list of valid values for the attribute.
Permitted Subtypes
For a structured data type, lists all subtypes for the attribute, and lets you specify whether each is permitted for the attribute.
=============
but most of the above are not showing up in attribute definition window. How do we see those?

DBSequence type no longer available for entity attributes?

I'm puzzled by this, if not scared.
Every version of JDev till 11.1.1.2.0 has had out-of-the-box support for DBSequence as an entity attribute type.
When you set it for your PK, JDev disables a few options, automatically sets "refresh after insert" (and maybe other stuff) and handles everything about it.
Now, I see that in new applications created with 11.1.1.2.0 that option is no longer present...!
It's available only for apps migrated from previous versions.
If you create a new application, you no longer have DBSequence in the Type dropdown.
Here's what the documentation (Oct 2009 DevGuide, par 4.10.10) says:
In the Edit Attribute dialog, you can set the value of the Type field to the built-in data
type named DBSequence and the primary key will be assigned automatically by the
database sequence. Setting this data type automatically selects the refresh after Insert
checkbox.Where on Earth is this built-in data type named DBSequence in Jdev 11.1.1.2.0?

Thanks Paul.
It seems JDev broke my application.
It only shows the native Java types in the dropdown, and does not show any of the Oracle types including Number, DBSequence and all the rest.
(Note that all the connections I work with use the Oracle type map, of course - it's automatic.)
I tried a new quick test with a new application and again, no Oracle types, just the java types.
Then closed and reopened my applications as well as JDev and I can now see all the types in my quick test.
However, my original application still "sees" no Oracle types, it's stuck with the Java types.
I'll try to see if I can repair it in some way... I'll eventually put it down as one of the gazillion one-time bugs that JDev shows daily.

JBO-26010: Invalid Entity Attribute Name

Hi All,
The requirement is to add a new field on the page but that field is not getting selected in the core EO, so I have extended the EO and than extended the VO based on that extend ed EO.
After that I followed usual steps to import then personalised and added the new field ...bounced every thing but when I am testing got following error:
## Detail 0 ##
JBO-30003: The application pool (oracle.apps.pon.negotiation.creation.server.NegotiationCreationAM) failed to checkout an application module due to the following exception:
oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-29000: Unexpected exception caught: oracle.jbo.PersistenceException, msg=JBO-26010: Invalid Entity Attribute Name "Description" specified for the View Attribute "XxAuctionHeadersAllVO"
===========
When I checked the "XxAuctionHeadersALLEO.xml" it has only entry of new attribute. But in "XxAuctionHeadersAllVO.xml" it has the complete SQL ....so is that can be a problem?
I have run the query from "XxAuctionHeadersAllVO.xml" in toad and it works fine.
Thanks!

Yes it is...:-)
Anyways thanks for the reply..
The Base EO - AuctionHeadersALLEO which I have extended to XxAuctionHeadersALLEO
I have already performed both the steps suggested by you (i.e. option 1) so after Substitute the custom VO "XxAuctionHeadersAllVO" on top of standard VO "AuctionHeadersAllVO" when I tested the change I have got the above error : JBO-26010: Invalid Entity Attribute Name "Description" specified for the View Attribute "XxAuctionHeadersAllVO"
So in custom VO (and also in standard VO) select it's just references it as "AuctionHeadersALLEO.DESCRIPTION" but the field is in AuctionHeadersAllBaseEO.xml not in AuctionHeadersALLEO.xml
so I don't understand how it works in the standard product?
Is it any better? Or do I have to be more clearer :-(

UIX validation entity attribute on page multiple times via different views

We have a situation where an ADF entity attribute appears in multiple views which appear on the same page. Each view selects a different entity row.
When validation fails on one of these attributes, we register an AttrSetValException, as we want to take advantage of attribute level error messages.
The problem is that the validation error message appears for all messageTextFields (for the same entity attribute) when only one of the fields failed validation. Also, the invalid value replaces all input fields even if the other ones were not changed by the user.
I have tried using ex.setNeedsEntityToVOMapping(true) on the exception to no avail. It is as if the entity validation is unable to discriminate between view usages of an entity attribute.
Steve Muench, I have read much of what you have written, but have not seen this particular scenerio. Any advice would be welcome.

The issue is fixed. The reason of the problem that I missed overwriting of the validateParameters() in the custom controller class and the custom parameter was missed from the parameter list and it effected parameter validation error.

Retrieve attribute description to Excel Addin for MDS

I propose a new feature:
retrieve attribute description to Excel Addin for MDS - as
separate row, which would be above attribute-row.
This is especially useful for users - translation into other languages.

Do you think, it would help if we add description as comments of the column name. So user have to hover the mouse to see it?
Also, we already have a work item to support multiple language in the model/entity/attribute name. So based on the client OS, it would show different language for the column name. But I cannot promise when we will deliver it at this moment.

Crystal didn't show the BEx query Attributes description changes/Values

We experiencing the BEx query attributes/crystal report issue.
I create a crystal report using BW- BEx query. Bex query displays the attributes values. But in crystal report side it didn;t show up the values as well as description changes.
But If I change the display properties of attributes (different from one attribute to another) the crystal report reflect the values. But crystal report didn't show the Attribute description changes , the one i did it in BEx query side.
Example:
Bex has a Masterdata as well as attribute Field1, Field2 etc.. I changed the description like Field_Test1 and Field_Test2. Also I changed the display property for Field_Test1 is Key and text and long , Field_Test2 is Text & LOng text.
I got the attribute values is crystal report Xi R2. But crystal didn't reflect the description changes?
Suggestions Please?

Post your question to the Business Object Integration Kits forum

DBSequence entity attribute type not available

Hi OTN,
I want to set an entity attribute type to DBSequence. But there's no such type in a drop-down list, only Java types.
I tried to set the type in source manually but at runtime framework doesn't assign a negative integer to the attribute at Create operation.
In simple test application DBSequence type is available and negative integers get assigned.
I have found a proper thread (Re: DBSequence type no longer available for entity attributes? but the solution there is to recreate the whole datamodel. That isn't suitable for me.
Maybe there is a better solution now?
Jdeveloper 11.1.1.2, ADF BC
Thanks.

I logged Bug 9380578 - "SQL FLAVOUR" AND "TYPE MAP" CAN BE CHANGED IN "PROJECT PROPERTIES"
(published in My Oracle Support).
NB: in JDeveloper 9.x, it was possible to change the "SQL Dialect" (as it was called at that time), but the ADF BC objects and the custom code weren't changed;
hence it was decided to gray out that choice after the Project creation.
Regards,
Didier.

Display entity-attributes and global-attributes in the same screen

Hi,
I have a question about entity.
Is it possible to display in the same screen, entity-attributes and global-attributes?
thanks
Rosalia

Hi Rosalia,
You can only display attributes from the current entity and the entity or entities that it is contained by (the parent entities).
So if you had the following data model
Global
..the person
...the income
the person is contained by global.
the income is contained by the person (which is contained by global).
If you want to create a person-level question screen, you can display global attributes on that screen by using subsitution like %global_field_1%. You cannot, however, input global attributes on that screen (ONLY attributes belonging to the person)
If you want to create an income-level question screen, you can display attributes from the person such as "tell us about %person_name%'s income..." as well as global attributes. Again, you cannot input person or global attributes on that screen (ONLY attributes belonging to the income)
However it only works from child-to-parent containment relationships! You cannot have a global question screen which loops through the person instances and displays attributes from the person, or from the income out-of-the-box.
We have managed to implement this using custom controls.
You can map individual attributes back up to the parent level, and then display them,
such as
the first person's name = InstanceValueIf(the people, the person's name, the person's id = 1)
the first person's name is now a global attribute and can be displayed on global question screens.
Hope this helps!
Ben

Bug: unable to rename entity attribute (jdev903)

Hi,
I have an entity and a view on it.
One of the entity attributes has the wrong name, so I tried to rename it, but jdev gave me a warning that it couldn't rename the attribute because the view is dependent on it. Sounds fair (although I wish it would rename the attribute in the view along with it, (refactoring)).
Then I removed the attribute from the view, and try to rename the entity attribute again. It still can't rename it! I've verified twice to see if the attribute was actually removed from the view, which it was, so this is definitely a bug.
Greetings,
Ivo

Ivo want's to rename the attribute in the entity object without first removing the attribute from the view object. That this isn't possible right now probably isn't a bug, because in your scenario you keep that in mind, so you manually first remove the attribute from the view object. But it would be nice if JDeveloper automatically renames the attribute in the view object too (instead of "complaining" about the dependency). And if you for example remove an attribute from an entity and a view object depends on it, it will ask you to remove the attribute from the view object(s) too etc.

Entity Attributes are not populating while creating EO using EO wizard.

Hi,
I am using JDeveloper version 10.1.3.3.0.3 and E-Business suite12.1.2.
I am facing problem while creating EO using EO wizard.
In Entity Object Editor Entity Attributes are not populating while creating EO.
Please help me resolve this issue.
Thanks & Regards,
Sagarika

Please ensure you click on Tables and Synonyms check box and select proper schema.
Try to select the table from the list after this instead of writing as in 10.1.3 when we write table name it automatically selects from the list if it exists in the list.
Thanks
AJ

Is there way to configure the Time for attribute Description?

Hi All,
We have a requirement that …
If we provide description (Tooltip) for attribute in Fact or Dimension it is displaying in couple of Seconds. Is there any way that configure to change the Time for attribute Description (Tooltip) Display Time ?
Thanks in advance

I should note that the time stays on the left of the event name when I re-enter the text (which I had to do all the time before I found the "show event times" button) so I feel like there's a way.

ADF JDeveloper 10.1.3.4.0 Entity Attribute validation not propagated to UI

Hi,
I'm trying to use entity attribute validation in an ADF Faces / ADFm / ADF BC application. However the validation error
is not propagated through the BindingContainer to my ADF Faces Page. When I customize and override the DCErrorHandler that
is registered on the BindingContext the reportException() method doesn't fire.
Anyone have an idea how to debug this Validation error gone lost ?.
Thanks,
Kenneth

Hi,
is it getting propagated without your custom error handler ?
Frank

[JDev 9.0.3/JClient] ViewObject/Entity attribute: Display Hint ignored?

I have a small problem with the ability to hide ViewObject/Entity attributes in generated JClient Forms. Hope somebody might know a bit more of this issue.
When setting the "Display Hint" to "Hide" on an attribute (of either the Entity or ViewObject), the appropriate JLabel and JTextField (or whatever Swing control is used to edit the value) will not be hidden, neither at designtime nor runtime.
I'm not (yet ;)) an expert when it comes to JClient, but it seems to me that when I tell an attribute of a ViewObject to be hidden, I would expect that the visible property of the appropriate Swing controls be set to false. [ setVisible(false); ]
In some other thread [ http://forums.oracle.com/forums/message.jsp?id=1342592 ] I read that the problem might be related to setting the control hint AFTER the JClient Form was generated. However, in that same thread someone else suggested that the control hint is processed at runtime. So, I've tried both approaches: first setting the control hint, then generating the JClient Form and first generating the JClient form, then setting the control hint. Neither approach worked.
However, I did notice that after I set the control hints, the JClient Form wizard allowed me to hide 'hidden' attributes (which indeed were the attributes which I had specified to be hidden). So that worked ok. But even though I unchecked the hidden attributes box, the end result was still the same: a Form with all attributes on it. Running the project revealed that the controls were not hidden at runtime either.
Am I pherhaps missing something? Or else could this be a bug?
(As the subject indicates, I'm using JDeveloper 9.0.3 Production Release.)

Alright, consider this scenario:
I have a ViewObject with some attributes and in particular the attribute 'X'. In the database table column X is NOT NULL and so attribute X automatically is Mandatory. (This is correctly generated by the BC4J wizard.)
Next, I manually specify that attribute X is invisible (Display Hint). This should cause any bound Swing controls to become invisible when simply browsing the database. However, when inserting a new record, all controls associated with attribute X should become visible (since X is a Mandatory attribute). After the new record has been committed, the appropriate Swing controls become invisible again.
I suppose that this behavior could be the same for non Mandatory attributes, but that's (somewhat) less important.
In case you want a 2nd form in which existing records can be edited (including column X), attribute X should nolonger be invisible. Then the Swing controls bound to attribute X should be removed from the browse form and the 'insert capabilities' of that particular form should be removed as well. The new 2nd should be used for editing/inserting, while the 1st one is for browsing only.
I realise that this scenario may contain a couple of flaws, but it's to give you an indication of what I'd like to be able to do with the existing wizards and attribute editors.
Enjoy :)

Designer Entity-Attribute 'Description' storage - where is it?

Similar Messages

Maybe you are looking for