Skip to content

Make DealField OrderNr nullable#139

Open
kardoaw wants to merge 1 commit intoDavidRouyer:masterfrom
kardoaw:bug/deal-field-order-nr-is-not-nullable
Open

Make DealField OrderNr nullable#139
kardoaw wants to merge 1 commit intoDavidRouyer:masterfrom
kardoaw:bug/deal-field-order-nr-is-not-nullable

Conversation

@kardoaw
Copy link
Copy Markdown

@kardoaw kardoaw commented Dec 16, 2022

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.

@NChampion
Copy link
Copy Markdown

NChampion commented Dec 23, 2022

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

  • Apartment/suite no
  • House number
  • Street/road name
  • District/sublocality
  • City/town/village/locality
  • State/county
  • Region
  • Country
  • ZIP/Postal code
  • Full/combined address

monetary

  • Currency
  • Currency of [Fieldname]

@gregarican
Copy link
Copy Markdown
Contributor

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants