Skip to content

MID-10911 Fix generic "Fatal error" message in object tables#646

Open
kay1313 wants to merge 1 commit into
masterfrom
fix/MID-10911
Open

MID-10911 Fix generic "Fatal error" message in object tables#646
kay1313 wants to merge 1 commit into
masterfrom
fix/MID-10911

Conversation

@kay1313
Copy link
Copy Markdown
Contributor

@kay1313 kay1313 commented May 11, 2026

Summary

Improves error reporting in object tables.

When a table search/list operation failed, the UI displayed only a generic synthetic row:

Fatal error

even when the underlying OperationResult already contained a useful diagnostic message. This made users check server logs to understand what actually failed.

This change keeps the existing synthetic error row behavior, but includes the available OperationResult message in the row label.

Example

Before:

Fatal error

After:

Fatal error: Couldn't list objects: CSV validation failed. Required unique attribute 'empnum' is empty at record 2. Each record must contain a non-empty value for 'empnum'.

Related work

Related CSV connector fix: Evolveum/connector-csv#8

The connector PR improves the connector-side validation message. This PR makes such list/search failure details visible in object tables.

Testing

Tested with a CSV resource where the configured unique attribute contains an empty value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant