Obj-Save fail with BadTableMappingException though column is exposed in DB
Hi Team,
Though column is present is non pzPVStream pega table (oracle), Obj-save getting failed with "BadTableMappingException: Database-BadTableMapping-TooManyProperties as RequestId is not exposed in table". if we map in external mapping for class it is working(RequestId RequestId) . but wanted to confirm on why it is failing with out external mapping, rest all columns are also same way present but working without extenal mapping.
Tried out saving DB instance and DB table instances.
This is happening post upgarde from 7.4 to 8.8 in all environments including prod.
Thanks in advance,
Suresh
Accepted Solution
Updated: 29 Feb 2024 8:24 EST
S & P Global Inc
IN
@Soham_Chanda1107 Saved the DB instance but that didn't help. I found that RequestID ,RequestId named properties exists in inheritance(child) , because of conflict between RequestID and RequestId properties. It is not considering RequestId only cosidering RequestID while saving . So adding RequestId seems mandatory in class mapping
Maantic Inc
IN
@SureshBhSave the DB table instance once post exposing and check. If not also check in schema details if the column exposed is coming or not .
Under configure->system->database->modify schema.
Accepted Solution
Updated: 29 Feb 2024 8:24 EST
S & P Global Inc
IN
@Soham_Chanda1107 Saved the DB instance but that didn't help. I found that RequestID ,RequestId named properties exists in inheritance(child) , because of conflict between RequestID and RequestId properties. It is not considering RequestId only cosidering RequestID while saving . So adding RequestId seems mandatory in class mapping