Hi guys,

I have table B which is a subtable of A. I created a typedList a while ago before the inheritance feature was available using the relation between these tables. Today, I decided to use the inheritance feature, and I created the hierarchy. When I regenerated the code, it won't compile. It seems the relation I was using is now changed because of the hierarchy, but the typed list is till using the old name. If I manually change the bad relation to RelationToSuperTypeAEntity it will compile, but I need to get this set properly in the desinger so I don't have to do it every time I regenerate. Any suggestions?

thanks, Jason

ps. I'm using 1.0.2005.1 released July 6th

Your typedlist contains a relation which is now used for the hierarchy? (I.e. a 1:1 PK-PK relation) ?

Thats correct

Jason wrote:

Thats correct

I indeed think that's a bug. To correct it in the current typedlist, select an alternative relation to base the typed list on.

I'll see if I can fix it in the code base as it's likely also present in v2.0

I had the same idea (selecting anoter relation to use) but when I click the relation I want to change, the dropdown for "Select Alternative" is completely blank (ie there is not even one currently selected). I tried removing the base entity and readding it, but its greyed out, even though the subEntity is included. I then tried removing the subEntity and readding it which worked, but doing this still didn't allow the base entity to be added.

Jason

Well, there has to be a relation left other than the relation used for the hierarchy, to connect an entity A with an entity B, both in the typedlist. Is that the case?

Thats the part that seems to be broken. Before I created the hierarchy, there was a relation "A" that connected the two. Now with the hierarchy, the dropdown is blank, and the generated code for the typed list still uses the old relation "A" which doesn't exist in the Relation class for the entity.

Though is there a relation between B and A which isn't the one used for the hierarchy? The hierarchy uses the relation between the PK's of B and A (the 1:1 relation). If not, it's not possible to add both to the typedlist for obvious reasons.

Though is there a relation between B and A which isn't the one used for the hierarchy?

No, there is only the 1:1 relationship between the two tables.

If not, it's not possible to add both to the typedlist for obvious reasons.

Maybe I'm misunderstanding how the typedLists work. In my case I'm working with a base class "Transaction" which has a subtype "LeadPurchaseTransaction". I want the typedList to include fields from both tables. If I add "LeadPurchaseTransaction", will I automatically be able to use fields from the "Transaction" table, or do I have to include a relation to that manually?

It may be a bit of a misunderstanding. LeadPurchaseTransaction cannot exist without Transaction. So if you ever have a LeadPurchaseTransaction entity you will be modifying the values in both tables due the the inheritance in LLBLGen.