Fwd engineering entity name changes to relational model?

I changed an entity name in my logical model after generating a relational model. But, I cannot figure out how to have SDDM (3.0.0.665) propagate this change to the relational model.
In the Engineer To Relational Model screen, if I select the changed entity from the tree view, in the Details pane there is a "Selected" check box next to the Name property (this line shows the discrepancy between logical name and relational name) but I can't check it. Under the Compare/Copy Options tab in that same dialog, the check box next to Name is checked. But, when I forward engineer the name is not changed.

BTW I just noticed that if I enable "Name Translation" then it seems to work. This is not at all intuitive or obvious, nor does it seem to be explained in the documentation.
According to the help:
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.

Similar Messages

  • Display extra information in entity header of the relational model

    Hi,
    Is there a way to display extra information in the header of the entity, next to the table name.
    Ex : each table in my model has a distinct object id. Right now I enter this info in the Dynamic Properties (Name = OBJECTID Value = 710). It would be really practical for me if that OBJECTID would appear in the relational model diagram.
    Thanks.

    No, it's not possible
    Philip

  • Power View Enhancement Request - Allow for columns to drop off PowerView when column name changes in data model instead of rendering the PowerView inaccessible

    Currently in PowerView, if a column name changes in the tabular model, and that column is being used in a PowerView chart, the PowerView will become inaccessible.
    It would be nice if it functioned similar to Pivot Table. If a column name changes for a column that is being used in a Pivot Table, the field is just removed from the chart, and the user can select the newly named column. 

    Hi plantm,
    After testing the issue in my environment, I can reproduce it. After we change a column name which is used in a Power View chart, Power view will render the message that” The external data connection has been disabled for this Power View report. Please enable
    the connection.” when we reopen the file.
    To fix this issue, we can click Refresh button under POWER VIEW menu, then it would prompt us that” Power View was not able to complete the action due to a query failure. This can happen if the structure of your data has changed, in which case closing and
    re-opening the application will resolve the problem.”
    According to the error message, we should try to reopen the file to fix this issue. Power view will render the message that” Please refresh to see the data for this Power View Sheet. You can set properties in the Connection Properties dialog so that the
    data refreshes automatically when you open the file.” when we reopen the file. Then we can refresh it again, the report will be displayed without that field.
    Based on my research, inherently what the message means is that Power View cannot be used as a tool for snapshot reporting. With an Excel PivotTable, we can see the data last saved in the PivotTable. Power View, however, does not behave the same way – it
    won’t render the last saved state. If we want to avoid this message when we reopen the file, there are two methods:
    When we create the Power View report, we can select the checkbox that “Refresh data when opening the file”.
    After it’s been set up, go to Connections on the Data menu, then choose Properties.
    For more details about the settings, we can refer to the following blog:
    http://www.sqlchick.com/entries/2013/3/30/creating-a-power-view-report-in-excel-2013-which-uses-an-ext.html
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Adding size to exisitn domain not changing in relational model

    Hi all,
    I defined a domain type of integer without any size. I now know the size and have changed the domain type but the column definitions in the relational model dont have the new size. What am I doing wrong?
    thanks
    Magnus

    Hi Philip,
    once again you are the font of all modeller knowledge, thank you very much
    regards
    Magnus

  • How to change the attribute name for a relation

    When the Data Modeler engineers a logical model into a relational model it create table columns for the relations. The names of the generated columns are listed in the attributes list in the properties dialog of the relation. The actual name of the attribute gets calculated by the attribute name of the entity which is part of the relation. This is okay, if there is only one relation between two entities. But when there are two relations between two entities the second attribute gets a stupid number suffix. This makes it impossible to give the attribute a useful semantic meaning.
    When I engineer the model into a relational model I can change the column name in the relational model. Changing the column name in the relational model is not perfect but it would be okay for me, if it would not be overwritten during the next engineering run.
    So I have two questions:
    How can I change the attribute name in the attributes section of the properties dialog of a relation? See here for screen shot:
    http://public.ceving.de/2012050300/relationattribute.png
    And if it is not possible:
    How can I preserve any changes on column names in the relational model during a re-engineering run?
    Edited by: 931739 on 03.05.2012 08:07

    Hi,
    I've logged an Enhancement request on this.
    I don't believe it's possible to change it from the Entity or Relationship dialog, as it's not updatable in these dialogs.
    What you can do is change it in the Relational Model, and then reverse engineer the change back to the Logical Model.
    David

  • Sql datamodeler: Engineer to relational model: General Options

    Hello
    When you engineer your logical model to a relational model you get a wizard. In lower part of this wizard byou have several tabs, one of the tabs is called general.
    On this general tab you have check box: Apply Name Translation
    The corresponding help text:
    Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.
    Does anybody have a clue what is meant here?
    Regards Erik

    Erik,
    you have to create glossary (tools>Glossary editor) with words permitted for usage in names in logical model. For each word you can define abbreviation that will be used in transformation process.
    Example:
    Employee - EMP
    Salary - SAL
    Attribute "Employee Salary" will be transformed to column "EMP_SAL".
    You can define preferred abbreviation for entities and attributes and it can be used instead of glossary definitions.
    You also have to set your glossary in "Tools>General Options>Naming standards>Glossary"
    Best regards,
    Philip

  • Renaming Foreign Keys in the Relational Model

    Hi,
    I'm new to Data Modeler, we are using v 3.0.0.66.5 and Oracle 11g, and I'm trying to build a Logical and Relational model for a new application.
    We always name our Primary Keys as ID, this is causing me a problem with my Foreign Keys names in the Relational Model, as they are showing as ID#. Is there a way to add the abbr. of the table to the Foreign Key?
    Thanks in Advance
    Sue

    I always do that job using Naming Standard Templates. This sequence renames ALL FK COLUMNS for ALL TABLES only in RELATIONAL MODEL:
    -Preferences > Data Modeler > Naming Standards > templates
    -into the box "Column Foreign Key"
    -Put something like that: {ref table}_{ref column}
    -Then, go into your modeler tree, select the relational model, right click and use "Apply Naming Standards to Keys and Constraints"
    -deselect all
    -select the last option "Column Foreign Key"
    -Go.
    What if the names still collide? What if you want to do the job for some--but-not-ALL tables? forget the method above. A transformation script will do that.
    You'll need some of these building blocks:
    - table.getFKAssociations()
    - keys.getRemoteTable().getAbbreviation()
    - column.setName()
    I'm novice to script coding, sorry I can't assemble a scripted solution right now.
    Edited by: T. on May 31, 2011 8:50 AM

  • DM3.0 EA2: Filter engineering changes between logical and relational model

    Hi,
    when I am engineering changes between logial and relational model there are some issues at filter handling for me:
    - When the filter "Show Modified Objects" is activated, the filter works only on the first level, e.g. on Entity level. On attribute level all attributes are displayed, not only the attributes which have really been modified. It is possible, to show on every level only the really modified objects?
    - I think, selecting a Filter condition is circuitous. All filter conditions except "Show All Objects" keeps activated when I choose another condition. So I have to deactivate "Show Deleted Objects" when I want to see only the modified objects. It is possible to choose another control element for filtering, e.g. disjunctive radio buttons?
    I am running Data Modeler on Windows XP with german localization and the JDK 1.6.0_11 from Oracle SQL Developer.

    I logged bug for that.
    Philip

  • Problem when engineering to relational model

    I have modeled everything in Logical model and then engineered it to the relational model. Now I have to make some changes, and I'm doing them in Logical model. When I'm engineering it to Relational, although I just altered one single item, I see that it's also bringing some other entities as altered. Inpecting these I see that all of them relate to identifying foreign keys with more than one column. For examplo, I have an entity with 2 columns as primary key, and a second entity with an identifying foreign key to the first, and a third column, based on a sequence, which, all three of them, are the second tables primary key. Everything is OK, I haven't changed anything on any of these entities, but when I'm engineering to relational, it creates a duplicate of one of the columns on the relational model, and alters it's name appendig a number 1 after it. If I try engineering again, it is going to create another column appending a number 2 and so on.... I think this is a bug.... am I right?
    My alternate solution is to drop the foreign key on the relational model, thus dropping both columns, and then engineering from Logical again. Everything keeps working fine, until I close my model. When I open it again, the same problem reappears....

    Philip,
    Sorry for my too late reply, as I forgot to flag this discussion to notify me via e-mail. Thanks for your response, but I was actually using DM 4.0.1.836 and this issue still persisted.
    I just downloaded DM 4.0.2.840, and the issue still persists. I just opened my original model and, without making any changes, tried to forward engineer from logical to relational, and it brings up differences on exactly the same tables.
    Wolf
    P.S.: I've gone through the motions of dropping the FKs on the relational model, dropping any orphaned columns (from these FKs) and re-engineering. Afterwards, I saved and closed all models, closed the application, opened it again and opened my model and the issue persists.
    I also created a new model, with some tables using the same principles, and no error occurred, although in this new model I didn't create a physical model.
    Is it possible that something is wrong with my original model?

  • New Guy Question about Name Changes from Logical to Relational

    Sorry for the "New Guy" question. I am trying to do this the way I wished it worked rather than the way it does.
    Lets say I have an Entity named "Current Database" with an Attribute named "Current Database Name". All this is in plan english for the Logical Model. Now when I generate the Relational Model I would like the Table named "CDCD_CURRENT_DB" and the column named "CURRENT_DB_NAME".
    I have been working with a Glossary and some other features trying to get this to work. It kind of does but I do not fully get it and I think I am missing out on much of the power of the product. I have been forcing the Nickname "CDCD" (As we call it) and the "Database" to "DB" in the "Preferred Abbreviation" of the Entity.
    I am working with v3.3.0.734
    Thanks for the help.

    Hi Sky13,
    it can be done with glossary but it looks to me what you want is not that native to glossary approach.
    it's good to look here for basics http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
    Example here also could be useful if you want to go with glossary - Re: Data Modeler: Naming
    If you want to use preferred abbreviation then it should be CDCD_CURRENT_DB.
    For me CDCD_ is just a prefix - you can handle it separately in relational model - on whole model, on subview and in both cases classification types also can be used to determine how objects are prefixed.
    You don't want Current to be abbreviated then do not put it in glossary however you need to check "Incomplete modifiers" check box in glossary.
    Entity property "Short name" goes to table abbreviation during engineering. There is a transformation script which will prefix table columns with table abbreviation if you need it. And another one can remove the prefix.
    You can define plural name in glossary and if entity name is a single word then plural will be used during name translation.
    Philip

  • Engineering to and from logical and relational models

    I have tried to modify a logical model entity by adding an attribute or two, tried to engineer to the associated relational model, only to have the engineering process create a brand new table rather than adding the new column or two to the existing table.
    Creating the column in the table first and engineering back to the logical model didn't appear to do anything, although I might have missed a new logical entity.
    Is this how the product is supposed to work?

    Hello,
    I'm sorry but your steps are not evident for me.How it works - you can start from table or entity, it doesn't matter which one is first you should be able to synchronize changes.
    Let's assume you have two relational models RM1 and RM2 and table TABLE_1 in RM1. if you engineer RM1 to logical model then entity will be created that corresponds to TABLE_1 in RM1 (and it will be named TABLE_1 if you don't use glossary that provides replacement of TABLE with something else).
    You can add attribute to entity and engineer logical model to other relational model (RM2) - new table will be created in RM2.
    Add one more attribute to entity and engineer to RM1 - two attributes will appear showing that two new columns can be created - they are not selected and you have to select them if you want columns to be created.
    You'll get only one new attribute (column) if you engineer to RM2 - the first added attributed is already there as column.
    Of course you can add columns in tables and can synchronize them with entity in logical 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

  • SQL Datamodeler: engineer to relational model: column names

    Hello
    Suppose I have an attribute called DAY OF BIRTH. Is there a way I can forward engineer this attribute to a column name DAY_OF_BIRTH?
    (I know you could have a coulmn name "day of birth" but thats not what I want)
    Regards Erik

    Hi Erik,
    1) you should check separator settings in General options>Naming Standard -it should be "space" for Logical model and "underscore" for Relational model;
    2) "Apply name translation" should be selected in engineering dialog
    Best regards,
    Philip

  • Engineering logical subtypes to Relational model

    I have a logical model with subtype (box in box). When I forward engineer to a relational model there is nothing in the model to represent the subtypes. I was expecting (as in old Designer) to see a differentiator "type" column to be generated with a column check constraint based on my subtypes. In the logical model I selected "single table" as the implementation strategy.
    Note I also have these entities tagged as Dimensions and did notice the engineering dialog showed the substypes as hierarchies too.
    Am I missing a a preference setting somewhere?

    Hi Kent,
    I was expecting (as in old Designer) to see a differentiator "type" column to be generated support for that will be added later.
    Note I also have these entities tagged as Dimensionswhat do you expect - if you change implementation from "single table" to something else you'll get tables also classified as dimension, no other magic will be involved
    and did notice the engineering dialog showed the substypes as hierarchies tooI don't see your point here.
    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

Maybe you are looking for