Skip to content

[PLUGIN-1952] Add column details in logging in case of invalid data#147

Merged
vikasrathee-cs merged 1 commit intodata-integrations:developfrom
Ashutosh-Jarvis:feature/unsupported-field-fix
Apr 8, 2026
Merged

[PLUGIN-1952] Add column details in logging in case of invalid data#147
vikasrathee-cs merged 1 commit intodata-integrations:developfrom
Ashutosh-Jarvis:feature/unsupported-field-fix

Conversation

@Ashutosh-Jarvis
Copy link
Copy Markdown
Contributor

@Ashutosh-Jarvis Ashutosh-Jarvis commented Mar 23, 2026

PLUGIN-1952 Add column details in logging in case of invalid data

In case of invalid data mention the column name along with wrong data.

@Ashutosh-Jarvis Ashutosh-Jarvis changed the title Feature/unsupported field fix Unsupported data exception fix Mar 23, 2026
@vikasrathee-cs vikasrathee-cs self-requested a review March 23, 2026 12:45

@Test
public void testConvertToDoubleValue() throws ParseException {
Assert.assertEquals(42.0, ServiceNowRecordConverter.convertToDoubleValue("42"), 0.0);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

write a test case to compare error message

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working on it

Copy link
Copy Markdown
Contributor

@itsankit-google itsankit-google left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Please add a JIRA to the PR.

  • Also add proper description:

    • It should be able to answer What, Why and Testing details.

@vikasrathee-cs vikasrathee-cs changed the title Unsupported data exception fix [PLUGIN-1952] Add column details in logging in case of invalid data Mar 30, 2026
@Ashutosh-Jarvis
Copy link
Copy Markdown
Contributor Author

Ashutosh-Jarvis commented Apr 1, 2026

@itsankit-google here is the description kindly review it
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.

Screenshot From 2026-04-01 04-54-40

@Ashutosh-Jarvis Ashutosh-Jarvis force-pushed the feature/unsupported-field-fix branch from 5ed9fc2 to d0ae86f Compare April 8, 2026 08:18
@vikasrathee-cs vikasrathee-cs merged commit fadd5db into data-integrations:develop Apr 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants