Hello Walaa,
thanx for the quick reply.
I tested it again with refreshing in the designer ....
And indeed ... now it also changes back to the default.
I found the following message in the refresh log:
Field 'Portal_ChildPortal' mapped onto relation 'Portal_SiteMapRule.ChildPortalId - Portal_Portal.PortalId (m:1)' has been renamed to 'Portal_Portal_' (Sync with name of target)
Portal_ChildPortal is the name I gave it manually, Portal_Portal_ is the name it was given by llblgen. So this shows that it actually is overriden by the refresh process.
hummm ... now what?
Paul
ps:
I looked at project settings, found:
SyncMappedElementNamesAfterRefresh = true
I put this on true, in order to make sure that changes to the datamodel would immediatly appear in the regenerated code. Which is still what I want without exception ... ahum, except this exception.
The problem is that the fieldname llblgen generates is not coming from the database either, it is a 'creation' of logic in llblgen.
Do you see a way of dealing with this???