Assets Two dimensional report using a Number Attribute fails

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 10.3.14, 11.3.0
    • Affects Version/s: 10.3.8, 10.3.9, 10.3.10, 11.1.1
    • Component/s: Assets - Report
    • 1
    • Severity 3 - Minor

      Issue Summary

      An Assets 2D report, with a numeric attribute set to one of its axis, will fail to display if the attribute has different values across objects.

      Steps to Reproduce

      1. Create a blank object schema in Assets
      2. Create a single object type, and add an attribute: "Number" of the default type Integer or Float
      3. Create 2 objects in this object type:
        Object1 with Number = 1
        Object2 with Number = 2
      4. Navigate to Assets>Report and create a new 2-Dimensional report:
        Indicate the schema and object type created above.
        For the Y axis select the Name attribute
        For the X axis select the Number attribute
      5. Try generating a preview, or save settings and open the report

      Expected Results

      The report/preview is opened - showing a table where the Y axis is the Name attribute, and the X axis shows the values of the respective Number attribute

      Actual Results

      "Oops...
      Something went wrong while rendering the report. Please try again, or contact your administrator if the problem persists."

      The below error is showing in the Browser's console:

      ...The following error occurred while rendering the widget. Please verify the requested mapper or viewer. Error: d.localeCompare is not a function
          value jQuery
      batch.js:3437:31433
          jQuery 43
              value
          (Async: EventListener.handleEvent)
              value
              Js
              Zs
              Xf
              bf
              rn
              ta
              Ft
              fi
              notify
              y
              d
              B
              i
              m
              dispatch
              D
          (Async: promise callback)
              D
              i
              m
              dispatch
              s
              i
              m
              dispatch
              n
              i
              m
              E
              value
              V
              ya
              wa
              ka
              Lo
              Ro
              fu
              fi
              Ii
              fu
              Kl
              Ia 

      Workaround

      The only alternative is to copy the numeric values to a text attribute (e.g. using Assets Automation rule), and use the text attribute in the report

      Versions Tested

      Testing Requirements Version Affected Version
      Customers Reported Version 10.3.8 Y
      Most Recent Bug-Fix Release 11.1.1 Y
      Previous Major Release    
      Most Recent LTS    
      Previous Supported LTS 9.12.26 Y
      Other Versions.. 10.3.10 Y

            Assignee:
            Jim Alexander
            Reporter:
            Yinon Negev
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: