"Invalid Insert" error for Dictionary Override

brian_rowland
Giga Guru

While working on a series of Dictionary Overrides of the cmdb_ci.correlation_id field to set attributes for child tables, one table returned the "Invalid insert" error on Submit.

 

Starting from the Dictionary Entry for cmdb_ci.correlation_id, I started a New Dictionary Override while in the scope of the table I want to apply the override for [Scope 2].  I have already created a dictionary override for a field in another scope [Scope 1].

brianrowland_ne_1-1689691567374.png

If I save a second dime after receiving the error, I get this second error message:

brianrowland_ne_0-1689691223543.png

I've deduced I can create the attribute for other tables in [Scope 2], so the issue must be with the table... somehow.

 

1 ACCEPTED SOLUTION

The Base table field is not editable in the UI. 

brianrowland_ne_5-1689695854234.png

An XML export/import, followed by setting/unsetting an unused override captures the updated file in the current update set, and resolves the issue.

 

The "Invalid insert" error suggests the action is attempting to write an invalid value to the DB.  In this case it was the attempted insert of duplicate override (extended table + target field).

View solution in original post

2 REPLIES 2

brian_rowland
Giga Guru

The system Error logs provide a clue:

brianrowland_ne_1-1689692675513.png

name is labeled "Table" and a query of the Dictionary Overrides [sys_dictionary_override] locates the culprit hiding on the "base table's" parent.

 

brianrowland_ne_3-1689692947867.png

Why is that?  the [cmdb] table doesn't even have the correlation_id field, and here's a clue we have a problem w/ the override:

brianrowland_ne_4-1689693153155.png

 

The Base table field is not editable in the UI. 

brianrowland_ne_5-1689695854234.png

An XML export/import, followed by setting/unsetting an unused override captures the updated file in the current update set, and resolves the issue.

 

The "Invalid insert" error suggests the action is attempting to write an invalid value to the DB.  In this case it was the attempted insert of duplicate override (extended table + target field).