Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Filter exception

    Hi Isomorphic,

    Using v12.0p_2018-08-23/PowerEdition Deployment (built 2018-08-23),
    if filter is visible and I hover on the header of ListGrid, I get this exception:
    Code:
    14:56:12.934:MMV1:WARN:Log:TypeError: Cannot read property 'getValidOperators' of null
    Stack from error.stack:
        ListGrid.getFieldUIOperatorList(<no args: exited>) on[ListGrid ID:LeadlistManagement_inCreation] @ ISC_Grids.js:1841:592
        ListGrid.getFilterOperatorMenuItems(<no args: exited>) on[ListGrid ID:LeadlistManagement_inCreation] @ ISC_Grids.js:2773:311
        ListGrid.getHeaderContextMenuItems(<no args: exited>) on[ListGrid ID:LeadlistManagement_inCreation] @ ISC_Grids.js:2796:266
        ListGrid.shouldShowHeaderMenuButton(<no args: exited>) on[ListGrid ID:LeadlistManagement_inCreation] @ ISC_Grids.js:2651:90
        _3.handleMouseOver(<no args: exited>) on [Button ID:isc_Button_5] @ ISC_Grids.js:2552:180
        [c]EventHandler.bubbleEvent(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:2133:89
        [c]EventHandler.handleEvent(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1855:351
        EventHandler.__handleMouseMove(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1940:19
        EventHandler._handleMouseMove(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1924:244
        [c]EventHandler.handleMouseMove(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1924:11
        [c]EventHandler.dispatch(_1=>[c]EventHandler.handleMouseMove(), _2=>[object MouseEvent]) on [Class EventHandler] @ ISC_Core.js:2220:108
        HTMLDocument.eval(event=>[object MouseEvent]) @ [no file]:3:123
    Can you take a look at this?

    Best regards
    Pavo

    #2
    Are you using custom SimpleTypes or applying custom validOperators?

    Comment


      #3
      Hi Isomorphic,

      this is most likely the same issue as the 2nd one here.

      Best regards
      Blama

      Comment


        #4
        This was actually a different instance, but the same issue - fixed for builds dated December 26 and later

        Comment

        Working...
        X