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

Error Deserializing TransactionDetailsApi response (TssV2TransactionsGet200Response) #25

Closed
AndrewJamesMills opened this issue Apr 9, 2019 · 3 comments

Comments

@AndrewJamesMills
Copy link

Full error:
Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.List`1
[CyberSource.Model.TssV2TransactionsGet200ResponseMerchantDefinedInformation]'
because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'merchantDefinedInformation', line 1, position 774.

In the response the merchantDefinedInformation class is null. The point referred to in the JSON is:
..."fraudMarkingInformation":{},"merchantDefinedInformation":{},"merchantInformation":...

Commenting out the merchantDefinedInformation references in the TssV2TransactionsGet200Response I'm able to retrieve the transaction.

@gnongsie
Copy link
Contributor

Hi,
We are aware of issues with the Merchant Defined Information section. We have escalated this issue to the relevant team.

Kindly bear with us while the issue is getting resolved. I will keep you updated on this thread.

@gnongsie
Copy link
Contributor

gnongsie commented Aug 5, 2019

Hi,

Thank you for bringing this to our attention.

This issue has been addressed in the latest version of the SDK.
Kindly fetch the SDK from NuGet (v0.0.0.10) and check again.

@snavinch
Copy link
Contributor

snavinch commented Feb 6, 2020

Closing this issue as it has been addressed

@snavinch snavinch closed this as completed Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants