-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Tableau 2019.2 set actions cause the extensions to reload it's content #240
Comments
Hrmm, we have a report of this happening when using Parameter Actions and we have some scheduled work to understand the cause of that and fix it. I will add set actions as something to explore as well. |
I did some testing with Set Actions. I used the example described here: Using this set action, the extension does not get reloaded. Can you share more about your workbook or actions? Do you have other actions on the dashboard? I'm assuming you are using server? Thanks for the additional information, |
Hello John. I'm doing it on the desktop version. The example that I was using was the asymmetric drill down (available here), and there, whenever selecting a mark for drill down a refresh is performed. Thanks, |
The issue with the asymmetric drill down example is that changes the data source / summary data without any notification to the extension, so we must reload. We need to add a "summary data changed" notification, but need to figure out how to do that without breaking existing extensions. |
I'm going to close this one as we track 167 and 368. |
Hello,
We got a report stating that when using set actions with Tableau 2019.2 this was causing issues with the usage of our extensions.
I looked into this and what is happening is that every click on the marks that trigger the set action also trigger a reload on the extension frame causing it to lose its context or content. In our case, we have a login token and it is lost, making it so that we have to login every time the extension reloads.
Have you ever come up with this, is a known issue or is there any way to prevent the extension from reloading?
Best regards,
Bruno
The text was updated successfully, but these errors were encountered: