Quantcast
Channel: SCN : All Content - SAP PowerDesigner
Viewing all 638 articles
Browse latest View live

ODBC error checking in a data model

$
0
0

At my client we're using PD 16.5.0 build 3982, and we're trying to check in a LDM that was originally generated from a PDM. When we try and check the LDM in to the repository, we get an ODBC error:

ODBC driver for Oracle

ORA-12899: value too large for column "PMTEXT"."TDAT" (actual: 2002, maximum: 2000)

SQLSTATE = NA000

 

I have an old (PD 16.1) PDM for the repository, which shows the column as having a length of 30,000, not 2,000. On my own laptop, the 16.5.3 (Sybase SQL Anywhere) repository also shows the column as varchar(30,000). However, the client's 16.5.0 Oracle database shows the column as varchar2(2000).

 

Has anyone else had this problem with an Oracle repository?


Adding a TraceabilityLinks between Requirement and LDM Attributes ?

$
0
0

hi,

 

i search about how to create a  Tracability Link in vbs to a Requirement but i did not found any usefull information about how i could do it.

i know  that Requriments have the Property   TraceabilityLinks As ObjectCol

but i don´t know how to define the Target Design Object ?

 

i know sometime there is a createnew function but how could i assign the Target Object of the Link ?

 

thanks /br

How to disable Requirement Title uniqueness ?

$
0
0

hallo ,

 

i tried to find a point where in Requirement Model ( Model Options ..." etc.) i could disable the uniqueness check for Title.

(Code is unique) but if i add with vbs a new Requirement with same Title i get an error.

 

The Base Problem is that the Business Analysts will switch the Requirements to a new Requirement ( with same "Title" ) but a new Code

and set a Extended Prop. "State"  to  Active or Inactive.

The impl. of new Ext. Prop is easy but i raise the "Feature" of uniqness Titles

I think in other Models the Code / Name could be different ?

 

thanks

/br

Children and parent in different CDM packages?

$
0
0

Hi,

 

I wonder if there is a way to use inheritance and packages, in a conceptual data model (CDM), so that the parent and the children are not in the same packages?

 

I have first created entity A, B and C in a Package P1.  Then, I have set an inheritance, having A as parent, and B and C as children.  Then I have created a Package P2 and I have moved the entity B into it.

 

That way, if I open the entity B, I can still see A as its parent.  However, in the P1 diagram, I cannot see B the inheritance anymore.  And this, not graphically and not also in the child list when I open the inheritance.  Also, if I try to add a new child in the inheritance, I can only choose among the entities included in P1.

 

In the P2 diagram, I can create a shortcut for the A parent entity but I cannot create an inheritance between that shortcut and B.  Same thing if I create a shortcut of the existing inheritance in the P2 diagram.  It will show with its link with the A entity but will not allow to add a link with B.

 

In conclusion, it is like I have kept half of the inheritance definition but lost the other half.  Is there a way to keep everything?  Is that a bug?

 

Thanks

Daniel

Synchronization issue | Extended Metamodel Signature

$
0
0

Hello,

 

we want to use the repository functionality. A colleague and I use the same repository folder to "check in" /"check out" our content. Unfortunately I cannot "check in" my content anymore after I synchronized my repository. After I click on 'OK' on the  screen below -the screen freezes.

 

repository_sync_problem.png

 

Do you know a solution for this problem?

Is this because of the different metamodel signature?

Data Mapping Model extensions to support LDM/CDMs as Source/Target ?

$
0
0

In DMM there are only 3 Source/Target Types (Database/XML/Process)  and in Database it´s only possible to assign "physical Database Models"

 

How could i assign a LDM or CDM as a Source or Target ?

 

Currently i "know" it´s not possible but the Question is could thhis behaviour changed with xem Definitions or with

Ressource=> Extentions => DMM ?

 

thanks

/br

Standard Domain Set

$
0
0

I'm starting a project I call "Things of the Enterprise" (TOTE) or just Enterprise, that is intended to develop a reference set of common items and relationships.  A good example of a common item is a "Person".  For the most part the Person Entity contains the same fields in every application within an enterprise.  This can be extended to say that for the most part the Person Entity is much the same across applications worldwide.  Even though a Person entity structure is fairly constant in most cases, all to often every project designs the person from scratch.  This eats up much time unnecessarily.

 

The Enterprise project is intended to create a standard set of commonly used items like, person and organization, and share them with anyone that can use them through public methods (like GitHub).

 

A project like Enterprise requires tools, not text, to be successful.  PowerDesigner is the perfect tool for this project.  With the ability to work across technology domains, like Object<->Data, and multiple targets (Oracle, SQL Server, Java, C#...) PowerDesigner makes it fairly easy to develop entities not only conceptually, but also as concrete items.  It also gives us implicit OR mapping.  If we generate a PDM from an OOM by default all of our strings become varchar(254).  If we use domains and have the same domain in both our PDM and OOM environments our generation is much better controlled and more consistent.

 

A core requirement for this type of effort is standards that are flexible enough to be both conceptual and abstract, cross technology domain, and internationalized.  PowerDesigner gives us the construct we need - the Domain.  The Domain is generic enough on the surface to fit almost anywhere, but flexible to contain detailed implementation details.  There is a base set of Domains that are used in almost all business applications.  Things like phone numbers, mail locations, and people are examples.  If we define a domain called Phone or sub classed domains like Phone.US, Phone.International, we can then use that title in many way.  We can use it as an abstraction - just the idea of a Telephony Location.  Or make it very concrete for different locations across the world, different technology domains (Object, Data), or different target platforms (Oracle, SQL Server).    The great thing is that we only need to say "Phone" in our PowerDesigner typing, with the domain implementation taking care of the rest for us.

 

PowerDesigner give us great flexibility in making these abstracts concrete.  And "protect" us from over or unnecessary analysis.  Have you ever seen long discussion about whether a field for a simple list should be 12 or 14 chars long?  It rarely matters from a technology perspective or business perspective.  Storage allocations in databases generally fall on byte/word boundary lengths - 12 and 14 use the same space.  And from a business perspective the sizes don't often matter either.  How often have you seem a true business rule that says list items can't be more than 12 char long?  We can create a generic domain for this "Type Of" idea.  I use "Pick" for this, and a length of varchar(20).  (I picked this because on a web form that fits about right in a dropdown).   When I see an element in the "Pick" domain I know that I am describing a small string that (most likely) represents a list of values, and possibly an enumeration.  Much richer and more clear then just seeing varchar(14).

 

With these basic Domain constructs we can then build more complex objects.  Things like Person, Organization, and Location.  But things don't stop there.  Not only do we have standard fields (backed by domains), and standard entities (composed of standard fields/domains), but we can also define standard relationships.  In most cases our Person has some type of relationship with at least one Location.  We can establish that relationship in our models.  Eventually we can build a comprehensive model of the universe.  OK, just a small piece of the universe, but you get the picture.  The standard model is a base that can be extended with business specific entities or tailored down.  In my case I deal with Providers.  I have extended my Organization entity to include the specifics of a Provider with little effort.  Now our systems development teams can just pull from common entities and relationships when designing systems, saving significant amounts of time, providing consistency, and even assisting with systems interoperability.  Have you ever seen Zip implemented as chars in one system, varchars in another, and as int (hey, it looks like a number doesn't it?) in another with the same organization.  Have you every tried to get the systems to talk? Conversion = time + complexity + point-of-failure.  With a standard model the Zip issue doesn't (shouldn't) occur.  Our designer would normally just grab the Location entity and use that, tailoring as appropriate.  If Zip was needed by itself, no problem, Zip is a domain that can be used as-is.

 

