Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

com.bullhornsdk.data.exception.RestMappingException: #200

Closed
BrianSallee opened this issue Feb 8, 2018 · 4 comments
Closed

com.bullhornsdk.data.exception.RestMappingException: #200

BrianSallee opened this issue Feb 8, 2018 · 4 comments

Comments

@BrianSallee
Copy link

Posting here per BHSupport

When using the following
findEntity(com.bullhornsdk.data.model.entity.core.standard.Candidate.class, xxxxxxx)
we get
com.bullhornsdk.data.exception.RestMappingException:
Error mapping jsonString to class com.bullhornsdk.data.model.entity.core.standard.Candidate. jsonString =

This is not on all candidates, but have not figured out what is different about the subset of candidates that cause this.

@johnsully83
Copy link
Member

This looks like a change made to the REST APIs is causing an issue with the SDK. The very first thing I'd check would be to ensure you have the latest version from Maven. Regardless of whether we do or not, could you post the full stack trace (at least the SDK portion of it). Also, could we post the jsonString in the error message? It will help us identify which field/property is causing the JSON mapping error.

@BrianSallee
Copy link
Author

John, Do you have a private email that I might submit that data through? I don't want to paste production candidate data publicly. If not I can change the values to be non identifying.

@BrianSallee
Copy link
Author

John, I sent the data in question to the gmail account in your GH profile.
Much thanks
Brian

@johnsully83
Copy link
Member

@BrianSallee thanks for that data. Based on that I made a fix to the SDK today which hopefully should remedy your issue (namely the companyUrl field for your configuration is marked as 'Allow multiple values' in field maps, which makes it serialize kind of strange in the REST APIs. We've handled this for most fields but not for this specific one until now).

As of sometime tomorrow you should be able to update your SDK dependency to version 1.2.30 and you should hopefully see the issue resolved. Currently it's still being propogated through Maven currently, but should be ready latest sometime tomorrow.

Feel free to reopen this issue or a new one if you still see issues.

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

No branches or pull requests

2 participants