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.
LinkedIn
Copied!

Table of Contents

Troubleshooting: duplicate pzInsKeys error after setting up a copy of the pc_work table

Summary

A developer asks: I'm receiving an error message that there is more than one result for pzInsKey, and that I should ensure that my database has its pzInsKey set properly. This happens for covered work objects.

What do I need to do to make sure that pzInsKey properties are set properly so that such duplicates are not created?

 

 

 

Suggested Approach

If you have created a copy of the database table pc_work to hold work objects, examine the pc_work database constraints. Make sure that your copy of the pc_work table matches those exactly. 

Unless the constraints are included in your cloned table, you'll get duplicate work objects that could produce the message you're seeing.

Examine the schema for pc_work closely.  That may reveal changes you must make to your clone. 

For example, inside the schema to pc_work there is a reference to pc_work, so you have to update your copied table name to reference itself, similarly. 

 

Did you find this content helpful?

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.