Forum Discussion

WojtekGS's avatar
WojtekGS
Data Storage
02-11-2025
Solved

New tabber implementation - multiple tabbers

I noticed new tabber implementation with UI controls. Great, I never liked scritping with widget IDs.

There seems to be major flaw though. Consider this scenario: I have 2 tabbers on dashboard, one should only affect widgets a,b and c and 2nd should only affect widgets x,y and z. I current implementation each tabber affects all widgets. under each tabber all widgets are listed and I can only select / unselect widgets to show. so while I change tabber 1 I am affecting widgets a,b,c but also x,y,z.

Unless im missing something , you cannot use multiple tabbers with new implementation.

I appreciate option to disable new implementation but I would love to use it if someone can fix that issue. THanks

  • WojtekGSThanks for your clarification! If you’d like to verify that all issues are known by R&D and will be addressed, please consider raising a case with the Support Team.

3 Replies

  • Liliia_DevX's avatar
    Liliia_DevX
    Sisense Employee

    WojtekGS hi! 

    Thanks for reporting this issue. This is currently under investigation by our R&D team so please follow our Release Notes to see when it's addressed. As a temporary workaround, you can use widget.scriptConfig = true; in the widget script and define the required logic accordingly.

    Please let me know if you have any additional questions on it, I'll be happy to assist you 🙂 

  • WojtekGS's avatar
    WojtekGS
    Data Storage

    HI Liliia_DevX . THanks for prompt resonse and update. I did reverted to using widget.scriptConfig = true but there still seem to be some impact from tabber ui. It still seems to affect what widgets are visible on dashboard load . You may want raise that with R&D team. 

    I will look forward to fix in new release.

    Thanks,

    W

    • Liliia_DevX's avatar
      Liliia_DevX
      Sisense Employee

      WojtekGSThanks for your clarification! If you’d like to verify that all issues are known by R&D and will be addressed, please consider raising a case with the Support Team.