This is my first attempt with replacetable autokey methods, so I may be doing this incorrectly.

The actual solution uses a similar approach with jsonutils to serialize data for a temp cache.  I ran into an exception after invoking GetTableWithoutKey() then trying to add a new record to the same table.

I built a small test code that fails in Pega Robotics Studio 19.1.77:

The error found in the logs is:

INFO  | 2021-07-15 13:54:59,848 |      16 | 16  | 14984 | MTA   | Automation                | Automation1                    | luErrors-8281398               | AddRecord: Exception invoking method - Column 'ID' is constrained to be unique.  Value '1' is already present.

Is this error expected with this automation?

Am I using this incorrectly? / Is this a design issue?

The simple fix is handling the index manually, removing the index conflict, but I'd like to avoid this unless necessary.

Thanks!

-Chris