Unable to update data object with the help of constellation DX api
Hi,
I am trying to update a record inside a data object with the help of constellation DX api (put method).
Even after passing all required field values, I am getting 500 error message (internal server error).
After running the tracer, there was an error related to the history table associated with the data object class. As per the error message, pxTargetClass should be exposed to the history database table.
Even I tried to expose the above-mentioned column, but table name did not appear in the list.
Does this problem have a solution?
Pegasystems Inc.
CA
I hope you're passing the
Please find the snippet of the request to update a record in the Data table in the below link. It's supposed to be the Patch Method. Please find the link has more details.
https://support.pega.com/discussion/pega-constellation-dx-api-reference
Updated: 8 Jul 2025 1:27 EDT
LTIMIndtree
PL
@RameshSangili Thanks for your valuable input!
I am still getting similar error response (500 - internal server error) even after changing the api method to 'Patch'.
Please refer to the attached screenshots where I have captured the request details as well as error details.
Pegasystems Inc.
CA
Can you please enable the REST loggers in Admin Studio to retrieve the raw JSON request, allowing us to understand the request headers and parameters?
Updated: 9 Jul 2025 3:13 EDT
LTIMIndtree
PL
Is it okay to change the current log level to Debug for these 2 following log category or do i need to add any more additional loggers? -
pxIntegration.Service.REST
pxIntegration.Connector.REST
PFA current log file after enabling these 2 above mentioned log categories.
HCA Healthcare
US
@ManobD33 You are getting a 500 internal server error while trying to update a record using the Constellation DX API because of an issue with the history table for the data object class. The error says that the pxTargetClass field should be exposed in the history table, but it is not available. This means that the system is expecting a specific column in the database that is missing. To fix this, check if the history class is properly configured and if its table is mapped under Records > SysAdmin > Database Table. If the table is not mapped, create the mapping manually. Then use "Optimize for Reporting" to expose the pxTargetClass property. Once that’s done, try the API call again, and it should work without the error.
LTIMIndtree
PL
@Sairohith thanks for sharing you observation!
Actually I was able to find that issue while updating that data type manually. I have already mentioned about this history table related issue while initiating this thread. history table mapping already exists and I tried to expose pxtargetclass column for that table as well. But the history table was not appearing in the list while running the column optimization wizard. Also, I tried to expose it by running a ddl script. unfortunately it was throwing some error message.
My understanding is that we should never get this kind of error as it’s not expected to map any such column manually for the history table. There must be something wrong with the table configuration which may be causing this kind of error messege to pop up. we should be having some other alternative to resolve this issue without even modifying the history table!
HCA Healthcare
US
@ManobD33Thanks for your response and for confirming that you already tried exposing the column and even ran a DDL script. I agree that ideally, we should not need to manually expose pxTargetClass in the history table, especially since Pega manages history tables internally. This kind of error usually points to some misconfiguration in the data object’s history class or its table mapping. It might help to review the class group settings or check if the history class is correctly inherited from Data- or mapped to the right table in the database. Also, try disabling history tracking temporarily for that data type and test the DX API again to confirm if the issue is history-related. If it works without history, then we can focus on fixing that specific configuration without touching the table directly.
LTIMIndtree
PL
@SairohithI even tried to disable the history snapshot from the advanced tab of the actual data object class, but it did not help resolving the issue.
My history class is inherited from History-Data- class.
I am facing similar issue even after creating a fresh DataType.
If needed, I am available for a screen sharing session.