Hi,

I'm running into an issue where a field is being removed from an entity during synchronization with the database, even though the column still exists in the database and catalog.

The entity in question is quite central to our model and has many relationships. If I remove the entity and add it back from the catalog, the field remains as it should. However, this action introduces a large number of 'suspicious' changes, which could potentially be explained by subtle changes in llblgen versions through the years.

My question is: what is the best course of action to fix this without having to re-add the entire entity?

Are there specific things within the .llblgenproj file I should check for that could cause this behavior, such as a subtle merge conflict?

We're using llblgen 5.12.1 for our project (which has been upgraded through the years).

Thanks in advance for your help.

Best regards, Alexander

Found it, it was an issue with a constraint and exactly like I thought some merge issue. Another colleague of mine had used the same name for an index. But don't understand why llblgen then just throws away the field.