I think you can see the advantages of a standard model.  As PowerDesigner users we know that PowerDesigner makes doing something like this possible.  If you would like to join in this project please let me know.  Even if you would just like to use the model let me know and I'll let you know as things get published.  The GitHub site is https://github.com/Tessalator/Enterprise. There is nothing there yet and I hope to have the first pieces out there soon.  In the meantime, I've attached a sample of some of my base domains, spec'ed for SQL Server.

 

BTW - I hope this is readable.  I'm not much of a writer (or proof reader, or speller, and you should see my hand writing...), but I a pretty good modeler.  I just whipped this out at lunch while I was motivated.

how do I import indicies with excelimport.xem???

$
0
0

Hi all,

i have the following exceltable:

 

IndexnumberIndexnameFieldAufsteigend
1TBAW0666TESTTAB.IXAW066601TESTTABPKX
2TBAW0666TESTTAB.IXAW066602TESTTABTBAW0666TESTTAB.PKX
2TBAW0666TESTTAB.IXAW066602TESTTABTBAW0666TESTTAB.FELD2X
2TBAW0666TESTTAB.IXAW066602TESTTABTBAW0666TESTTAB.FELD3X
2TBAW0666TESTTAB.IXAW066602TESTTABTBAW0666TESTTAB.GUELTIG_AB
3TBAW0666TESTTAB.IXAW066603TESTTABFELD1X
3TBAW0666TESTTAB.IXAW066603TESTTABGUELTIG_ABX

 

 

And the following importdefinition:

Table Indexdefinitionen=Table.Index.IndexColumn: Indexnumber=Comment, Indexname=<Parent>, Field=Column, Aufsteigend=Ascending

 

 

 

The 3 indexes are created, but not the indexcolumns, i tried both versions of fieldnames with tablename and without, i also switched on and of the option "create object if not exists", but no results, do i try to bind the field to the wrong object/collection within Table.IndexColumn?

 

