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

Postman Test data field names does not match the Resource data field names [See the 1st comment for enhancement suggestion] #79

Open
Tasin5541 opened this issue Feb 16, 2022 · 2 comments

Comments

@Tasin5541
Copy link

The test cases provided for Postman has mismatched data field names and as a result, The returned response from the api has null values for those mismatched fields.

Example:

Request
image

Response
image

Look at the ExternalIdentifier and ElectronicMailAddresses fields. Both are null in the response because the request had these fields as externalId and emails respectively.
The test case for EnterpriseUser has more mismatched fields.

@Tasin5541
Copy link
Author

Tasin5541 commented Feb 16, 2022

My bad, I was trying to integrate this in an existing .net core application that was using text.json for serialization instead of newtonsoft and sadly it does not support DataContract (why Microsoft??). So I might need to change the models with JsonPropertyName.

Shouldn't this project be using the default json serializer for .net core 3.1 instead of using newtonsoft? I mean this is a Microsoft project that doesn't use their own library and doesn't want to support DataContract in their default library either. It's very confusing.

@Tasin5541 Tasin5541 changed the title Postman Test data field names does not match the Resource data field names Postman Test data field names does not match the Resource data field names [See the 1st comment for enhancement suggestion] Feb 16, 2022
@quentin-49
Copy link

@Tasin5541 Where/How did you get your response from Azure AD ? I haven't seen anywhere in azure AD how to get the response done by them. :/

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