Weird DA issue, running on 17.1 version.
Two entities in the model entity "A" and entity "B". Trying to create an associative entity between them. I create "Association 1" I then create an identifying relationship between "A" and "Association 1" The PK for "A" shows up as a PK/FK in "A", so far so good. I then create a relationship between "B" and "Association 1". PK from "B" does not show up in the "Association 1" Entity in any way. The key to "B" does not show up as an attribute, it does show up as an FK in the relationships tab for the "Association 1" entity. Trying to add the attribute in the entity flags that it can't be added. This type of entity works for every other combo of entities and relationships in the model. I am baffled. Any thoughts.
So, you do these steps??
Add Entity "Entity A"
Add Attribute "Key A" to "Entity A" as primary key
Add Entity "Entity B"
Add Attribute "Key B" to "Entity B" as primary key
Add Entity "Association 1"
Link EntityA to Association1 by using the identifying relationship tool and clicking EntityA, then Association1
Link EntityB to Association1 by using the identifying relationship tool and clicking EntityB, then Association1
If not, please give us the exact steps.
And, yeah, you're probably right it's obvious and you'll kick yourself when you figure it out, BUT we've all been there and will be again...<grin>
Exactly what I did, and if I do that between A and C it works, if I do it between B and D it works. Only between A and B does it not propagate the key.
Ok, lets try this... For Association1, under the relationships tab, you have 2 related entities (Entity A and Entity B). What Type is listed for each entity? and what FKs are listed for each entity?
Second question, just to make sure. We are talking about a Logical model, not a Physical one, correct?
Lastly, the below is what you see between A & C and between B & D, correct?
In association 1 I have Entity A and Entity B, both relationships are typed as IDENTIFYING and the Keys are A Key and B Key, but they down shop up in the diagram. Truly weird. I also tried to add the field in to association and it would not let me because it already existed.
Truly Weird is right! I'm running out of ideas, so lets review:
Entities A-D all look and act correctly. Associations between A-C and B-D work. Association between A-B does not work. hmmm
Grasping at straws... Create a new entity "AssociationAB". Create Identifying relationships between EntityA & AssociationAB, then between EntityB & AssociationAB. All leaving Association1 alone.
I'm feeling like I'm the help desk telling you to reboot, even though you told me you rebooted twice. But, hey, humor me. Lets see what happens.
Good idea, but no dice. I did reboot though ;)
Rolling on the floor!
I'm clueless. Next up would be to send the model to someone on IDERA's staff. they normally keep an eye out so someone might chime in soon. I hope so for your sake.
Keep this updated as I want to know what it was
Never have figured this out so I left the company. Actually I am at a new job and that problem is somebody else's problem now. Still wonder about it.
Powered by IDERA