Hi,
I am trying to set up this code on my server. The first issue I am getting this the code is not running on https. I have written a proxy server in nodejs but I am getting an error of WebSocket. Can somebody help me with what I am doing wrong?

Let users search the list of options in the parameter.

I have an automated deployment method for pulling and publishing extensions in a self-hosted tableau-extensions server. The current folder contents have trex files named as <extension>v2.0.0.trex and <extension>v2.1.0.trex, while other tableau extensions repos are just <extension>.trex.

Can we tag the repos with versions, so that people requiring a specific version can checkout the appropriate tag, and make this repo have only one .trex file as <extension>.trex?

That would be very much appreciated

Hey Keshia,

I've got a bit of time and am considering upgrading to v2.1, but I'm not clear on what's new / different and what might break.
From reading your commits, one point seems to be that the extension 'refreshes' when the parameter value changes -- is this equivalent to the 2.0 config option for 'Update list of values on param change'? We don't use this, so having it as a default might be reason to avoid..

If you have a min, would love a little changelog / advice on how usability might differ. Also, apologies if I'm blowing a minor update out of proportion!

--Matt

Show checkboxes next to options in multi-select for selection instead of clicking on the value for selection.

This will require re-building the multi-select into a div instead of html select element.

Reproduction steps:

Develop dashboard, multiple sheets.
Copy paste dashboard to an new workbook.
Add data driven parameter extension to this dashboard.
Extension does not load. Unable to configure.
Behavior not the same as other extensions.

I've used this extension for a while now but this week it stopped working for me. After clicking a value in a worksheet the extension used to provide a drop down of a filtered list, now however it just says "Parameter Needs Configuration". I realised there is a new version 2.1 and I tried to use that however when I click a dashboard action the extension will remove all filters and jump to the the first value it fines, rendering it useless. This is a very useful tool when it works, any ideas what happened this week to stop it from working?

When I select a value from the list in the Data-Driven Parameters extension three things happen:

1. The parameter is changed to the selected value
2. The list is re-loaded
3. The parameter is reset to the first item in the list.

Is it possible that I have something set so as to trigger this behavior? Any help would be appreciated.

This is not possible as we need to use the default html element in order for the drop down to flow outside the dashboard extension zone.

Parameter is sometimes showing the other options in the drop down as blank.

These values are present - when selecting a "blank" square, it updates the value in the parameter.

Resizing the dashboard will cause all of the drop down values to display properly.

Having difficulty reproducing - only affects some users.

Tableau Server 2019.2.2

Chrome: 76.0.3809.132

No issues on other browser on same machine.

Thanks

Hi Keisha,

When we are trying to configure the dashboard extension it is not letting us select the field. It just shows loading. Please note that I already have another dashboard extension on the same dashboard and it works fine. I even tried to remove the other and tried it but still doesn't work. Please help.

please see the below screenshot:

Hi Keshia,

The update one hour ago broke our implementation of the extension.
We are using it to hold a list of dates, defaulting to Most Recent. It has worked well for months now.
An hour ago we noticed that our dashboard was empty -- not being fed the Most Recent date by the extension -- though the extension is displaying Most Recent as the selection. If we toggle to another date (successfully populating dashboard with that date), and back to Most Recent, the dashboard then populates with the Most Recent parameter.

Can you explain what was changed in the most recent release?
Having only skimmed your commit, my theory is that no event is emitted upon first load -- only on change. Thus we're missing the value initially present on load.

Thanks,
Matt

On our Tableau Server, it seems like the DDP extension does not work for users with only Viewer permission. When promoted to Interactor, the extension works normally.
This is fine. Though I'm curious what minimum components of Interactor permission are needed -- I suspect it's Filter or Web Edit specifically.

Please feel free to close this right away, more a question than issue.

Hey Keshia,

This might be unique to how we've structured our dashboard navigation.
Our workbook consists of 5 dashboards that are moved between with tab-like buttons that execute go-to-sheet dashboard actions. Every page is linked to every other page this way.
The DDP extension exists on each page.

When a user navigates to a new page by clicking a button and triggering the dashboard action:

1. the page will load with Tableau Server spinner
2. Tableau server spinner finishes
3. the DDP extension reads 'loading' and populates, triggering the mouse cursor to display an hourglass
4. the DDP extension finishes populating and the page is ready for interaction, but the cursor remains an hourglass until the mouse is moved in the slightest

This is confusing some users who are waiting, without touching the mouse, for the cursor to change from hourglass back to mouse pointer.
I noticed this does not happen when the cursor placed in non-workbook screen space -- eg: the gray background area to the left and right of the dashboard, or the Tableau Server breadcrumb header or toolbar.

Any thoughts?
This is occurring in Chrome 77.0.3865.120

Hi ,

First of thank you so much for making this happen. Its really awesome.
We just started using multiselect feature and we found a bug. When we select the values and go and after that when we change the filters on other fields, the selections on multiselect would go away. Is there anything you could do immediately on this issue?
And I am also eagerly waiting on other fixes like dropdown and having boxes etc.

Have a great day...!!
Again thank you so much for your work..!!

Thanks,
Bharath

Hi Keshia,

Happy Halloween!
So today I did some deep testing of v2.0.0 and v2.1.0.
We're using DDP to pull in a new most-recent data date, from an extract, on dashboard load.
To test it, I've followed this process:

• publish identical dashboard versions using DDP 2.0 and 2.1 to our Tableau server with the most-recent date displayed prominently
• update the most-recent date (in our database) that DDP is watching for
• run an extract for the most-recent date datasource, to include the database change
• refresh each dashboard, hoping DDP has caught the new most-recent date and has set the parameter accordingly on-load

I also made sub-versions with and without 'reset values on load' -- I'm not sure how this setting is intended to be used so I wanted to see if it changed anything.

It seems that 2.0 will pick up this sort of data change, but 2.1 will not - at least not on dashboard-load.
Can you reassure me that this behaving as intended?
Does only 2.0 check for / populate new values on-load? Looks like 2.1 supports other hooks for checking, like parameter change, so perhaps the focus has shifted there.
If so, just wanna mention that we find the immediate-check very useful and have built it to be the beating heart of our dashboards!

--Matt

Tableau Server: 2019.2.1
Tableau Desktop: 2019.2.1

First off - love the extension! When publishing a dashboard to Tableau server the data driven parameter is reverting to the first value in the option list. I have published versions with both Automatically reset values on dashboard load checked and unchecked and neither changes this behavior.

I have a workbook with multiple tab and each one of this tab have an data drive parameter extension in then referring to same field. When i browser the report in IE-11 it get an Error message popup on switching between tabs (Screenshot).

But the same report works fine on Mozilla and Chrome.

@KeshiaRose I'm trying to test the extension however seems that I'm not able to save the changes (screenshot attached) . I've tested in Tableau desktop 2018.3 , 2019.1 and 2019.3 , same issue

Can you please check if something changed?

Thanks
Sebastian

Hi,

Would it be possible to add the ability to multiselect?
And that you can choose your own delimiter.

Thanks a lot for this extension, it is awesome!

Hi, this is a great extension for Tableau, thanks a lot :)

I have my parameter half way down the dashboard, and one issue I seem to have is the parameter values don't update automatically if the corresponding worksheet is filtered. They will only update and refresh once something is picked. Is there a solution to this at all? I was hoping for it to act in a similar way to a quick filter set to 'only relevant values'

Cheers

I've created a webserver on an instance which is within a private VPC, and uses a private DNS (eg: tableau.extensions.company.local). The server works and the extensions page loads in a browser (albeit getting the 'insecure' flag in chrome as a self signed certificate is used).

My issue: Tableau Desktop will not allow me to use the extension, since it is 'not secure'.

Is there a way for Tableau Desktop (and server) to circumvent the need to have a fully fledged signed certificate from a trusted authority? I will only be using the extensions webserver for the extensions, on a private machine within a private DNS.

Any help, or advice would be appreciated.

For example, use the first day of the month but be able to show a string that is formatted the way you want ex: "January 2019".

I have a Data source which has more than 50,000 rows and the parameter not even ready to set configuration. It is showing "Loading..." only. I really need this parameter to work on but hopeless.

When I put this in a container with other filters with titles, I cannot align the titles. Should have the same setup as other parameter/filters.

Is there any way to change the dropdown dimensions so it looks in-line with other default Tableau dropdowns? Did you choose to make them larger for a reason? I actually prefer the larger size, but not next to a default dropdown.

When selecting the values from the filter then again go to that filter to select other values in dropdown shows only some values. basically filtering the values in the dropdown after a selection show only some values not all values.

It works very well before, but it's not able to pass parameters since this morning.
Should I download a new version of extension or anything to fix?
(Mine shows version 0.7.0 now)

Thanks!

Let end users choose the values they want and then hit apply to set values all at once.

Hello, i'm using this to act as a universal pagination for multiple sheets in a dashboard.
But when the filter changes and the max page changes, the parameter does not update to the new page number.

Hi,
This extension is great! it helped us to filter in a dynamic way using Level of details expression (Specifically using the parameter value in FIXED expression).
Thanks alot!
It worked good for a while but recently the following happened:

• The parameter drop down is visible in Tableau desktop:

• But, it's hidden when looking on the published dashboard. What
  you do see instead is a grey empty rectangle. See the following screenshot:

• When open Tableau Server ==>Settings ==> Extensions I get the following error:
  "An unexpected error occurred while processing your request. Try again.
  undefined" - see screenshot attached
  

Can you give an advice to handle it?
thanks

We have followed the steps in implementing the Data Driven parameters and updated the trex file.

But we are getting error when we tried to add the extension into Tableau desktop.

Extension error.docx

