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?

Similar Messages

Logical model cannot refer to 'remote objects'?

Hi
Using DM 3.3.0.747.
In the relational model one can drag and drop in a table from another relational model from a separate design. This shows that table as a linked table and can be refreshed via the 'Synchronize Remote Objects' and allows that table to be referenced from your 'local' tables (i.e. used in foreign keys).
I tried the same, but for a logical model entity. This does not work/is not allowed? What is the expected behaviour?
We would like to use this for logical models as well. (So that we may develop/document the logical models separate, but use common/shared entities in the same way possible in relational models. This will help us a lot in keeping the models smaller and easier to manage and version control.)
Thank you & Regards

Hi Ed,
I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
Please can you provide more detail to help resolve your problem. For example:
Was the problem on an initial engineer from the logical model? Or on a re-engineer?
Are you using Entity subtyping in your Logical Model?
Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
David

How to show relation attribute on logical model

Hi.
How to show child entity relation attributes on logical model?
Entity properties attribute list contains relation attributes, LM dont show they.
I have model with several subviews. I need to show some entity without related entities but need to save "semantic" of relations on this subview. When relation attributes does not visible - no information about invisible relations on this subview.
I can create my own visible attribute like "reference to customer" to make sense the relation with entity "Customer". This case problem is relation attribute presents in entity implicitly and relation model have 2 attribute - my own and generated FK column.
In logical model i can`t replace child table relation attribute to my own "visible" attribute.
In relational model i should redefine FK manually. Transformation script is posible but very odd way.
Any advice appreciated.

I am confused.
I think the legacy Oracle Designer Barker notation could show reation attributes optional or by default, int`t it?
Thanks a lot anyway.

How to change "Relation UID" attribute name in logical model?

Beginner question here, sorry if it has been covered already.
In the Logical model in Data Modeler, how do I change an attribute name which is used as a "Relation UID"?
For example, I create two entities each with a Primary UID called "id", then create a 1:1 relationship. Each entity will now have an attribute called "id1" marked as a Relation UID, but I can find no way to change the attribute's name. Is there a way?
Thanks.

Hi GuyM,
you need to check setting in preferences - "Data Modeler>Model>logical" - FK attribute name synchronization - clear the check box if you want to set the name manually.
Philip

Entity name showing all upper case only in Logical Model

Hi,
Are there any options to show entity names in Logical Model as they were typed in? Both 2.0 and 3.0 will display "Customer" as all caps "CUSTOMER".
Thanks in advance.

Hi,
you need to change the used notation - all caps is used for Barker notation
Philip

Help with logical model

