Skip to main content
Question

Exception when committing staged resource; An item with the same key has already been added

  • May 12, 2026
  • 6 replies
  • 43 views

Willem Hendrix
Rookie
Forum|alt.badge.img

When saving a form to the database in the Universal GUI I get the following error, and after this error the form shows data from a differend database record:


This error seems to be related to the following request:


This error only occurs in the Universal GUI. In the Web GUI and the Windows GUI it works fine.
Anyone have any idea what is causing this error and what a possible solution is?

6 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Willem,

"status_code” is a reserved keyword that Indicium uses for internal processes. You should not name your model objects "status_code” as this error then occurs. There should have been a validation that informs you about this, but I cannot seem to find it in the latest version.

Which version of the platform are you running?

And to resolve the issue, can you rename the object in the Software Factory and deploy the change?


Willem Hendrix
Rookie
Forum|alt.badge.img

Hi Mark,

We are using version 2024.2 of the platform.

Renaming status_code could be an option, however that means changing more than 125 procedures, views, contexts, layouts etc… Including testing the entire application to check if everything is still working after the changes. So if there is an easier solution for this, than that would be more than welcome.


Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Willem,

The impact might be solely scoped to Handler procedures if I read the stack trace correctly, so perhaps it only truly will have to change it in the tables/views that have a handler.

Do not that the 2024.2 is no longer supported since March 2026, so upgrading is advised:
Lifecycle policy | Thinkwise Documentation


Willem Hendrix
Rookie
Forum|alt.badge.img

Hi Mark,

Unfortunately, by renaming the specific “status_code” column, I will still need to modify those 125 objects. But if that’s the only solution to this problem, then so be it.

We are aware that 2024.2 is no longer supported. But in order to upgrade to a newer version we first have to get the application to work with the Universal GUI. And that's what we are currently working on.

Thanks for your help


Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Willem,

Last question, which Indicium version are you running?

The Indicium team did resolve the naming conflict for columns, task and report parameters. Version 2025.2.13 or later have these improvements and that could mean the column named "status_code” is fine to use. My apologies for not mentioning this earlier.

Indicium version 2025.2.13 and later are compatible with the 2024.2 platform version, so you can download and replace your current Indicium version.


Willem Hendrix
Rookie
Forum|alt.badge.img

Hi Mark,

I am running Indicium version 2025.1 so I will try updating Indicium first. Hopefully that will fix the issue.
Thanks.