Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error writing to interaction history



All inbound Service Requests fail with an error written to the Interaction History (IH).

Error Messages

Error in SomeService: Cannot save instance of class Data-Decision-IH-Fact; it belongs to fully exposed table dataschema.PR_DATA_IH_FACT in database PegaDATA, but the instance has properties which do not correspond to columns: ServiceId

Steps to Reproduce

Not Applicable

Root Cause

A software use or operation error.

In the environment, two independent applications are present in the system which write to the same IH Fact table. The 'Data-Decision-IH-Fact' IH Fact class is customised with additional properties. Previously, an application used a custom property named  'ServiceId' to write to the IH FACT table (Data-Decision-IH-Fact) (this worked correctly).

In the last deployment to Production, for the second application, a property is created to write to the IH FACT table but is named as 'ServiceID' (the casing is different from the first application). After the introduction of this new property in the second application, the first application failed with the reported error. 

In the new deployment, for the same Data-Decision-IH-Fact class (which is fully exposed), a differently cased property is present in the system. The database connection and its relevant column mapping is set to the first accessed property.


Perform the following local-change:

Modify the second application such that the casing of the properties is the same for the 'Data-Decision-IH-Fact' class across all applications.
  1. In the Data-Decision-IH-Fact class, withdraw the 'ServiceID' property and introduce a new property 'ServiceId' with the same case as the first application.
  2. In the SR class, withdraw the 'ServiceID' property and recreate the 'ServiceId' property .
  3. Update all the Strategy references to reflect the new property.
  4. Update the pyInteractionHistoryConfiguration data transform to reflect the case change.
  5. Restart all the nodes.

Published January 17, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us