Hi, I am new to this software and need some help with a simple logical model.
Here is the task:
I need to create a model for a parking garage.
Each level can have any number of lots.
There are different types of lots (handicapped, women, regular, ...) with different Prices and Sizes.
It is important for the users and the system to know whether a lot is free or occupied.
It is crucial to assign numbers to the lots, so users can find it again.
And this is my model:
Level 1:n Lot n:1 Type
(#Level) (#Number,*Availability) (#Type,*Price,*Size)
Question:
Is it correct or would you change something? I am not quite sure whether to make availability and level an entity or an attribute of Lot.
Which data types do I need to assign each attribute? What is the difference between logical and domain?
Thanks in advance
Edited by: user13256814 on Jun 2, 2010 3:51 AM

Hi Bhaskaran,
u can see the logs correspoding to your application in the server location..
\usr\sap\<sid>\<instance_number>\j2ee\cluster\server0\
i think ur application folder will be there inside this or within one subdirectory here.
http://help.sap.com/saphelp_nw04s/helpdata/en/fe/4f5542253fb330e10000000a155106/content.htm
U can check the service entries in services file which is located in
<Drive Name>:\WINDOWS\system32\drivers\etc...
but normally in JCO Connection test , if it is not showing errors(especially MetaData) , then it means this entry is there in the services file.
Regards
Kishor Gopinathan

Logical Model vs. Process Model

Some questions on SDDM 3.1.4 support for internal consistency of a design:
1. Can I have the same Information Store on more than one Data Flow Diagram (in the same design)? When I try this, either by creating a new one on the second DFD and trying to give it the same name, or by copying and pasting from the first DFD, the product renames my new Information Store by suffixing a "v1" string to the end of the existing name.
Ideally, the Information Store would not only have the same name on both diagrams, but would be recognized by SDDM as the same "thing," such that a change to the definition in one place would appear the next time it was viewed in the other place.
If this can be done, how?
2. Can I tell SDDM that an Information Store on a DFD and an Entity on an ERD represent the same concept, and should be linked internally? Ideally in that case, attributes of the Entity and data elements of the Information Store would be forced to be synchronized, or at least I could run a report telling me whether they were or not (based on name matching).
If this can be done, how?
TIA,
Mark
Edited by: Mark on Nov 7, 2012 11:50 AM

Hi Mark,
1. Can I have the same Information Store on more than one Data Flow Diagram (in the same design)? yes, when you create store it appears also in global list "All information stores" - using drag&drop from there you can add it to each data flow diagram. And it'll be the same thing.
2. Can I tell SDDM that an Information Store on a DFD and an Entity on an ERD represent the same concept, and should be linked internally? Ideally in that case, attributes of the Entity and data elements of the Information Store would be forced to be synchronized, or at least I >could run a report telling me whether they were or not (based on name matching).You cannot attach entity to information store saying they are the same concept. Moving of attributes (from logical model) between elements of DFD can be presented with information structures you can create (or use) on Flow - so you create Information structure in flow dialog and add attributes from logical model to it. And data store attributes (entities used) is the set of attributes in information structures of incoming and outgoing flows.
Philip

Engineer between Logical Model and Relational Model

I am trying to update changes from one model to the other but there are dublicate entries generated instead of updates.
The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionary.
Our rule is, that the name of Entities/Tables and Attribute/Columns are identical.
So I changed the Naming Standard of the Logical Model in Preferences
from Separator = Space to Separator = Character with char = Underline.
If the entity is not existing, it is created with the correct name.
If the entity exists, a new entity is created with Namev1.
The same happens when I try to update changes in the other direction.
How can I achieve that the existing entity (or table) is updated and not a new one is created?
Or in other words, is there a way to link entities to corresponding tables?
Walter

Hi Walter,
The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionaryit's good to import entities and related tables from Designer repository together. Data Modeler will import the link between them and use that link in synchronization between logical and relational model. After that you can import details for physical model from database.
If you don't have tables in Designer repository and keep the same names for entities, attributes, tables and columns then you can engineer logical model to relational and import details from database.
Philip

Engineer to Relational Model: deleted attributes / undeleted columns

Hello,
I am using Datamodeler 3.3.0.744.
I'm modifying an existing logical model: I'm deleting one or more attributes in an Entity.
Then I'm executing "Engineer to Relational Model" in oder to get an up to date Relational Model (it existed already).
The corresponding columns are not deleted in the Relational Model, even though attributes don't exist anymore at the logical level.
I can't find any option available in order to do that...
In the previous release (3.1), it worked fine, I could choose the behavior related to the deleted attributes (deleting or not deleting corresponding columns).
Edited by: user4995029 on 27 mai 2013 02:43

When your forward engineer for a 2nd time you should see a dialog that has the logical on the left and the relational on the right. Entities that are new or changes have an exclamation point next to them. If you open that you will eventually drill down to see the attribute/columns. Where your dropped an attribute it will say "To drop". The check box is unchecked by default. If you check it then when you forward engineer those should get dropped from the associated table.
Is it not working that way in 3.3?

ODM: How to link DFD Information Stores to Logical Model Entities

I have created a hierarchy of DFDs for my system :).
Some of the DFDs have Information stores on them.
Now I want to specify the Entities in each InformationStore.
I'd like to do this by linking the Information Stores to the Entities I have defined already in the Logical model/ERD.
However... in the Information Store Properties dialog box in the Entities section there is just a [xyz] button ??
I can't see how to link the Information stores on the DFD to my existing Entities.
I was epxecting to see + and - buttons and a dialog box that allowed me to select the Entities I have already created ?
Help !
(are Information Structures somehow involved as they have the + and - buttons) ??

