Scalability Tool not recognizing Vizlib Objects

[eeide]

I am having trouble with the scalability testing tool recognizing Vizlib objects.

For example - I have a vizlib filter that is recognized in the App Structure when in an action but is not recognized when selecting that filter in the listboxid. This is just one example. I'm also having trouble with date range picker as well. Any ideas why? 

[lucas85moose · Accepted solution]

The issue you're experiencing with the Qlik Scalability Tool not recognizing Vizlib objects like the Vizlib Filter or Date Range Picker stems primarily from how Vizlib extensions are built. Unlike native Qlik Sense objects, Vizlib components are custom-rendered using JavaScript and Angular frameworks, which means they often load asynchronously and don’t follow the same internal APIs or object IDs. While these objects may appear in the app structure—especially when referenced through actions—they typically do not expose native listbox IDs or selection interfaces that the Scalability Tool can interact with. This causes problems when attempting to simulate user interactions such as selections or filtering during load testing. Additionally, because Vizlib objects often rely on client-side rendering that happens after the main Qlik app has loaded, the Scalability Tool may attempt to interact with them before they’re fully available, resulting in failures or unrecognized actions. A common workaround is to temporarily replace Vizlib objects with native Qlik equivalents (like filter panes or native date pickers) during scalability testing to ensure compatibility. Another option is to use variable-based logic—if the Vizlib object sets a variable, the tool can simulate setting that variable’s value directly rather than interacting with the visual component. This can help approximate the user behavior you intend to test, even if the exact object can’t be used in the script.  
dog sounds meaning