Make DealField OrderNr nullable #139
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've started running into this as well. The API must've returned 0 instead of null directly up until a few weeks ago. The problem seems to stem from sub-fields created based on the field type. We have custom monetary and address "deal" fields that generated sub-fields with no direct ID. They have a parent_id but their id, order_nr and a majority of their attributes are null. The problematic sub-fields: address
monetary
|
|
It's more than just this one field. Other Boolean and DateTime field values are passed back in the Pipedrive API response as being null. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Pipedrive API documentation does not seem to state that explicitly, but I am experiencing that a deal field's order nr can also be
null.