Thanks for any advice


PowerDesinger 16.5 Checkin Model in C#

$
0
0

Hi team,

 

I have a C# project on PowerDesigner 16.1 and now I want migrate the PowerDesigner from 16.1 to 16.5.

The checkin method change from one version to other.

 

In 16.1

CheckIn(ByVal MergeMode As Integer = 2, ByRef Actions As String = Nothing, ByRef Conflicts As String = Nothing) As BaseObject

 

In 16.5

CheckIn(ByVal MergeMode As Integer = 2, ByRef Actions As String = Nothing, ByRef Conflicts As String = Nothing, ByVal ChangeListCode As String = "", ByRef ChangeList As BaseObject = Nothing) As BaseObject

 

If I try in VBScript I dont have any problem, but with C# this function never work.

As you can see this function have two more arguments:

 

ByVal ChangeListCode As String = "", ByRef ChangeList As BaseObject = Nothing

 

Declare variables

 

String changeListCode = ""

PdCommon.BaseObject chlist = (PdCommon.BaseObject)rc_prd.CreateChangeList();


output = model.CheckIn(1, out actions, out conflicts, changeListCode, out chlist)


The output is always null, but with 16.1 it's working.


Any ideia? What are we doing wrong?

I already try with CheckinDocument but this method only work if I don't have any previous version in repository.


Best Regards

Fault? PD 16.5 / Repository / Project / LDM>PDM Generation

$
0
0


Has anybody else run into this issue or have a resolution?

 

Scenario:

  1. Create a project.
  2. Create a LDM within the project
  3. Check the project in to the repository
  4. Generation a PDM from the LDM.
  5. Ensure PDM resides in project
  6. Check project in to repository, including new PDM
  7. Update PDM
  8. Update LDM
  9. Regenerate PDM from LDM: Merge into existing PDM

 

Everything is fine after step (6), and a check-out to a different client machine works fine.  However, after step (9), the PDM loses its link to the repository, and it is no longer possible to check it in.  Execution check-in from the PDM context menu generates a project check-in including the LDM changes, but the PDM is greyed out.  The check-in will succeed at project level, but the PDM changes will not be passed back to the repository.

 

PD version: 16.5.2.4120

OS: Win 7 Enterprise x64

 

There are issues with this configuration as currently installed, as installation directories reference Program Files rather than Program Files (x86), but this seems unrelated to the check-in problem.

PDM Check IN Error

$
0
0

Hello,

 

the following error prevents the check in of a PDM into the repository:

 

Unexpected error while executing the following action:

Changing value of attribute Modification Date of object Target model reference

The check in of the document has been cancelled.

 

I'm not sure what that means at all? What excatly is meant by "object Target model reference"?

 

For the time being I'm the only user using check in for that model, means, the model didn't change in the repository since I checked it out. There are only few changes to the local model, some datatype changes, attribute deletes etc. The model is rather small (about 30 tables).

 

This happens again and again. I resolve the situation fiddling around with the model (copy, check aout again, override, ...) but have no repeatable approach to fix it.

 

Thanks for any hints,

 

Chris Werner

 

p.s.: Using PD 16.5.0.3982

Reverse Engieering Problem in PD 16.5 SP03 PL01

$
0
0

I am trying to reverse engieer a table from Teradata(Live DB) and convert it into a PDM.

 

I am having trouble converting unicode columns. For example, if in a table one column is defined as VARCHAR(200) UNICODE; when I reverse engineer this column in my PDM becomes VARCHAR(400). It doubles up all the unicode columns in length. If the column is defined as LATIN, no problem at all.

 

If I try to reverse engieer through a script, it gives me a correct column length for UNICODE and LATIN.

 

So, I was wondering is there any option in PowerDesigner to make it right while reverse engieering from a live DB? or am I simply doing something wrong?

 

Thanks.

How to set default options in PD 16.5 SP03 PL01

$
0
0

Everyone,

 

I want to set some default physical options while reverse engineering the table(s).

 

I want following options to be added everytime I reverse engieer the table.

 

CREATE MULTISET TABLE,

NO FALLBACK ,

NO BEFORE JOURNAL,

NO AFTER JOURNAL,

CHECKSUM = DEFAULT,

DEFAULT MERGEBLOCKRATIO

 

This is what we are going to use most of the time, so I dont want to create a table and then goto physical options and choose them. I want this by default. However in rare cases we might be using some other options as well like CREATE SET TABLE, so I should be able to change it whenever I want but default properties should be listed above.

 

Is there a way I can do this?

 

Thanks,

Perry

No notations available in model options

$
0
0

Hi guys.

 

I have a problem with changing the notation because there are no notations available. I have checked an older version there it ispossible. Do you know how this happens?


Thank you!!



Old version:

Old_Version.png


new version:

New_Version.png


Best,

Ahmet

 

New ebf errors!!

$
0
0


Adsız.jpg

Adsız.jpg
I am getting these errors since I updated my PD from "sp2 pl04" to "sp3 pl01". I am using 32-bit version. Does anyone know why I get these errors?
Does anyone


objects generated out of order

$
0
0

I have noticed that the DDL generated will often have objects generated out of order, such as some (but not all) tables and views being generated before the drop database command.

 

Is there something I am missing in the setup or options for generation that would make objects be generated in the logical order, i.e. tablespaces before tables, no ojects in the database before dropping the database, etc..

 

I am running 16.1.0.3917 EBF 18.

DB is DB2 z/OS V10

customer stories

$
0
0

Hallo team,any successful customer stories on power designer.if any please share

Can't export files from VBA without user-intervention, any ideas?

$
0
0

Hi,

 

I am trying to automatically export files for a workspace. Because of memory usage I want to go through the models in the workspace, open them, expot and close them using VB Script.

 

This works however, when you open a model from code and call GenerateFiles for the first time, the extended generation window is shown. I am doing this on a Physical Model.

 

Does anyone have an idea how to prevent this from happening and just export all of it without user-intervention?

 

Code:

dim l_exports : set l_exports = createobject("System.Collections.ArrayList")
dim l_path    :     l_path    = "c:\temp\BIFMEX\ET6\"
dim l_ok      :     l_ok      = true

' Codes of the extensions that contains files I want to export:
l_exports.add "BIFBA"
'l_exports.add "BIFCG_OCG2"
'l_exports.add "BIFME_OME"
'l_exports.add "BIFGBV_TRFM"

' Export model sub, does the actual export
sub exportModel(byval p_mdl,byval p_exports, byval p_path)
   ' Set the model as the activemodel by showing the diagram   p_mdl.DefaultDiagram.OpenView     ' Go through the extensions in the model to see if they match   ' the list of extensions to export    for each emd in p_mdl.extendedmodeldefinitions      if p_exports.contains(emd.code) then         ' Get the package options for the model and configure that         set l_po = p_mdl.getPackageOptions()         l_po.GenerationTargetsBLOB = ""         l_po.GenerationPathName = p_path         l_po.GenerationCheckModel = false         l_po.GenerationBeforeCheckModel = false         l_po.save()                  ' Call the generatefiles function for the target extension,         ' this is where the problem occurs         l_ok = p_mdl.GenerateFiles(p_path,nothing,emd.code)         if l_ok then            output "Target: " & emd.code & " exported for model: " & p_mdl         else            output "Target: " & emd.code & " NOT exported for model: " & p_mdl         end if      end if   next
end sub


' ---> What the workspace looks like:
' Workspace
'  + Base Model 1
'  + Base Model 2
'  - Folder for Subject 1
'    + Subject 1 Model 1
'    + Subject 1 Model 2
'  + Folder for Subject 2

' First open toplevel models and export those (named Base Model 1 and 2):
for each child in activeworkspace.children
   if child.isKindOf(PdWSP.cls_WorkspaceModel) then      set mdl = child.open      if not mdl is nothing then         exportModel mdl, l_exports, l_path      end if   end if
next

' The go through the folders and perform an export per folder:
dim l_models : set l_models = CreateObject("System.Collections.ArrayList")
for each child in activeworkspace.children
   if child.isKindOf(PdWSP.cls_WorkspaceFolder) then      l_models.clear      ' First open all models in the folder, because of       ' cross model dependencies:      for each fldrChild in child.children         if fldrChild.isKindOf(PdWSP.cls_WorkspaceModel) then            l_models.add fldrChild.open            end if      next            ' Export the relevant models:      for each mdl in l_models         exportModel mdl, l_exports, l_path      next      l_models.clear            ' Close all models in the folder, to preserve memory      for each fldrChild in child.children         if fldrChild.isKindOf(PdWSP.cls_WorkspaceModel) then            fldrChild.modelobject.close false         end if      next      exit for   end if
next

Regards,

Marcel Schot

It's that time of the year again - please suggest topics for the PowerDesigner SIG at EDW

$
0
0

I'm moderating the PowerDesigner SIG at EDW in Austin next week. As usual, we already have a number of topics we think people will want to discuss, but we want the bulk of the content to come from you, so please let me know what you want to talk about, either via the Linked In Group, SCN, or by emailing me - George.McGeachie@MetadataMatters.com.

PowerDesigner 16.1 different EBF

$
0
0

Hi All,

 

I have a Powerdesigner 16.1 with 11 EBF, and my Powerdesigner Proxy have the 18 EBF.

 

I can work with different EBF on PD and PD proxy?

 

Thanks.

Viewing all 638 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>