pyCommitError when attempting to load Demo Screen Pops to simulate a phone call for updating a dialog
Hi there, am undertaking the Pega Customer Service for Commuications Foundation course via the Pega Academy. When trying to do the execrice on updating dialogs by a manager, I receive the following error:
PyCommitError:
Attached is a screen shot of the error and location of error. Any assistance would be appreciated.
Thank you
Milan
***Moderator Edit: Vidyaranjan | Moved from PSC to Academy***
Pegasystems Inc.
US
Hello Milan,
Sorry you are having issues completing the exercise. I could not reproduce your issue and from your screenshot it is not clear to me the steps you took that resulted in the error message. When I completed the steps in the exercise it worked for me. I have attached the steps with the screenshots that I got when I completed the steps. Please try to redo the steps with the further clarifications provided in my screenshots. If you still get the error please provide more details of the steps you took that resulted in the error.
Thanks,
Luigi
Pegasystems Inc.
IN
There is an SR (SE-28925) and mesh link (https://mesh.pega.com/message/229723) to resolve similar issue.
Try below steps to resolve the issue as outlined in the mesh:
- When you get this error, identify the exact HISTORY class name in question. I do this by looking at the history record key in the error message, and seeing it's "History- OJYQN8-MyCSApp-Work " in this case: History-OJYQN8-MyCSApp-Work-Grp2-Interaction
- Search for that name in the search gadget, and open up the "Database Table" instance associated with it (Data-Admin-DB-Table)
- Note that the table is probably mapped to the same table mentioned in the error you see on your screen, like "pr_History_ OJYQN8-MyCSApp-Work-Grp2-Interaction "
- Change that mapping field to "pc_history_work"
- Save the database table rule
- Click the "Test connectivity" button: it should open a new tab and say something like: "Class History- OJYQN8-MyCSApp-Work-Grp2-Interaction is mapped to table prpc72.pc_history_work in database PegaDATA."
- Try your operation again, it should succeed.