Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-7612

JSON null to be imported as ""

XMLWordPrintable

    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When configuring a JSON import, if the JSON includes nulls, these will be imported as string values "null" into any Text Attribute, while the Value "" will be correctly imported as no value.The Use Case:Using a REST API, I get a JSON response.I want to use the Import to Populate a Text Attribute, using two or more datalocators, for example:Datalocators: platformname, platformversion to the Attribute: OS Name (Text):   this import will result in the Attribute "OS Name": "Windows 98 - null"The expected behavior for this case should be: "OS Name": "Windows 98"If the JSON has "platformversion":"" - this will be correct, however, the JSON is a response from a 3rd party application, and cannot be formatted to replace null with ""....

            [JSDSERVER-7612] JSON null to be imported as ""

            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            SET Analytics Bot made changes -
            Support reference count New: 1
            Marc Dacanay made changes -
            Labels Original: affects-server insight-m New: affects-server insight-m ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 977252 ]

            evgeniy russkikh added a comment - - edited

            I am facing the same issue. It should be fixed this way:

            1. If null value in a quotes - parse this as string value "null", example: {"attribute":"null"}
            2. But if null without quotes, it should parsed as no value, example: {"attribute":null}

             

            I have found a workaround: using Regular expression  "^(?!null$)" (without quotes) works ok, but regex matching make huge CPU load, so it can't be used in all the cases

            evgeniy russkikh added a comment - - edited I am facing the same issue. It should be fixed this way: If null value in a quotes - parse this as string value "null", example: {"attribute":"null"} But if null without quotes, it should parsed as no value, example: {"attribute":null}   I have found a workaround: using Regular expression  "^(?!null$)" (without quotes) works ok, but regex matching make huge CPU load, so it can't be used in all the cases
            Alex Cooksey (Inactive) made changes -
            Labels New: affects-server insight-m
            Alex Cooksey (Inactive) created issue -

              Unassigned Unassigned
              da0dd4439f59 Alex Cooksey (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: