Lack of foreign keys after LER to PER conversion.

Hi
I 've realized that there are no foreign keys in case a 1:1 relationship after LER to PER conversion. When I click on this relationship (PER) I get an error (details in atached file).
Is this an TDM bug ?

regards
Czarek

Error.txt (3.04 KB)

Hello Czarek,

Thanks for your bug notification. We will fix it for the next TDM version. CR # 71 699.

Workaround: Run the Repair Model function in the converted model. How to do it:

  1. Enable Expert Mode: Settings | Options | General | select the Expert Mode checkbox.
  2. Activate the converted model where there is the error.
  3. Right-click the model name in Model Explorer and select Repair Model.

The model will be corrected.

If you have any questions, please write me back. Thanks.

Regards,

Vladka + TDM Team

Hi Czarek again,

Could you please confirm you have the same settings of the relationship in your LER model as we have - see the attachment?
If no, please send us your settings.

Thanks.

Regards,

Vladka + Dave
Relation1-1.png

Hello Vladka

Thanks for your response.
In some cases I’ve the same 1:1 relationship properties that you have attached. I have also some 1:1 not mandatory relationships in my LER. But I’ve noticed, that it doesn’t matter if they are mandatory or not, results are the same - there is no foreign keys in PER and the TDM error appears.

regards
Czarek

Hello Czarek,

Thanks for your confirmation.

The problem with the keys is fixed for the next TDM version.

Thanks very much for your co-operation!

Regards,

Vladka + TDM Team

Message was edited by: dkretek

Hi there!

I have the same problem but with ALL the keys! Mandatory or not mandatory, one to one or one to many.

I did not find any option telling to generate or NOT to generate the foreign keys between Logical and Physical model!
Is there any one?

Tanls
Piero

Hi Piero,

I did not find any option telling to generate or NOT to generate the foreign keys between Logical and Physical model!
Is there any one?

In LER models keys do not migrate, however in PER models they do. So, when you convert your LER model to PER, the FKs are added automatically. This is a correct behavior. There is no option to turn this functionality off.
I do recommend you to read the following article about differences between LER and PER models in TDM:
http://modeling.inside.quest.com/entry.jspa?externalID=3622&categoryID=159

If you have any questions, please write me back. Thanks.

Regards,
Vladka

Hi there Vladka!

Yoi said:

"In LER models keys do not migrate, however in PER models they do. So, when you convert your LER model to PER, the FKs are added automatically. This is a correct behavior. There is no option to turn this functionality off."

Yes, I WANT THEM! But They have NOT been added!

Regards
Piero

Hi Piero,

What a mystery! Let’s solve it.
Please send us your LER model to modeling@quest.com. We will check it out.
Thanks!

What TDM version do you have?
To which database do you convert your LER model?
Do you use Sync&Convert Wizard or Simple Model Conversion? Both?

Quick movie on conversion:
http://modeling.inside.quest.com/entry.jspa?externalID=2064&categoryID=158
(LER to PER conversion, Simple Convertor - see the second part.)

I look forward to your reply.

Regards,

Vladka