Logical diagram's relation lines invisible

In my logical diagram and its subviews, a few of the lines (maybe 10%) representing relations aren't appearing between the entities.  The relations exist and appear to be defined just as the ones that do appear.  In "Show/Hide Relationships", they're flagged as selected, and I've tried clicking them off and on but it doesn't help.  In Preferences=>DataModeler=>Diagram=>Format, I've tried messing with the line widths to see if the change would affect the invisible lines, but no.  When engineered to a relational model, the corresponding foreign key's lines do appear.  If I create a subview from the entities that have relations between them, the lines don't appear on the subview either.  If I change the logical diagram's background color to red, the relations do appear in white (or maybe yellow), though in the narrowest width.  (That is, if I change the line width to fat and blank in Preferences, the 90% of the lines that usually appear are there in fat black, but the usually invisible ones are thin and white/yellow.)
How can I get the missing lines to appear?  (SQLD 3.3.0.747)

I guess all I needed to do was report it here in order to figure it out!
How I fixed them:  Set diagram color to red so that they'd be visible.  Right-click the now-visible line to bring up a submenu.  Under Format, "Use default" was clicked off.  Click it on.
How they managed to become un-default, I don't know, but they're better now.  I'll mark this answered but leave this here in case someone else stumbles into the same problem.

Similar Messages

  • Logical Diagram Notation - Information Engineering Notation

    I'm a little confused about the Logical Diagram Relational Properties diagram. In a parent/child relationship where parent is required and children are optional, the Source to Target Cardinality must be set to * and Target to Source Cardinality to 1. Source Optional pertains to the Source and is unchecked and Target Optional is checked. A bit inconsistent and untuitive to me to have one Source setting describe the source and the other Source setting describe the Target, but fine. Those settings display correctly in Barker and Bachman notation.
    If, however, you switch the notation to Information Engineering Notation, the optional settings are revered and display incorrectly. Checking Source Optional controls the optionality of the Target and visa versa.

    If, however, you switch the notation to Information Engineering Notation, the optional settings are revered and display incorrectly. Checking Source Optional controls the optionality of the Target and visa versa.Optionality is represented at the other end of the line in IE notation.
    Philip

  • Java error on P6 Professional v8.2.2.8 TimeScale Logic Diagram

    I just recently upgraded a test environment to the latest P6 Professional release 8.2.2 (build #:8206). Now the Timescale Logic Diagram get a java error, see below. Of course, the P6 web tool and database have been upgraded to 8.2.2.8. They seems to be working fine. This Timescale diagram use to work, now it is broken. I was wondering what is up?
    In the error is mentioned the ViewProb table not be available. This table does exist in admuser and is full or rows. If the solution is to upgrade to java 1.7, then I am kind of screwed since that is not an option were I work.
    Environments:
         dell latitude laptop
         8 gigs of memory
         java 1.6 plugin and jre installed
         windows 7
         oracle 11g (11.2) database on rhel5 server
    JAVA Stack Trace:
    System.Exception: TemplateService Fail to Get Template Data: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: TCVirtualDBEngine.TableByName: Table not found: VIEWPROP (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
    OraclePrimavera.Core.ECTableNotFoundError: TCVirtualDBEngine.TableByName: Table not found: VIEWPROP
       at OraclePrimavera.Core.TCVirtualDBEngine.@18vdbengin$TableByName$_RaiseException($Unnamed15& $frame_TCVirtualDBEngine.TableByName)
       at OraclePrimavera.Core.TCVirtualDBEngine.TableByName(String TableName)
       at OraclePrimavera.Core.TCVirtualDBEngine.GetObjectList(String anObjectName)
       at Primavera.API.AppInstanceBasedObjectContext.GetBusinessObjects(String objectName)
       at Primavera.API.Services.P6LookBusinessRuleService.GetTemplateIDs()
       at SyncInvokeGetTemplateIDs(Object , Object[] , Object[] )
       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
       at Sy...).
       at Primavera.Look.DataAccess.ServiceBasedTemplateDataProvider.GetAllTemplateData()
       at Primavera.Look.DataAccess.DatabaseTemplateProvider.get_AllTemplates()
       at Primavera.Look.DataAccess.DomainContext.get_Templates()
       at Primavera.Look.DataAccess.DomainContext.get_CurrentTemplate()
       at Primavera.Look.ViewModels.MainViewModel.EnsureSaveTemplate()
       at Primavera.Look.Views.MainWindowView.Window_Closing(Object sender, CancelEventArgs e)
       at System.Windows.Window.WmClose()
       at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

    I fixed this problem by purging Primavera Professional P6 SP1 off laptop computer and re-installing SP2 cleanly. When I mean purge, I mean uninstall using the Window's system admin panel, and remove any remnants from directories used by Primavera. I also cleaning out my temporary files folder and rebooted my computer before installing SP2 to make sure no services were running from SP1.
    Timescale logic diagram seems to be working.
    On other thing that may or may not be related: I also remove all Oracle client installs and re-installed a single clean 32bit Oracle client. I do not think Primavera uses Oracle's client, but I did this before I installed Primavera P6 Professional SP2.

  • 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

  • How to copy field comments from logical model to relational one?

    Dear gurus!
    I had a logical model without field comments. Then I made an engineering of logical model into relational one. Later I added field comments to logical model. How can I copy these values to relational model? Seems to me that when I use
    model.getTableSet().toArray()
    then I get list of relational model tables. How can I get a list of logical "tables" and to get a relations between those two lists?
    Thank you!
    Edited by: user12947051 on 12.01.2012 23:58
    Edited by: user12947051 on 12.01.2012 23:58

    You don't need to write and run script for that. Just use engineering to relational model. Use compare/copy options tab if you don't want something else to go into relational model
    Philip

  • Make line invisible in Smartforms

    Hi all,
    how to make a line invisible in Smartforms?
    I tried to paint the text white. Its not shown in the preview, but when I print the page, the line appears.
    Hope, somebody can help..

    Hi,
        If the line is regarding the Template the u can go to the button Draw line and Colums button u get the 4 directional arrows select the line which u dont want to be displayed go to the button outer frame/ upper frame/ Lower Frame select it so that it will not get displayed in the Print output.
    Regards,
    Vijaya Lakshmi.T

  • SAP Script - Logical expression in multi lines

    Hi Friends,
    How can I write logical expression in more than one lines in SAP script editor?
    Case:
    I have to write:
    IF &J_1BPRNFHD-DIRECT& = '1' AND &J_1BPRNFHD-MANUAL& = 'X' AND &J_1BPRNFHD-SHPUNT& = ' '
    I am writing in first line
    /:  IF &J_1BPRNFHD-DIRECT& = '1' AND &J_1BPRNFHD-MANUAL& = 'X' AND
    and &J_1BPRNFHD-SHPUNT& = ' ' is not coming in the same line. How to write it in more than one line?
    What I mean is that:
    Can I write like:
    /:  IF &J_1BPRNFHD-DIRECT& = '1' AND &J_1BPRNFHD-MANUAL& = 'X' AND
    /:     &J_1BPRNFHD-SHPUNT& = ' '
    In fact, above is not working. Please help.
    Regards,
    Surya
    but the rest of the things, that is, &J_1BPRNFHD-SHPUNT& = ' '

    I'm not an SAP script expert but this is just a suggestion.
    Write 2 seperate conditions.
    You can replace this:
    IF &J_1BPRNFHD-DIRECT& = '1' AND &J_1BPRNFHD-MANUAL& = 'X' AND &J_1BPRNFHD-SHPUNT& = ' '.
    ENDIF.
    by this:
    IF &J_1BPRNFHD-DIRECT& = '1' AND &J_1BPRNFHD-MANUAL& = 'X'.
    IF &J_1BPRNFHD-SHPUNT& = ' '.
    ENDIF.
    ENDIF.

  • Automatic Plant determination logic in the order line item level

    Dear all,
    I would like to know if there is a possibility to determine plants automatically, avoiding the standard plant
    determination logic at line item level, to determine plant based on stock availability.
    The process will be to skip the standard plant dtermination logic and drive the process through
    based on ATP on plant level.
    Coming more specific to the requirement the system determines the plant where the stock is available and if the stocks are not
    sufficient the system goes to the next plant automaticaly and confirms the stock quantities, which also could mean that the ATP would run on plant 1 and then plant 2 and plant 3......depending on the availability of stocks with partial confirmations or full.
    If there are existing user exits etc. available also when the configuration not available would welcome it.
    Thanks

    Hello
    On more option I can see is of maintaining preferred plant in Table OIDAP.
    Generally, this table is used for IS-Oil plant determination.
    There you can set up one preferred plant and up to four alternative plants for a combination of
    - sales area
    -country
    -transport zone (of the ship-to party)
    -material number or material group.
    The plant selected depends on the availability of material in the plant/storage location.
    Regards
    JP

  • Problem exporting notation from score to PDF in Logic 8. Top line of staff displaced a 1/6th note when exported.

    When I export drum notation from the score to pdf, it shifts the top line of the staff over by a 16th note. It looks the way I want in the program, but only does this when exported. I'm using Logic 8. Anyone know how to fix this? See the pictures attached below...
    Here's a screen shot of the notation in Logic:
    Here's what it looks like when exported to PDF:
    Any help would be appreciated. Thanks!

    I've tried both ways and had the same results. I discovered today though that if I zoom in all the way in the score the notation actually shifts over in Logic. I'm not sure why it does that, but now I know that it has nothing to do with exporting or how I export it. The notes should line up for this particular groove and I've tried with other beats and had the same results. Not sure if there's a setting somewhere that displaces certain lines of the staff or something of that nature. I can drag the notes over with the layout tool, but it'd be nice to have a preset to have it go where I want it and save myself time. Thanks for responding and if you have any other ideas let me know.

  • How can I make the pen lines invisible?

    I have made lots of edits with the pen tool, and I am noticing that the lines from the pen are a different color than what the shape is I made. Is there a way to make these lines from the pen invisible?
    Thanks so much for any help!

    Hello Les and Salah,
    I appreciate your reply. Unfortunately, all the objects with pen lines have a stroke of 0 pt already... I have a picture to show you what I am working on... The very thin blue lines are my issue. Thank you so much.

  • Logical M:N Relation with Delete Rule:"NO ACTION" creates "CASCADE" FK

    I think I've detected a bug in the generation of FK when we have"N: N" relations, give me idea that the delete rule that is defined in the relationship of logical model is ignored.
    So I give you a small example to reproduce it:
    I've a simple example of 2 entities:
    Logical Model:
    Entity_A(#id_a, desc)
    Entity_B(#id_b, desc)
    M:N Relation between Entity_A and Entity_B (REL_A_B) with Delete Rule: "NO ACTION".
    When apply "Engineer to Relational Model" I've as result 3 tables:
    Relational Model:
    Entity_A(#id_a, desc)
    Entity_B(#id_b, desc)
    REL_A_B(#id_a, #id_b) but the generated foreign keys are defined using Delete rule "CASCADE".
    Is not supposed to have been generated with delete rule "NOT ACTION"?
    As result the generation of DDL scripts is creating FKs with the clause " ON DELETE CASCADE", which was not originally intended.
    I try to change this value in logical model but I've seen not effect on result.
    I hope I have helped!

    Hi Ariel,
    thanks for reporting the problem. I assume it's for Data Modeler 3.3.
    I logged a bug for that.
    Philip

  • Delete Rules between Logical Model and Relational Model are different

    Relation Properties in Logical model has three Delete Rules: "RESTRICT", "NO_ACTION", "SET NULL".
    1. "RESTRICT" and "NO_ACTION" are same
    2. "CASCADE" is missing.
    However, Foreign Key Properties in Physical model has three Delete Rules: "RESTRICT", "NO_ACTION", "CASCADE".
    1. "RESTRICT" and "NO_ACTION" are same
    2. "SET NULL" is missing in this case.
    They are supposed to have "NO_ACTION or RESTRICT", "SET NULL", and "CASCADE".
    Please fix this ASAP. It is really annoying in Engineering process. Modeler creates duplicate wrong relationships while it engineers.
    Thanks.
    Edited by: hayangae on Oct 9, 2012 1:01 PM
    Edited by: hayangae on Apr 3, 2013 4:08 PM

    Hi,
    it seems you are not using the latest version 3.3. In earlier versions - delete rule set on relationship was used only in some cases to set delete rule on related foreign key. Now delete rule is transferred to FK as it's defined on relationship.
    I assume you are using Oracle database - "Restrict" doesn't appear anymore for Oracle.
    2. "SET NULL" is missing in this case.Most likely the foreign key is set as mandatory thus you cannot use "set null" as option.
    Modeler creates duplicate wrong relationships while it engineers.Can you elaborate on that - example?
    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

  • DataModeler: Cannot engineer from logical model to relational model

    Hello,
    I have been trying for a couple of (very frustrating) hours to engineer a very simple logical model to its relational model. The toolbar button (and also menu option) that should do this just does nothing. No errors, no feedback, absolutely nothing!!! However I could engineer a relational model back to its logical model.
    I am using SQL Modeler version 1.5.1 build 525 on Windows Vista. I have closed and restarted the program many times but to no avail. Are there other factors (e.g. anti-virus, JDK etc) that could be responsible? But then why are other parts of the software working but not this one?
    Please kindly send your advice asap so I can proceed. I really like the Modeler and will not want to discard it.
    Thanks,
    Chiedu

    Hi Folks,
    I was able to figure out the likely cause of the problem. The version of Modeler (datamodeling-1.5.1-525-no-jre.zip) I used was downloaded without JRE. The current version of JRE installed on my computer is Java 6 Update 12 (build 1.6.0_12-b04). I suppose the two don't quite work very well together.
    I have now downloaded and installed another version (datamodeling-1.5.1-525.zip) with its own JRE and the problem was resolved.
    My guess is that the problem was due to the incompatibilities that may exist between Data Modeler and the various versions of JRE.
    Thanks.

  • Strange mapping of Boolean from Logical to DB2 Relational model

    Hi guys,
    Using most recent version of Data Modeler (3.3.0.747) I notice strange behavior:
    Attribute, declared as Boolean in Logical model is engineered to a column, with type CHAR(1) in Relational Model, when "RDBMS Type" is Oracle, but when "RDBMS Type" is "DB2", column type is CHAR(254)
    Is this a bug or a feature?
    Is there any way, where I can control type mapping between logical and relational model?
    Well, I can just go and change CHAR(254) to CHAR(1) all over my Relational Model, but this is pretty frustrating.
    MfG,
    Stoyan Tsonev

    Hi Stoyan,
    Is there any way, where I can control type mapping between logical and relational model?In fact mapping is between logical data type and database native types - Tools>Types Administration.
    You need to change mapping for Boolean logical data type - check "size" check box and put value in text field to define default size. Default size will be used when there is no explicitly defined size in column/domain definition.
    Philip

Maybe you are looking for