Hi @KeshiaRose ,
Thank you for developing such a awesome extension. I am using this extension to auto update the parameter on changing the backend data. I have enabled the option to include value '(All)' in the parameter list. But when I try to reload the extension it by default selects the first value from the list but not the value '(All)'.
Can you please guide me on how should I make the extension to select the value'(All)' by default?
Also, can you please guide me on the use of the 'Automatically reset values on load' option?

Regards,
Prasad Kulkarni

Hi,

Loving the extension - I'm using it to populate a list of dates that feed stored procedure params pulling in data for the vizzes the rest of the dashboard. Importantly it defaults to a 'Most Recent' date. When viewing the dashboard in Tableau Server, the page first loads the vizzes with the date that was Most Recent at time of upload (typically a few days out of date), then the extension populates, then the dashboard reloads with the new Most Recent date. This reload/repaint is about 40% of the load time, so I'd really like to try to reduce it.

Can you shed any light on what's happening here?
Perhaps it's standard Tableau caching behavior. If this is the case, then shortening my cache times might help, right?
Perhaps it's an order-of-operations thing? I want the extension to update ASAP and first, so other vizzes immediately have the date they need to get stored proc data. Any tips on how to prioritize the extension and its stored proc? I tried naming the sheet connected to the extension with a prefix of 'aaa' but it doesn't seem to do anything.

Thanks for the great extension!
-Matt

When running this on my mac, i had to change the build command in package.json to the following (since rd and move are not valid commands on mac osx)

"build": "react-scripts build && rm -R docs && cp -R build docs",

is there a way to make this build script work across platforms?

Hi- I am using the data driven parameter to default my dashboard to the latest date in my data set. The data driven parameter is working as expected, but the daily subscription email does not show the most recent value in the workbook.

It looks like the data driven parameter is triggered in tableau online when the URL refreshes and, I am assuming, a subscription does not refresh the URL so the latest date is not pulled into the dashboard before generating the subscription email.

Does anybody know of a workaround for this? Any help would be GREATLY appreciated!
Ali

When using the 'Use different field for display values' option, sorting does not occur on the new field but rather the original field.

The current release does not work on Tableau desktop. We have a sheet with a list of short strings and an open parameter that the extension should update - but the update only works when you reload the extension or if you allow for multi-selection and they use the apply button (if you choose one even it works with the apply button). The single select option does not work still. An old version works perfectly though, version 0.7.0.

Hi we are getting this error on random occasions we believe is related to the extension we are using in the dashboard:

The only thing I could find on the issue was this thread here: https://community.tableau.com/thread/296491
which doesn't really provide any solution to stopping the error from appearing.

Any additional information on preventing this error from occurring would be appreciated. Thanks

Your extension has filled an important role in a project that requires users to select from an updated list of accounts. It works amazingly well with small numbers of rows, but seems to take about 4 times as long every time the number of rows doubles. For example, 2500 rows takes 10 seconds; 5000 rows takes 45 seconds and 10000 rows takes 3 minutes (180 seconds). One of our clients has nearly 80000 rows which I estimate would take over 3 hours to load!

I haven't read your code; JavaScript and such are new to me and I'm afraid you are years ahead of me. Besides, if I managed to make changes myself I'd cut myself off from future enhancements that you might make.

Still, I suspect it is the sort which uses an O(n-squared) algorithm. In my case I'm using a custom Data Source using 'top(n)' and 'order by' such that the data is already sorted. Would it be possible to add a 'Don't Sort' option for sorting in your extension and do you think it might improve my load times?

Extension continuously shows "Loading" in IE11. Works appropriately in Chrome and Edge.

For example, sort sub-categories by the sum of sales.

Hi @KeshiaRose

I noticed that there is an error coming when I move from the Dashboard which has Extension to the other dashboard. It is happening only with IE ( I am using IE 11). There is no error if I open Dashboards with out the extension directly. In Chrome I did not notice it.
Then I removed extension and tested same and no error at all.
And the other Issue is Text Color change is also not working in IE, Showing only Black.

Could you please check it once.

I am getting error while importing the new version (where updates has been added to automatically update the parameter values) of Data Driven Extension into my Tableau.
I am getting the below error, can somebody help me if I am missing something here?

Hi,

Sorry if this is a bit out of the scope of this specific extension, but couldn't find any info online.

My company runs 3 Tableau Server environments, each with 3 nodes. If I want to install and host this extension locally for one of these environments, do I need to install and host on each node, or just one?

I'm operating at the edge of my knowledge with regards to hosting/serving, so apologies if my terminology is a bit off.

We have the extension in use for the same date parameter in multiple dashboards for selecting a month. We have found that the parameter value is not being consistently passed to subsequent dashboards.

Only the 'landing page' dashboard has the 'Refresh on Dashboard Load' option selected, with all others having no options selected, but it seems like the starting value of the extension is not being read from the parameter, but instead is refreshing to the last selected value for the specific dashboard.

Details of issue published to forum: https://community.tableau.com/thread/313370