App reports Error when change tracking enabled for Entities with a key field not named ID about change-tracking

[nkaputnik]

Hi @dinurp
this is not a bug or issue with Change-Tracking, this is a limitation of Fiori Draft.
Draft-Enabling an entity requires the entity to have a GUUID based ID, so this error message has nothing to do with the Plug-in.

Best,
Nick

[dinurp]

Hi Nick,
The issue remains even when the type of the field is changed to UUID. Fiori draft does not mandate that the keys are named ID. For localized entities, the generated key is named ID_texts. It is not evident in the stack trace. But, the query that causes the crash is from change tracking.
BTW: The type Integer was in the generated sample with cds add samples and it works just fine when change tracking is not used.
Regards,
Dinu

[nkaputnik]

Hello @dinurp
we will look into this. In the meantime, since this is an open source project: If you can debug your project and pinpoint to specific pieces of the plug-in code, this would be a huge help for us.

Best,
Nick

[dinurp]

Dear Nick,
Here is the fix that worked for me. It may not cover all the cases, but solved the I issue I faced.
diff-support-naming-keyfield.txt
Regards,
Dinu