- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2023 07:48 AM
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].
If I save a second dime after receiving the error, I get this second error message:
I've deduced I can create the attribute for other tables in [Scope 2], so the issue must be with the table... somehow.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2023 09:29 AM - edited 07-18-2023 09:33 AM
The Base table field is not editable in the UI.
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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2023 08:13 AM - edited 07-18-2023 08:52 AM
The system Error logs provide a clue:
name is labeled "Table" and a query of the Dictionary Overrides [sys_dictionary_override] locates the culprit hiding on the "base table's" parent.
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:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2023 09:29 AM - edited 07-18-2023 09:33 AM
The Base table field is not editable in the UI.
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).