Work smarter with #PowerDesigner – How to display ‘missing’ toolbars

Like many other modelling tools, PowerDesigner provides tools to help you control the layout of the symbols on your diagrams. For example, I would probably want to align these three sub-type entities in my diagram using the top edge:

misaligned entities

By the way, these are not standard entity symbols, I’ve customised the display to show the name of the super-type entity, and the Generate property. I’ll probably show you how to display these properties in another blog post.

The alignment commands are available from the Symbol menu. All I need to do is select the three symbols, then click on the Align Top tool on the menu:

Symbol menu

I prefer to use the toolbar to do things like this, probably because it needs fewer clicks. Unfortunately, the required toolbar (the ‘Layout’ toolbar) isn’t always visible, it’s often hidden. Exactly how well hidden it is depends on your version of PowerDesigner. I’ll start with the current situation, which probably applies to most PowerDesigner users.

the Layout Toolbar

Here are the toolbars you’re most likely to see when you start PowerDesigner (they’re usually in a long strip – I’ve moved them around for this image).

standard toolbars

The layout toolbar is not visible, here’s how to change that:

  • right-click on a blank area to the right of the visible toolbars
  • choose a toolbar to show or hide

choose toolbar

That’s it, nice and simple.

Some of you will be saying to yourselves, “Hang on, the toolbar I’m looking for isn’t listed!”. That’ll be because you’re using an older version of PowerDesigner than the one I’m using today. In PowerDesigner 16.1, Sybase decided to make several toolbars optional. By default, the Layout, Check, Format, Window and Repository toolbars were not visible; they did not appear in the list of available toolbars. You needed to use one of the customisation features of PowerDesigner to enable the missing toolbars.

On the Tools menu, select Customize Menus and Tools, select the Toolbars tab, click on the word Toolbars, then click on Add Command and select the toolbar you want to use. Repeat this action for each toolbar you want to enable.

Advertisements

#PowerDesigner Tips and tricks – showing both the Name and the Code on a symbol

I answer a lot of questions on the SAP Community Network; a couple of years ago, a user wanted to know how to display the object codes on her diagrams instead of the object names. In PowerDesigner every object has both a Code and a Name – the Name is what it’s known as inside PowerDesigner, and the Code is what it’s known as outside PowerDesigner. In a Physical Data Model, for example, the Name of a table might be “Customer Account”, and the Code might be “CUST_ACCT” – in this case the table name is also the name of the Logical Data Model entity that the table was generated from. PowerDesigner has derived the Code from the model’s naming standards.

By default, PowerDesigner diagrams (and the Browser window) always show the object names; for a Physical Data Model (PDM), this could include:

  • Tables and Columns
  • Indexes
  • Views and View Columns
  • Dimensions
  • Facts

etc.

For example, here’s a sample PDM diagram showing the object Names, and the corresponding list of objects in the Browser:

The advantage of this view from my perspective, is that the names on show are descriptive, unencumbered by any restrictions imposed by the DBMS or local naming standards – I know what every column name means. The name of the bottom reference in the diagram was copied across from the LDM, the two called “Inheritance_1” were generated from an inheritance (super/sub-type) hierarchy.

The disadvantage of this view is that it doesn’t show the names used for the objects in the database. Those names are actally there, in the object definitions, in the Code property:

Column Name and Code

I’m sure that the vast majority of people who work with Physical Data Models would prefer to show the object codes on the Diagram, like this:

PDM - showing Codes

It’s really easy to change the view from Names to Codes; exactly how you do it depends on your version of PowerDesigner. The original method is by selecting ‘Code’ in the Naming Conventions in Model Options:

Showing codes - model options

The setting applies to every diagram in the model, and also affects the Browser content.

PDM - showing Codes - browser

In PowerDesigner 16.6, the setting was moved to the Display Preferences for the Diagram, though it still affects the whole model, including the Browser. Also, a new tool was introduced on the Standard toolbar  – Showing codes - toolbar – now you can toggle between displaying names or codes with a single click.

If you want to show both Names and Codes on diagrams, you can do this for individual diagrams via Display Preferences. The ability to customise the content of symbols is one of the features that helps PowerDesigner to stand out in comparison to ERwin Data Modeller and ER/Studio Data Architect. For example, here’s a table symbol that focuses on the table and column codes, but also shows the names for those objects:

Table with Name and Code

The Code is not available for display by default, so you’ll have to use the Advanced features to make it available. Right-click the diagram background, select Display Preferences, and select ‘Table’ on the left.

Display Prefs - default for Tables

Here’s where you choose what to display on Tables, based on the properties that SAP have made available. You’ll see that you can choose ‘Name’ or ‘Owner and Name’, but not ‘Code’. All is not lost, however, as we can make other properties available to display – just click on the Advanced button at the bottom right.

Now you can select what you want the user to be able to display on table symbols. You can move things around, add and remove things, and change the way they’re organised. Here’s the default view:

customise content

In this case, you want to make the Code visible. To do this, click on the ‘Add Attribute’ button, select ‘Code’ from the list of Attributes, and press <OK>. You will see more attributes than my clip shows, I’ve cropped the image.

my customisation - 3

Here’s my customised view, in which I’ve removed and added content, and amended the layout – notice the prefix and suffix for the Name:

my customisation - 1

I’ve changed the displayed content (a.k.a. ‘List columns’) for the Columns in each Table, making sure that it shows the code and then the name of each column:

my customisation - 2

I won’t show all the steps needed to reproduce my table symbol, due to lack of space; besides, I have to let you work out something for yourself, I can’t take away all the challenge for you.
You can apply these settings to other diagrams as well, just click on the ‘Apply To’ button in Display Preferences. Beware, this will apply all the current Display Preferences to the selected diagrams.

One last point – you can change the content of individual symbols – just right-click the symbol, slect ‘Format’, then click on the ‘Content’ tab:symbol format

In this version of my diagram, every table symbol has different content:

customised diagram

#PowerDesigner Tips and tricks – a brain dump from years of experience starts today

Over the years that I’ve been using PowerDesigner, I’ve stashed away a large number of useful nuggets of information, most of which I wish could have been downloaded into my brain when I worked on that first Conceptual Data Model (this was before Sybase added the Logical Data Model to the tool). Anybody who knows me well will not be surpised at all when I say that I’m using a PowerDesigner  Requirements Model to document my tips. Here’s a snippet:

RQM - snippet of Tips

Watch this space for a steady trickle of tips and tricks for PowerDesigner users.

I might sneak in a few for ERwin or ER/Studio as well.

#DataLineage – interested in integrating #PowerDesigner with #Solidatus?

PowerDesigner provides comprehensive support for data lineage via the mapping editor and the Data Modement model, but I’m sure SAP will agree that it isn’t the most intuitive data lineage solution on the market. There are several companies I know of that provide comprehensive visualisation and interrogating of data lineage, with the ability to link the metadata they extract from your applications and databases with metadata held in modelling tools.

Solidatus is one such company, here in the UK. They describe their offering as “an intuitive, simple to use web based application that gives you the ability to rapidly map and visualise your organisation’s data landscape — otherwise referred to as data lineage.”

Does your organisation use PowerDesigner for modelling, with or without data lineage? Are you also a customer of Solidatus, or perhaps you’re evaluating the tool? I’m looking for a forward-thinking organisation to work with, to build an integration between PowerDesigner and Solidatus. If you’re interested, please drop me a line using the Contact page (see the Top menu bar).

Thanks

%d bloggers like this: