Thanks for your help !
I appreciate your speedy help, and has managed to get it to work. However, it still wasn't quite clear how to do these things, I'll try to explain below, also for others to see.
I modified the DDL template to create a trace dependency back to the original class (shouldn't this really be a part of the default templates ?).
I started with the example code in my last posting, but it had to look like the code below (I've added line numbers for reference):
1: Dependency
2: {
3: %TRANSFORM_REFERENCE("Dependency trace",classGUID)%
stereotype="trace"
4: Source
5: {
6: %TRANSFORM_REFERENCE("Table",classGUID,"DDL")%
7: }
8: Target
9: {
10: GUID=%qt%%classGUID%%qt%
11: }
12: }
When working with this I also enabled the debug output from the Model Transformation->Transform Current Package dialog.
The change I had to do was in line 6, where I had to add the namespace of the target (generated) tables. This is for me not clear from the documentation. I agree it's there, but it's so difficult to extract that meaning.
And in addition, I had to call this template (named Connector__TransformedFrom, which was made from pressing the Add New Custom Template button) from the class template, by adding a line
%Connector__TransformedFrom%
No example says this directly. Also note a very ugly little thing: The name has TWO underscores in it, and the name is automatically generated from the selections in the Add custom template dialog, and further you can't copy and paste the resulting name ! This also kept me stopped for some time.
I used the debug output to see what was generated, and noticed nothing there until the two underscores were correct.
Also noticed that if you call a template which doesn't exist, no error messages are generated. This could be helpful in the debug output.
Also, the XRefs which was created, they don't seem to be visible anywhere in the EA. I thought they would be visible from "See also" Cross Reference box, but nothing there.
About the documentation, it seems that the information is there, but it is hard to work from. It seems like it is mostly a reference, with some small fragments of examples included.
If you clearly seperated it into a reference and a tutorial guide, with the tutorial guide much more factual, it would be much more useful.
Further, the documentation is often very terse, and it takes too much time to dig down to each detail. The different terms used are also terse, and often poorly explained, making it quite hard to grasp what you mean.
I really needed your help to get the understanding, but is still doubtful how fast I can be up to speed creating the transformations I need.
I'll surely have to come back to you for more
