Tableau Desktop 2018.3

Tableau Desktop 2018.3

Tableau 2020.4 Prep Builder in the browser, spatial enhancements, and Resource Monitoring Tool for Linux. Start Tableau Desktop and enable debugging (Windows) Exit Tableau if it is already running on your computer. Open a Command Prompt window. Start Tableau using the following command. Replace with the version of Tableau you are using (for example, Tableau 2018.3). TableauDesktop-64bit-2018-3-29.exe: Patch Description: Tableau Desktop 2018.3 x64 (2018.3.29) Bulletin Id: TU-751: Bulletin Title: Updates for Tableau 10.3: Severity: Important: Location Path: TableauDesktop-64bit-2018-3-29.exe: Bulletin Summary: Updates for Tableau 10.3: Superceding Bulletin Id: None: Patch Release Date: Mar 24, 2021: Affected Product Information. Nov 20, 2018 In addition, the following entry is found in the Desktop or Server logs: index support is disabled. Tableau Desktop and Server 2018.3.0; Extract; Resolution Option 1 Upgrade to Tableau Desktop/Server 2018.3.1, or a newer version. Starting in version 10.3, you can also deactivate any perpetual (or subscription in version 2018.3 and later) product keys from the command line when uninstalling Tableau Desktop on Windows using the RECLAIMLICENSE=1 installer options.
Tableau Desktop 2018.3.3
See Full List On Tableau.com
Tableau Desktop 2018.3.1
Tableau Server 2018.3 Download
In this section
See also: Known Issues
Tableau 2021.1 UpdatesMarch 2021
You can now use Chrome version 80 and later to debug your dashboard extension in Tableau Desktop. If you are using Tableau 2021.1, or the latest maintenance releases of Tableau 2020.2, 2020.3, or 2020.4, you no longer need to use Chromium (version 79 or earlier) for debugging. For more information, see Debug Extensions in Tableau Desktop and Download the Chromium Browser.
If you plan to implement OAuth in your dashboard extension, you'll want to check out Add OAuth to Dashboard Extensions, and the OAuth sample (datadev-oauth-sign-in) on Glitch.
Because of browser changes in Tableau, dashboard extensions running with self-signed certificates (SSL) might not work in Tableau 2021.1, or in the most recent Tableau maintenance releases: 2020.2.7+, 2020.3.6+, and 2020.4.2+. For more information, see Known Issues.
Tableau Dashboard Extensions API version 1.4May 2020
Tableau Dashboard Extensions API library: tableau.extensions.1.4.0.js
(download or clone the Extensions API repository on GitHub). 
About this release:
To support the logical and physical tables introduced in Tableau 2020.2, the Tableau Dashboard Extensions API (version 1.4) provides new APIs and data structures. Use these new methods to get the underlying data from data sources and worksheets. The new methods replace getUnderlyingDataAsync. Starting in Tableau 2020.2, a data source could have multiple logical tables, and logical tables can contain one or more physical tables. If you have an existing extension that uses one of the deprecated methods to get underlying data, the method call could fail if the data source contains more than one logical table. You should update your extensions to use these new methods. The new methods are backward compatible with previous versions of Tableau.
InterfaceDeprecated method (v1.3 and earlier)New method (v1.4 and later)
Datasourcedatasource.getActiveTablesAsyncdatasource.getLogicalTablesAsync
Datasourcedatasource.getUnderlyingDataAsyncdatasource.getLogicalTableDataAsync
WorksheetNot Applicableworksheet.getUnderlyingTablesAsync
Worksheetworksheet.getUnderlyingDataAsyncworksheet.getUnderlyingTableDataAsync
To support the data model, the API also includes the LogicalTable object that has two properties: caption and id. The caption is the name of the logical table as it appears in Tableau.
For more information about getting underlying data from data sources and worksheets, see Get Data from the Dashboard.
For information about the data model, see The Tableau Data Model.
DataValue now has a nativeValue member. This member represents the raw native value as a JavaScript type, which is one of string, number, boolean, or Date object. Note that special values are returned as null. The nativeValue helps simplify error checking as all values will either be their native type value or null. The nativeValue exists for ALLDataValue objects, including those returned from parameters, filters, selections, and underlying or summary data. Dates values are in UTC.
Added documentation for the clearSelectedMarksAsync() method, which clears the selected marks in the current worksheet.
Bugs fixed in this release:
Range filters now work correctly when the minimum or maximum values are equal to zero (0). Previously, calls to the applyRangeFilterAsync() method would ignore the RangeFilterOptions if the min or max properties were equal to zero (0).
The isVisible attribute for dashboard zones is now set properly to true or false when the extension is initialized.
The setZoneVisibilityAsync() method now supports ES6 map objects for the zoneVisibilityMap parameter.
Tableau Sandboxed Extensions Development EnvironmentSeptember 2019
Sandboxed Extensions are Tableau dashboard extensions that are not permitted to make external network requests. Available for testing with Tableau 2019.3. Fully supported in Tableau 2019.4.
The Extensions API SDK provides a local development environment that replicates the Tableau Hosting Cloud Service for Sandboxed Extensions. You can test your Sandboxed extensions locally with the same sandbox policies before submitting the extension to Tableau for publication. See Create and Test Sandboxed Extensions and Publish Sandboxed Extensions.
Extensions API library v1.3July 2019
Tableau Extensions API library: tableau.extensions.1.3.0.js
(download or clone the Extensions API repository on GitHub) 
About this release:
The Extensions API library version 1.3 (tableau.extensions.1.3.0.js) is backward compatible with previous releases of the library.
Now available: Extensions API type definitions and new TypeScript samples. The latest release provides the TypeScript type definitions so that you can author your extension using TypeScript. See Use TypeScript with the Extensions API and TypeScript Sample Extensions on GitHub.
New all-values-selected property for categorical filters (filter.isAllSelected). You can use this new property to determine when all values of categorical filters are selected. The isAllSelected property is a Boolean and returns True or False. Prior to this release, there was no way to tell if all values of categorical filters were selected. The filter.appliedValues method returns empty array when (All) is selected, so there is no way to use that method to determine if all values are selected or if no values are selected. The isAllSelected property is available starting with Tableau 2019.2 and the Extensions API library version 1.3 (tableau.extensions.1.3.0.js).
Extensions API library v1.2April 2019
Tableau Extensions API library: tableau.extensions.1.2.0.js
(download or clone the Extensions API repository on GitHub) 
About this release:
The Extensions API library version 1.2 (tableau.extensions.1.2.0.js) is backward compatible with previous releases of the library. You can use the Extensions API library version 1.2 for extensions on Tableau 2018.2 and later. The library contains logic to handle any necessary conversions for the supported version of Tableau the extension is running in. For the best experience, you should always use the latest version of the library with the extensions you create.
The names of the Extension API library files have changed. The hypens (-) have been removed from the file name (was tableau-extensions-*, now tableau.extensions.*). Starting with the 1.2 library, the names of the library files are as follows:
Note If you have previously been referencing tableau-extensions-1.latest.js in your code, you will need to use the new naming convention when you upgrade to the 1.2 library (tableau.extensions.1.latest.js).
Bugs fixed in this release:
Fixed in the Extensions API library 1.2, the type of DataValue.value is now the raw native value as a JavaScript type, rather than always defaulting to String. A DataValue.value can be one of the following JavaScript types: String, Number, Boolean, or Date. A DataValue is returned as a property of a DataTable in methods, such as getSummaryDataAsync() or getUnderlyingDataAsync(). Note that special values, regardless of type, are always returned as String values surrounded by percent signs, such as %null%, or %no-access%. 
Important! If your code depended on the type of DataValue.value always being a String, that code will now break with this fix.
The environment.apiVersion property now correctly reports the version of the Extensions API library that the extension is using.
The documentation for the selectMarksByValueAsync method has been corrected. If you are calling the method, be sure to specify the complete namespace for the SelectionUpdateType enum that is passed to the method as the updateType parameter. For example, use tableau.SelectionUpdateType.Replace, to replace the currently selected marks with the values you specify in the method call.
Tableau 2019.1February 2019
Tableau Extensions API library: tableau-extensions-1.1.0.js
(download or clone the Extensions API repository on GitHub) 
Download Tableau Desktop 2019.1 or Tableau Server 2019.1
Changes in this release:
Upgrade to the Chromium browser, which allows modern web technologies to be used with dashboard extensions (HTML 5, CSS, native ES6 support). Tableau 2019.1 now uses Qt 5.10, The Qt WebEngine is based upon Chromium 61.0.3163.99, with additional security fixes from newer versions. With this update, you no longer need to download and use a specific version of Chromium (47.0.2526.0) to debug dashboard extensions on Tableau Desktop. You can now debug extensions in Tableau Desktop using Chrome.
Show and hide capabilities for extensions (now you see it, now you don't). For more information, see Show and Hide Objects in the Dashboard.
Bugs fixed in this release:
Select dropdown fixed on Macintosh. (TFSID 758234)
The applyRangeFilterAsync method allows full range of options, and doesn't break when a user selects 'all'. (TFSID 766488)
Fixed 'Access is denied' error encountered when switching from a sheet containing an extension to any other sheet on a tabbed workbook on server (fixed in Tableau 2019.1, 2018.3.2, 2018.2.5).
Full support for IE11 now starts in 2018.2.3, 2018.2.3.
Fixed in Tableau Desktop 2019.1: Extension API synchronization issue.
 In previous version of Tableau Desktop (2018.2, 2018.3), the execution of extension API calls was not properly synchronized with longer running actions. These issues would most often occur with a worksheet that took multiple seconds to refresh. This could manifest itself in various ways: The intializeAsync method could return the promise before the dashboard was properly loaded in Tableau.
A FilterChanged event could be triggered before the data was actually refreshed. As a result, calls to getSummaryDataAsync could return the data before the filter was changed.
If an extension API was called from a setInterval or similar function, while other actions were going on, Tableau could occasionally crash.
Customers who upgrade to Tableau Desktop 2019.1 will not have these synchronization issues with extensions.
Tableau 2018.3

Interface	Deprecated method (v1.3 and earlier)	New method (v1.4 and later)
`Datasource`	`datasource.getActiveTablesAsync`	`datasource.getLogicalTablesAsync`
`Datasource`	`datasource.getUnderlyingDataAsync`	`datasource.getLogicalTableDataAsync`
`Worksheet`	Not Applicable	`worksheet.getUnderlyingTablesAsync`
`Worksheet`	`worksheet.getUnderlyingDataAsync`	`worksheet.getUnderlyingTableDataAsync`

November 2018
Tableau Extensions API library: tableau-extensions-1.0.0.jsNo change for this release
(download or clone the Extensions API repository on GitHub)
Download Tableau Desktop 2018.3 or Tableau Server 2018.3
New in this release:
Updated documentation. Getting Started, Create a 'Hello World' Dashboard Extension, 
Debugging Extensions on Tableau Desktop, Debugging Extensions on Tableau Server and Tableau Online, Error Codes and Error Handling for Extensions.
TC18October 2018
Tableau Extensions API library: tableau-extensions-1.0.0.jsNo change for this release
New in this release:
Use the Design Guidelines for Dashboard Extensions as a roadmap for designing great dashboard extensions.
Create extensions with the look-and-feel of Tableau, using the Tableau UI, a React component library.
New and updated documentation. See Publishing a Dashboard Extension. 
For information about developing and running an extension locally on http://localhost and testing it on Tableau Online or Tableau Server (over HTTPS), see Load and view localhost content on sites that use secure connections.
Bugs fixed in this release:
Extensions are now fully supported in Internet Explorer (IE 11).
Tableau 2018.2July 2018
Release of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-1.0.0.js
(download or clone the Extensions API repository on GitHub)
Download Tableau Desktop 2018.2 or Tableau Server 2018.2
Bugs fixed in this release:
Extensions are now fully supported in Internet Explorer (IE 11).
Tableau 2018.2 (Beta 2)June 4, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.16.0.js
Download Tableau Desktop, Tableau Server from Tableau 2018.2 Beta
Changes in this release:
XML Schema: This release introduces two changes to the XML schema for the extensions manifest file (.trex). If you have an existing .trex file, you need to make a couple of corrections. 
The first change is to the URL of the extensions namespace (xmlns). The URL is now www.tableau.com... instead of wwww.tableau.com...
The second change is to the author's web site. This link to your web site must now be over HTTPS for security. This link to your web site will become the Get Support link in the About dialog box for your extension. Users will be able to click the link to get to the help page that you provide.
Extensions settings and permissions in Tableau Server 
Server administrators can manage dashboard extensions on the Settings > Extensions tab (for each site and for the server). By default, only extensions that do not require full data access are allowed to run. HTTPS is required. Server administrators can enable dashboard extensions that are trusted to access full data by adding them to a safe list for a site. Server administrators can control whether or not the users will see prompts (asking them to allow the extension to access data) when users are adding an extension to a dashboard, or when they are interacting with a view that has an extension. For more information, see Dashboard Extensions in Tableau Server
The About dialog box. Users can now find out about an extension in the dashboard by selecting the layout container and then clicking About from the More Options menu. Information from the extension manifest file (.trex) is used to populate a dialog box. (Note that the dialog box you see might look slightly different from this example.)
Tableau 2018.2 (Beta 1)April 26, 2018
Download Tableau Desktop, Tableau Server from Tableau 2018.2 Beta

Developer Preview (0.12.8)April 13, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.12.8.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Changes in this release:
This release of Tableau introduces a minor change in the workbook format that affects extensions. If you saved a workbook with an extension using an earlier version of Tableau, and then open the workbook with this current Tableau release, the workbook will open, but it will not have the extension. You will have to add the extension back in using the latest release of Tableau.
Bugs fixed in this release:
Certain keyboard shortcuts were intercepted by Tableau and not passed on to the extension. This is now fixed, with the excecption of cmd + V on Mac, which will be fixed in a later release. (Issues #76)
Calls to getSummaryDataAsync() or getUnderlyingDataAsync() would not return the correct data types for the columns. Column property datatype returned string for all columns, regardless of actual data type of column.
Web Authoring would throw an exception when an extension is added.
XSD validation of minApiVersion accepted only single digit version numbers (for example, 0.12 would fail).
Permissions denied error message would disappear after the dashboard zone was reloaded.
Developer Preview (0.12.8)April 13, 2018

Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.12.8.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Changes in this release:
This release of Tableau introduces a minor change in the workbook format that affects extensions. If you saved a workbook with an extension using an earlier version of Tableau, and then open the workbook with this current Tableau release, the workbook will open, but it will not have the extension. You will have to add the extension back in using the latest release of Tableau.
Bugs fixed in this release:
Certain keyboard shortcuts were intercepted by Tableau and not passed on to the extension. This is now fixed, with the excecption of cmd + V on Mac, which will be fixed in a later release. (Issues #76)
Calls to getSummaryDataAsync() or getUnderlyingDataAsync() would not return the correct data types for the columns. Column property datatype returned string for all columns, regardless of actual data type of column.
Web Authoring would throw an exception when an extension is added.
XSD validation of minApiVersion accepted only single digit version numbers (for example, 0.12 would fail).
Permissions denied error message would disappear after the dashboard zone was reloaded.
Developer Preview (0.12.7)March 28, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.12.7.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Updated in this release:
Extensions API library goes to 12 (one better than 11). The library has been refactored to be smaller, faster, lighter.
Dashboard authors and users of your extension can decide whether to allow the extension to run or not. When users add an extension that can access the underlying data in a dashboard, they now see a prompt that lets them allow the extension to run. In addition, when someone opens a dashboard that contains extensions, they see a dialog box that lists information about all the extensions in the dashboard, and a prompt to allow the extensions to run. For more information, see Accessing Underlying Data
Starting with the 0.12.7 release, the Extensions API library supports versioning. Future versions of Tableau will be able to run extensions that use earlier versions of the Extensions API library (0.12.7 and later). You will no longer need to roll the version number of the library in your extension at every release just to enable it to run in Tableau. For example, a dashboard extension that uses the Extensions API 0.12.7 library should run in a future release of Tableau without modification. And Tableau will provide a meaningful error message if you try to run an extension that requires a later version of the Extensions API library than the version of the API that a particular Tableau release supports. For example, if the extension uses the 0.14.0 library but the version of Tableau only supports an earlier version (0.12.7), users of the extension will see a message informing them that they need a later version of Tableau.
Bug fixes:
Canceling extensions selection causes error
Parameters (Desktop): Tableau crashes if you add a filter based off of a parameter to a dashboard
Saving and opening a workbook that has an extension throws error
Parameter Changed Notification not working on server
Extension dialog box height and width are reversed
Developer Preview (0.10.0)February 28, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.10.0.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Updates in this release:
New configure feature, which allows you to register a custom JavaScript callback for a context menu item in the extension zone. See Adding a configuration dialog box and the UINamespace sample.
A fix for a problem that existed in the 0.9.0 release that caused extension initialization to break on Tableau Server.
For other changes with this release, see Known Issues on the Extensions API Developer Preview site.
Adding a configuration menu item

November 2018
Tableau Extensions API library: tableau-extensions-1.0.0.jsNo change for this release
(download or clone the Extensions API repository on GitHub)
Download Tableau Desktop 2018.3 or Tableau Server 2018.3
New in this release:
Updated documentation. Getting Started, Create a 'Hello World' Dashboard Extension, 
Debugging Extensions on Tableau Desktop, Debugging Extensions on Tableau Server and Tableau Online, Error Codes and Error Handling for Extensions.
TC18October 2018
Tableau Extensions API library: tableau-extensions-1.0.0.jsNo change for this release
New in this release:
Use the Design Guidelines for Dashboard Extensions as a roadmap for designing great dashboard extensions.
Create extensions with the look-and-feel of Tableau, using the Tableau UI, a React component library.
New and updated documentation. See Publishing a Dashboard Extension. 
For information about developing and running an extension locally on http://localhost and testing it on Tableau Online or Tableau Server (over HTTPS), see Load and view localhost content on sites that use secure connections.
Bugs fixed in this release:
Extensions are now fully supported in Internet Explorer (IE 11).
Tableau 2018.2July 2018
Release of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-1.0.0.js
(download or clone the Extensions API repository on GitHub)
Download Tableau Desktop 2018.2 or Tableau Server 2018.2
Bugs fixed in this release:
Extensions are now fully supported in Internet Explorer (IE 11).
Tableau 2018.2 (Beta 2)June 4, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.16.0.js
Download Tableau Desktop, Tableau Server from Tableau 2018.2 Beta
Changes in this release:
XML Schema: This release introduces two changes to the XML schema for the extensions manifest file (.trex). If you have an existing .trex file, you need to make a couple of corrections. 
The first change is to the URL of the extensions namespace (xmlns). The URL is now www.tableau.com... instead of wwww.tableau.com...
The second change is to the author's web site. This link to your web site must now be over HTTPS for security. This link to your web site will become the Get Support link in the About dialog box for your extension. Users will be able to click the link to get to the help page that you provide.
Extensions settings and permissions in Tableau Server 
Server administrators can manage dashboard extensions on the Settings > Extensions tab (for each site and for the server). By default, only extensions that do not require full data access are allowed to run. HTTPS is required. Server administrators can enable dashboard extensions that are trusted to access full data by adding them to a safe list for a site. Server administrators can control whether or not the users will see prompts (asking them to allow the extension to access data) when users are adding an extension to a dashboard, or when they are interacting with a view that has an extension. For more information, see Dashboard Extensions in Tableau Server
The About dialog box. Users can now find out about an extension in the dashboard by selecting the layout container and then clicking About from the More Options menu. Information from the extension manifest file (.trex) is used to populate a dialog box. (Note that the dialog box you see might look slightly different from this example.)
Tableau 2018.2 (Beta 1)April 26, 2018
Download Tableau Desktop, Tableau Server from Tableau 2018.2 Beta
Developer Preview (0.12.8)April 13, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.12.8.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Changes in this release:
This release of Tableau introduces a minor change in the workbook format that affects extensions. If you saved a workbook with an extension using an earlier version of Tableau, and then open the workbook with this current Tableau release, the workbook will open, but it will not have the extension. You will have to add the extension back in using the latest release of Tableau.
Bugs fixed in this release:
Certain keyboard shortcuts were intercepted by Tableau and not passed on to the extension. This is now fixed, with the excecption of cmd + V on Mac, which will be fixed in a later release. (Issues #76)
Calls to getSummaryDataAsync() or getUnderlyingDataAsync() would not return the correct data types for the columns. Column property datatype returned string for all columns, regardless of actual data type of column.
Web Authoring would throw an exception when an extension is added.
XSD validation of minApiVersion accepted only single digit version numbers (for example, 0.12 would fail).
Permissions denied error message would disappear after the dashboard zone was reloaded.
Developer Preview (0.12.8)April 13, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.12.8.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Changes in this release:
This release of Tableau introduces a minor change in the workbook format that affects extensions. If you saved a workbook with an extension using an earlier version of Tableau, and then open the workbook with this current Tableau release, the workbook will open, but it will not have the extension. You will have to add the extension back in using the latest release of Tableau.
Bugs fixed in this release:
Certain keyboard shortcuts were intercepted by Tableau and not passed on to the extension. This is now fixed, with the excecption of cmd + V on Mac, which will be fixed in a later release. (Issues #76)
Calls to getSummaryDataAsync() or getUnderlyingDataAsync() would not return the correct data types for the columns. Column property datatype returned string for all columns, regardless of actual data type of column.
Web Authoring would throw an exception when an extension is added.
XSD validation of minApiVersion accepted only single digit version numbers (for example, 0.12 would fail).
Permissions denied error message would disappear after the dashboard zone was reloaded.
Developer Preview (0.12.7)March 28, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.12.7.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Updated in this release:
Extensions API library goes to 12 (one better than 11). The library has been refactored to be smaller, faster, lighter.
Dashboard authors and users of your extension can decide whether to allow the extension to run or not. When users add an extension that can access the underlying data in a dashboard, they now see a prompt that lets them allow the extension to run. In addition, when someone opens a dashboard that contains extensions, they see a dialog box that lists information about all the extensions in the dashboard, and a prompt to allow the extensions to run. For more information, see Accessing Underlying Data
Starting with the 0.12.7 release, the Extensions API library supports versioning. Future versions of Tableau will be able to run extensions that use earlier versions of the Extensions API library (0.12.7 and later). You will no longer need to roll the version number of the library in your extension at every release just to enable it to run in Tableau. For example, a dashboard extension that uses the Extensions API 0.12.7 library should run in a future release of Tableau without modification. And Tableau will provide a meaningful error message if you try to run an extension that requires a later version of the Extensions API library than the version of the API that a particular Tableau release supports. For example, if the extension uses the 0.14.0 library but the version of Tableau only supports an earlier version (0.12.7), users of the extension will see a message informing them that they need a later version of Tableau.
Bug fixes:
Canceling extensions selection causes error
Parameters (Desktop): Tableau crashes if you add a filter based off of a parameter to a dashboard
Saving and opening a workbook that has an extension throws error
Parameter Changed Notification not working on server
Extension dialog box height and width are reversed
Developer Preview (0.10.0)February 28, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.10.0.js
Tableau Desktop, Tableau Server (from Extensions API Developer Preview)
Updates in this release:
New configure feature, which allows you to register a custom JavaScript callback for a context menu item in the extension zone. See Adding a configuration dialog box and the UINamespace sample.
A fix for a problem that existed in the 0.9.0 release that caused extension initialization to break on Tableau Server.
For other changes with this release, see Known Issues on the Extensions API Developer Preview site.
Adding a configuration menu itemYou can use a new callback function option to initializeAsync() as a way to create a configuration option that opens a window or dialog box for your extension. To do this you first add the context-menu option to the extensions manifest file (.trex).
Add  to the .trex file
Create a configuration function
When you initialize an extension, you can now pass an optional contextMenuCallbacks object to the initializeAsync() function. This object maps a special ID or key (which must be 'configure') to a function you create. The function you create, in conjunction with adding a  item to the manifest, adds a new Configure… context menu item to the zone of the extension inside a dashboard. When the user clicks the context menu item, the configuration function you specified is executed.
For example, you could use the UI namespace and have the configuration function call the displayDialogAsync() function to create a dialog box that can be used to change settings for the extension. The parent (or initial window) for your extension, might have the following JavaScript code.
To better understand how to use the context menu, and to see it in action, check out the updated UINamespace sample.
Developer Preview (0.9.0)February 14, 2018
Update of the Tableau Extensions API
Tableau Extensions API library: tableau-extensions-0.9.0.js
Tableau Desktop (from Extensions API Developer Preview)
Updates in this release:
Updates to the UI namespaceThis preview release introduces more options for the UI namespace. You can now control the initial sizing (height, width) of a modal dialog box (or popup). The modal dialog itself is an extension. Using the displayDialogAsync() and closeDialog() methods you can pass payloads between the calling extension and the extension running in the modal dialog box. For an example of how you can use the UI namespace to create a configuration dialog box, see the UINamespace sample. The sample also shows how to use the settings event to capture the new configuration. The sample source code has extensive comments that describe how to use these new features in the Extensions API.
New sample: UINamespace
Permissions added to access full dataTo access the underlying data along with information about the data source, the extension must declare that it requires full data access in the extension manifest file (.trex).
An extension requires full data access, if the extension uses any of the following four APIs:
Worksheet.getUnderlyingDataAsync()
Datasource.getUnderlyingDataAsync()
Datasource.getActiveTablesAsync()
Datasource.getConnectionSummariesAsync()
If you use any of these APIs, you need to add a  element to the manifest file (.trex) and specify full data permission. The XML looks like the following:
The  element must be added under  in the manifest file. For a complete description of the manifest, see the Tableau Extensions Manifest File.
If full data is not declared in the manifest file, and the extensions calls one of the APIs that accesses any underlying data or data source information, the API call fails. In addition, an error is written to the Tableau log file (log.txt). If you are debugging the extension with the Chromium web browser, an error is reported the console pane. The error message would look similar to the following:
Error codes for extensionsErrors that are returned from the Extensions API are custom Tableau Error objects that extends the standard JavaScript error object.
The Extensions API wraps the standard error object with an errorCode property. Any time you encounter an error when you are developing your extension, you can look at this errorCode to determine the cause. See Error Codes.
For an example of how to handle error conditions, see the UINamepace sample. The sample shows how you could handle the error condition that occurs if a user dismisses a modal dialog box (DialogClosedByUser). The following snippet illustrates this pattern:
Developer Preview (0.8.0)January 10, 2017
Update of the Tableau Extensions API.
Tableau Extensions API library: tableau-extensions-0.8.0.js
Tableau Desktop 10.5 RC, Tableau Server 10.5 (from Extensions API Developer Preview)
Tableau Desktop 2018.3.3New desktop authoring experience
You no longer need to place the .trex file for the extension in a predetermined folder, you now do the following:
In the dashboard, under Objects on the left, select Extension and drag it to the dashboard sheet on the right. The Select an Extension dialog box appears.
The first time you open the dialog box to add an extension, you will see a link to Choose an Extension. Click the link and browse to the directory where you have the .trex file. Subsequently, when you drag the Extension on the dashboard, the dialog box shows you the most recently used list, choose from the list, or click Browse to select another extension.
New UI namespace
You can now launch a new modal dialog using the function: tableau.extensions.ui.displayDialogAsync(dialonExtensionURL).
The URL you want to load (dialonExtensionURL) will be an extension itself.
The extension in the dialog will have full access to the extensions API. When ready to close to the dialog, from the dialog extension you can call tableau.extensions.ui.closeDialog(string). See the documentation for details.
Note that the UI namespace is work is still in progress and has some upcoming additions. Stay tuned for more.
HTTPS and security
For information about the HTTPS requirements for extensions, see Security and Tableau Extensions
Remote Debugging
Due to changes in this release, remote debugging does not work as expected in Tableau Desktop. To enable debugging, you must add the --remote-debugging-port=8696 option to the command used to start Tableau. The easiest way to do this is to open the Tableau shortcut on the Start menu. Open the file location of the Tableau shortcut. Right-click the Tableau shortcut and click Properties. In the Target text box, append the remote debugging option to the command. Do not enclose the option in quotation marks.
For information about debugging extensions, see Remote Debugging of JavaScript and HTML.
Developer Preview (0.7.0)November 29, 2017
Update of the Tableau Extensions API.
Tableau Extensions API library: tableau-extensions-0.7.0.js
Tableau Desktop 10.5 RC, Tableau Server 10.5 (from Extensions API Developer Preview)
Breaking change
Schema change - Updated XSD file for the dashboard extensions manifest file (.trex). If you have an existing extension, you must update the .trex file to follow the new schema. There is a script you can run that converts the manifest file for you. Or you can manually make the changes. For more information about the manifest, see Tableau Extension Manifest File. You can download the manifest conversion script from the Extensions API Developer Preview on https://prerelease.tableau.com.
Existing workbooks - if you have an existing workbook that uses a dashboard extension, you will not be able to open it with this (0.7.0) release. To get around this issue, update the manifest file (.trex), update your extension to use tableau-extensions-0.7.0.js, and then open a new workbook and re-create the dashboard.
New features
Tableau Server. You can publish dashboards containing extensions and run them on Tableau Server. You can download a version of Tableau Server 10.5 that supports dashboard extensions from the Extensions API Developer Preview on https://prerelease.tableau.com.
Security - Your dashboard extension must use an HTTPS connection. If you are using localhost for development, you can still use HTTP.
Sharing dashboards - the dashboard extension now gets saved with the workbook, so you can share your workbooks that use the extension with others.
New method DataSource.getConnectionSummariesAsync gets a summary object for each underlying connection in a data source.
New method DataSource.getActiveTablesAsync gets all tables used to create the data source (what you would see in the join canvas).
Logging - You can view dashboard extension activity in Tableau log files. Tableau records extension events that you can use to troubleshoot registration errors and command execution. See Use Log files to Troubleshoot Dashboard Extensions.
Bug fixes
The Worksheet.clearFiltersAsync method no longer removes filters from your worksheets, but properly resets the filters to a default state.
The name of the selected dashboard extension now appears instead of 'other' in the dashboard Layout pane.
Developer Preview (0.6.0)Oct 10, 2017
See Full List On Tableau.comInitial release of the Tableau Extensions API. Provides support for dashboard extensions.
Tableau Desktop 2018.3.1Tableau Extensions API library: tableau-extensions-0.6.0.js
Tableau Desktop 10.5 beta
IssueTableau Server 2018.3 DownloadViews on Tableau Server eventually fail to load. This may also result in a 502 error after approximately 30 minutes.
Checking the vizqlserver logs will show the log entries with the action begin-vql-session-save-workbook-for-checkpoint as the final entry for an Apache request id. 
The Apache request id in the following example is XFRVQc82Wz2e6RrSxr@vpwAAAOU:
{'ts':'2019-02-01T14:18:42.009','pid':7436,'tid':'f484','sev':'info','req':'XFRVQc82Wz2e6RrSxr@vpwAAAOU','sess':'BE8A7BF9510B4ED187819C5F5C73DAEA-1:3','k':'begin-vql-session-checkpoint-workbook-xml','l':{},'a':{'depth':4,'id':'K11HZQm4UYdJwFo1JL4AOk','name':'vql-session-checkpoint-workbook-xml','root':'Ohu1ryXYE43I8hqZP8jrxe','sponsor':'C4gSIVGcUXKJkX7XDPenNn'}
{'ts':'2019-02-01T14:18:42.009','pid':7436,'tid':'f484','sev':'info','req':'XFRVQc82Wz2e6RrSxr@vpwAAAOU','sess':'BE8A7BF9510B4ED187819C5F5C73DAEA-1:3','k':'begin-vql-session-save-workbook-for-checkpoint','l':{},'a':{'depth':5,'id':'GIUZ6mgjUT0JfWTQ4Sdnd5','name':'vql-session-save-workbook-for-checkpoint','root':'Ohu1ryXYE43I8hqZP8jrxe','sponsor':'K11HZQm4UYdJwFo1JL4AOk'}