I have a subtype of Position, GPPosition, with a self-reference called NonHotelColumn (using self-servicing, 2.0). When I move this field to the subtype, rather than leaving it in Position, I get several compile errors in the generated code that attempts to reference PositionFieldIndex.NonHotelColumn. For example: in PositionRelations, I have

public virtual IEntityRelation PositionEntityUsingNonHotelColumn
        {
            get
            {

                IEntityRelation relation = new EntityRelation(SD.LLBLGen.Pro.ORMSupportClasses.RelationType.OneToMany);
                relation.StartEntityIsPkSide = true;
                relation.AddEntityFieldPair(EntityFieldFactory.Create(PositionFieldIndex.ID), EntityFieldFactory.Create(PositionFieldIndex.NonHotelColumn));
                relation.InheritanceInfoPkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("PositionEntity", true);
                relation.InheritanceInfoFkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("PositionEntity", false);
                return relation;
            }
        }

I have a similar problem in PositionDAO.

This is caused by a strange thing in your project: the relation Position -> Postion (m:1), namely Position.NonHotelColumn -> Position.Id

is defined on Position, but that's wrong, the designer should have unmapped this relations because NonHotelColumn isn't part of Position, it's not mapped there.

Bug no. 3 found with this project. I think it's all related to an incorrectly working relation detection routine, which caused a couple of issues you ran into. I hope to have a fix for you tomorrow (wednesday).

Otis wrote:

Bug no. 3 found with this project. I think it's all related to an incorrectly working relation detection routine, which caused a couple of issues you ran into. I hope to have a fix for you tomorrow (wednesday).

Thanks for the help. 3 bugs - do I get a free t-shirt?

A free T-shirt is earned after the 100th bug

The bug in question is caused by the fact that when a field is unmapped, a relation with self over that field isn't removed. Fixed in next build.