Not good, because I want the Logical Model to drive the processes, not the other way around. The tool seems to be implementing a version of systems analysis that I can trace to DeMarco (1979). This was discovered to be sub-optimal, and documented as such by Flavin (1981), and McMenamin and Palmer (1984). Palmer's later work (unfortunately, mostly unpublished) showed in more detail exactly how the Logical Model should drive the Process Models, not the other way around.
Ideally, an Information Store could be associated to an Entity, and, when the analyst was ready (not before), balancing reports could be run to identify situations where the Entity had attributes that were never created, or never read. Other CASE tools have been able to do this for the last 20 years; it's not rocket science.
I would characterize the way the tool works now as "program-centric" rather than "data-centric."
By analogy, it reminds of a different, but also common programmer behavior, namely pestering the DBAs to denormalize everything, because it saves them (the programmers) from having to code joins.
Don't let programmers drive software methods, or the supporting software tools.
Mark

Problem with a Domain applied to an Entity attribute

I have created a validation domain that has the following logic in it. It is simply to check to see if the account number is in the correct format. I am trying to determine if validation domains at the entity level will serve our purpose. The custom code portion of the domain is listed below.
/**Implements domain validation logic and throws a JboException on error.
This code checks that the account number is in the format 99999.9999.99 July 10, 2007 mb
protected void validate() {
if (mData != null) {
int length = mData.length();
if (length < 9) {
throw new JboException("Account Number must be at least 9 long in the format of 99999.9999 or 99999.9999.99");
char currentChar;
for (int i = 0; i < length; i++) {
currentChar = mData.charAt(i);
if (i == 5 && currentChar != '.') {
throw new JboException("Account Number must be in the format of 99999.9999.9.");
When I apply it to the entity object initially it works well and is listed once on the Entity Attribute Type drop down list. When I test the Application Module at the Entity level (i.e. right click the Application Module and select "test", it initially works well.
Then without explanation, I try to click on the attribute that has this domain applied to it, and I get the following NullPointerException error with the domain listed twice on the Entity Attribute Type drop down list. I can only remove the domain assigned to the Entity Attribute in the structure pane.
Has anyone else seen this?
Mary
UofW
java.lang.NullPointerException
     at oracle.jbo.dt.ui.entity.EOAttributePanel.enableDomainFilter(EOAttributePanel.java:1142)
     at oracle.jbo.dt.ui.entity.EOAttributePanel.updateControls(EOAttributePanel.java:517)
     at oracle.jbo.dt.ui.entity.EOAttributePanel.setAttribute(EOAttributePanel.java:871)
     at oracle.jbo.dt.ui.entity.EOAttributeTabPanel.updateControls(EOAttributeTabPanel.java:202)
     at oracle.jbo.dt.ui.entity.EOAttributeTabPanel.setAttribute(EOAttributeTabPanel.java:189)
     at oracle.jbo.dt.ui.entity.EOEditAttributeTabPanel.attrValueChanged(EOEditAttributeTabPanel.java:316)
     at oracle.jbo.dt.ui.entity.EOEditAttributeTabPanel.enter(EOEditAttributeTabPanel.java:104)
     at oracle.jbo.dt.ui.main.dlg.DtuWizard.selectPage(DtuWizard.java:724)
     at oracle.jbo.dt.ui.main.dlg.DtuWizard.selectPage(DtuWizard.java:699)
     at oracle.jbo.dt.ui.entity.EOWizard.selectPage(EOWizard.java:213)
     at oracle.jbo.dt.ui.main.dlg.DtuWizard.newMddPageSelected(DtuWizard.java:745)
     at oracle.jbo.dt.ui.main.dlg.DtjMddTraversable.onEntry(DtuMddNavigable.java:266)
     at oracle.ide.panels.MDDPanel.enterTraversableImpl(MDDPanel.java:926)
     at oracle.ide.panels.MDDPanel.enterTraversable(MDDPanel.java:899)
     at oracle.ide.panels.MDDPanel.mav$enterTraversable(MDDPanel.java:106)
     at oracle.ide.panels.MDDPanel$Tsl.updateSelectedNavigable(MDDPanel.java:1348)
     at oracle.ide.panels.MDDPanel$Tsl.updateSelection(MDDPanel.java:1216)
     at oracle.ide.panels.MDDPanel$Tsl.actionPerformed(MDDPanel.java:1210)
     at javax.swing.Timer.fireActionPerformed(Timer.java:271)
     at javax.swing.Timer$DoPostEvent.run(Timer.java:201)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:153)
     at java.awt.Dialog$1.run(Dialog.java:515)
     at java.awt.Dialog.show(Dialog.java:536)
     at java.awt.Component.show(Component.java:1300)
     at java.awt.Component.setVisible(Component.java:1253)
     at oracle.jbo.dt.ui.main.dlg.DtjDialog.setVisible(DtjDialog.java:137)
     at oracle.jbo.dt.ui.main.dlg.DtjMddWizardDialog.setVisible(DtuWizard.java:2376)
     at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
     at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
     at oracle.jbo.dt.ui.main.dlg.DtjDialog.showDialog(DtjDialog.java:115)
     at oracle.jbo.dt.ui.main.dlg.DtjMddWizardDialog.showDialog(DtuWizard.java:2315)
     at oracle.jbo.dt.ui.main.dlg.DtuWizard.createMddWizard(DtuWizard.java:500)
     at oracle.jbo.dt.ui.main.dlg.DtuWizard.setVisible(DtuWizard.java:321)
     at oracle.jbo.dt.ui.entity.EOWizard.setVisible(EOWizard.java:223)
     at oracle.jbo.dt.ui.main.dlg.DtuWizard.showDialog(DtuWizard.java:299)
     at oracle.jbo.dt.jdevx.ui.JdxMenuManager.invokeEOWizard(JdxMenuManager.java:970)
     at oracle.jbo.dt.jdevx.ui.JdxMenuManager.invokeEntityWizard(JdxMenuManager.java:948)
     at oracle.jbo.dt.ui.main.DtuMenuManager.doEditMenuAction(DtuMenuManager.java:1413)
     at oracle.jbo.dt.jdevx.ui.JdxMenuManager.handleDefaultAction(JdxMenuManager.java:407)
     at oracle.ide.controller.ContextMenu.fireDefaultAction(ContextMenu.java:343)
     at oracle.ideimpl.explorer.BaseTreeExplorer.fireDefaultAction(BaseTreeExplorer.java:1576)
     at oracle.ideimpl.explorer.BaseTreeExplorer.dblClicked(BaseTreeExplorer.java:1913)
     at oracle.ideimpl.explorer.BaseTreeExplorer.mouseReleased(BaseTreeExplorer.java:1934)
     at oracle.ideimpl.explorer.CustomTree.processMouseEvent(CustomTree.java:176)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1774)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

Frank:
Thanks so much for your reply. I apologize for not saying that my JDeveloper version is 10.1.3.1.0.
And Yes, the error is NOT in the tester, it is received when I click on the Attribute that has the domain applied to it in the Entity Object Editor in the Applications Navigator therefore locking up that Entity Object Editor.
I can only remove the domain from that entity through the structure pane attribute editor AND when I look at the available entity attribute types drop down list, there my domain (which happens to be called UWAcctNumDomain) is listed twice with the path on my 'C' drive preceding the name. When I first created the domain, it was only listed once. Somehow it is now listed twice and that may be the cause of the error.
I am testing the usability of domains for our purposes. We are establishing re-usable business rules for our Oracle tables and establishing them in a Entity Object jar file with all relationships, column titles, history columns, etc. We would like to define as much as possible at the Model layer so that when they are re-used, those business rules are already established and therefore this will save development time.
The reason I used the Java Code instead of Expression Language is simply that I took an example of a formatting domain from page 311 of the Oracle JDeveloper 10g Handbook and customized it for our account numbers.
Any input you have is greatly appreciated.
Mary
UofW

Engineer to Logical Model in SQL Developer EA4 causes problems

I'm working with SQL Developer 3.0 EA4 (Build MAIN-03.97)
Unfortunately I fond out, that it would be impossible to use the function " Engineer to Logical Model" any more after I change the relational model. In datamodeler.log I got the error message line "[AWT-EventQueue-0] ERROR MDBAction - java.lang.NullPointerException" for each time I use the function "Engineer to Logical Model". I try it out with the sample model "sh_cre_all.sql" and with following steps:
1) Import via DDL File – no problem
2) Engineer to Logical Model – no problem
3) Change some attributes in the relational model – no problem
4) Again Engineer to Logical Model – no problem
5) Save, Exit an Open the sample – no problem
6) Again Step 3 and 4 – no problem
7) Add a table via drag&drop from an oracle schema – no problem
8) Save, Exit an Open the sample – no problem
9) Engineer to Logical Model no longer possible!!!
Bernd

I have experienced similar problems with 'Engineer to Logical model'.
The scenario was following:
Creating Logical model using 'Engineer to Logical model' from existing Relational model.
Modifying the Relational model and 'Engineer to Logical model' again. No exception occured but the Logical model wasn't updated accordingly.
Removing all entities from the Logical model.
Trying to 'Engineer to Logical model' again. No entities were created in the Logical model (even after few tries).
So I got to situation where I was unable to generate a Logical model, which was quite frustrating.
The workaround was to create new Data Modeller project and import to it from the original project - the 'Engineer to Logical model' worked again.

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

How convert spaces in logical model to underscores in physical model

Hi,
in Oracle Designer we used spaces in logical model objects (entities, attributes, relations) which were automatically converted to underscores when the physical model was generated from the logical one. Is there any way how do this conversion in Data Modeler? So far I have been able to convert mixed case in logical model to uppercase in physical model (with the exception of foreign keys) but changing space to underscores still eludes me.
Why I think this is important: the logical model should use "normal" language if possible, i.e. spaces, mixed case etc. But the physical model should have uppercase only and definitely no spaces. Having objects in Oracle defined with spaces leads to many difficulties since any reference to the object must use "" around the name of the object...
Thanks
Jakub

Hi,
but the problems continues (even when the model is reduced to no entities at all!)
The error you reported (in engineering and import) cannot be reached if there are no entities and attributes - it's a specific error probably related to usage of distinct types that are removed from design.
You can use search functionality in order to find attributes/columns (logical/relational model) with incorrect data type definition based on distinct type.
And it's better to move to Data Modeler 4.0 (833).
So what to search (example is on logical model - it's the same for relational model - column):
1) Activate search window (CTRL-F when logical diagram is active, or Find icon), switch to advanced mode
2) for "Object type" Attribute:
- check "Data Type kind" line and put DT as search text
- check "Distinct type" line, don't put search text - it'll search for attributes without distinct type
- change the operand for expression from OR to AND
3) press "Find" button
If you find some attributes, then you need to decide what to do with them - to set data type or to delete them.
The same for columns in relational model.
Philip

Logical model fwd engineer to relational model. Missing FK relationships

We are experiencing missing relationships in the relational model when engineering from logical model to the relational model. The logical model objects have properly defined primary keys defined. We are using SQL Data Modeler v3.1.700. Any suggestions on how to engineering these relationships without deleting the objects from the relational model.
Thanks,
Ed

Hi Ed,
I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
Please can you provide more detail to help resolve your problem. For example:
Was the problem on an initial engineer from the logical model? Or on a re-engineer?
Are you using Entity subtyping in your Logical Model?
Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
David

Logical Model - Entity Attribute?

Similar Messages

Maybe you are looking for