i have compilation error on my on premises instance.
I performed the following steps:
- Generated the source code for all schemas.
- Performed a Compile All.
After generating the source code, the number of compilation errors decreased significantly. However, there are still some remaining errors, which I have attached. I have also attached a screenshot of the system message displayed after generating the source code for all schemas.
Additionally, based on the remaining compilation errors, they all appear to be related to the UsrEntity_Agent entity. I have attached a screenshot of this entity from the Application Hub for your reference.
However, the source code generation fails with the following error:
Unable to generate source codes for the following schema: "UsrEntity_Agent".
Additionally, the object itself displays the following validation error:
Property conflict in 'UsrEntity_Agent': property 'UsrIDExpiryDate' already exists. Please rename one of the conflicting columns and republish the affected schemas.
The problem is that I am unable to edit or rename the object's columns in any way, so I cannot resolve the conflict or proceed with generating the source code.
I have attached screenshots showing:
- The Column name conflict error on the UsrEntity_Agent object.
- The Unable to generate source code error that appears when attempting to generate the source code.
Could you please advise on how to resolve these remaining compilation errors? If the UsrEntity_Agent entity is corrupted or incomplete, is there a recommended way to repair or regenerate it?
Like
Hi Mohamed,
Thank you for the detailed description and the logs.
The blocking issue is a duplicate column in the inheritance chain. UsrEntity_Agent is a child object that inherits from Contact, and the columns UsrIDExpiryDate, UsrIDIssuanceDate, and UsrAgentNationalID are defined both on the parent and directly on UsrEntity_Agent. This is exactly what the validation message reports:
Property conflict in 'UsrEntity_Agent': property 'UsrIDExpiryDate' already exists.
This conflict is what stops source code generation. A duplicate property definition like this can happen because:
- the same column exists on both the parent object and the child object in the inheritance chain,
- a back-reference property generated from a lookup collides with an existing column,
- two different packages define the same column in different layers.
To resolve it, remove or rename the duplicated columns so that each is defined only once in the chain. Then run Generate source code for all schemas, followed by Compile All.