Skip to content

[Cherrypick][PLUGIN-1952] and version update for unsupported field name message#149

Open
Ashutosh-Jarvis wants to merge 2 commits intodata-integrations:release/1.2from
cloudsufi:cherry-pick/unsupported-fieldName-message
Open

[Cherrypick][PLUGIN-1952] and version update for unsupported field name message#149
Ashutosh-Jarvis wants to merge 2 commits intodata-integrations:release/1.2from
cloudsufi:cherry-pick/unsupported-fieldName-message

Conversation

@Ashutosh-Jarvis
Copy link
Copy Markdown
Contributor

@Ashutosh-Jarvis Ashutosh-Jarvis commented Apr 13, 2026

cherry picked: d0ae86f
PR Link: #147

fix: include specific field name in error message

What:
Updated the validation logic / error handler to append the exact field name to the resulting output message.

Why:
Previously, the message was too generic, making it difficult to identify exactly which data column triggered the issue. Including the specific field name provides immediate context.

Testing:
Tested by creating the jar of this plugin in local and embedding it with Servicenow connector.

updated version from 1.2.10 to 1.2.11-SNAPSHOT

@vikasrathee-cs vikasrathee-cs changed the title Cherry pick and version update for unsupported field name message [Cherrypick][PLUGIN-1952] and version update for unsupported field name message Apr 13, 2026
@Ashutosh-Jarvis Ashutosh-Jarvis force-pushed the cherry-pick/unsupported-fieldName-message branch from 98153ff to d18ebee Compare April 14, 2026 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant