Page tree
Skip to end of metadata
Go to start of metadata


Release 2.2.3 - 09/12/2020

Find below a list of changes for this release:

  • Bugfixes
    • Fixed the error message that shows up when a dataset is no longer found.
  • Improved SAML configuration.

Release 2.2.2 - 02/09/2020

Find below a list of changes for this release:

  • Bugfixes
    • Fixed a bug related to changing the name of a worksheet, where it was not being possible to update the configuration.
    • Fixed a bug that was preventing users logged in with SSO to fail the first attempt at log in Write-Back
  • Added support for SAML from ADFS.

Release 2.2.1 - 29/09/2020

Find below a list of changes for this release:

  • Bugfixes
    • Fixed a bug that prevented Write-Back from creating configuration tables in Amazon Redshift.
    • Fixed some visual bugs that were impacting UX in Firefox.
    • Fixed conditional expression preventing comparison between Source Fields and Custom Fields.
  • Improved conditional editor user experience.
  • Improved the error message when there are no valid Source Fields in the worksheet.
  • Improved detection of changes in source fields data types when attempting to add data.

Release 2.2.0 - 14/09/2020

Find below a list of changes with this release:

  • Security
    • We have added support for SAML and Open ID as Single Sign On (SSO) mechanisms. Together with Kerberos which was already supported Write-Back nows cover the most common SSO mechanisms supported by Tableau Server.  More information here.
    • Improved documentation to establish secured connections to SQL Server. 
  • Unique entry datasets
    • It is now possible to configure datasets that only allow one entry per combination of source fields. This configuration can be used to force a 1 to 1 relationship with your data and have the screen pre-polulated whenever there is already an entry. 
    • More information here.
  • Field Conditions 
    • Fields can now be hidden on the form based on previous fields values. An expression that hides or shows the field can be defined making it even more flexible to cope with specific business requirements. More information here.
  • Dynamic pre-defined fields
    • Pre-defined fields (drop down) can now be populated based on Tableau parameters making the entries easier to maintain or even dynamic on the latest Tableau versions that support this type of parameter. More information here.
  • UI/UX Improvements. 
    • Fields can now be ordered on the standard form giving more flexibility when editing an existing dataset. More information here.
    • Users are notified when editing an entry on the tabular form and the corresponding group is collapsed.
  • Under the hood bug fixes and improvements

Release 2.1.5 - 29/09/2020

Find below a list of changes with this release:

  • Bugfixes
    • Fixed a bug that prevented Write-Back from creating configuration tables in Amazon Redshift.

Release 2.1.4 - 09/09/2020

Fix of minor bugs and improvements.

  • Improved LDAP configuration and fixed compatibility with Active Directory.
  • Fixed a bug that prevented submitting simultaneously a large number of entries when using Oracle database.
  • Fixed a bug that prevented deleting numbers in the main form when editing data.

Release 2.1.3 - 20/07/2020

Find below a list of changes with this release. There are some minor breaking changes with the configuration, check the Upgrade Manual#UpgradingfromRelease2.1.2toRelease2.1.3.

  • Fixed a bug with where users could not use ldap authentication method to authenticate with AD.
  • Removed - activedirectory from the authentication methods available since it can be replaced with the ldap option.
  • FIxed a bug when using themes, where the color of the input fields on the append data forms were not consistent.

Release 2.1.2 - 29/06/2020

Find below a list of changes with this release:

  • Improved installer user experience.
  • Improved color calculations when using themes.
  • Fixed a bug that was causing issues with Oracle databases.
  • Fixed a bug that was preventing data editing with Snowflake databases.
  • Fixed an issue that was occasionally preventing adding data when the source fields were reversed.
  • Fixed other minor bugs and under the hood improvements and optimization.

Release 2.1.1 - 17/06/2020

Find below a list of changes with this release:

  • Fixed a bug that prevented submitting and editing data when there were %null% values on Tableau and improved error handling for the Tableau forecasting model.
  • Fixed an issue that was causing the login pop-up to show in the data sources panel, now if you login with an already configured extension, the pop-up will no longer show up in the data sources panel.

Release 2.1.0 - 08/06/2020

Find below a list of changes with this release:

  • Themes
    • It is now possible to customize the looks of Write-Back to fit the colors of your dashboard.
    • It's also possible to change the text label and color of the Write-Back Add Data button. 
    • You can find more about this here.
  • UI/UX Improvements
    • It's now easier and more secure to change or edit the source fields from the worksheet with a new and intuitive drop-down that lets you select the desired source fields.
      • When editing a configuration to add or rename source fields, the behaviour is now more consistent and you will be able to do so without losing data.
      • More about this here.
  • Selecting a mark is no longer mandatory
    • It is now possible to configure the extension so you don't have to select a mark before adding data. Useful for scenarios where input is not about a particular mark.
      • More about this here.
  • Boolean Support
    • Write-Back is now able to have source fields from Tableau that are boolean.
  • Under the hood bug fixes and improvements

Release 2.0.2 - 13/05/2020

Find below a list of changes with this release:

  • Bugfixes
    • Fixed a bug that was caused by having %null% values from tableau source data, where it prevented the users to add data.
    • Fixed a bug where attempting to change the option to refresh the dashboard when editing a dataset would not work in PostgreSQL.
  • UI Improvements and fixes
    • Numeric values that come from a text field are no longer formatted. It was happening that if a field was a text but had numeric values, these values were being formated. Example, field Year, type text, value 2020: was being formatted as 2.020. This will only happen for numeric fields now.

Release 2.0.1 - 13/04/2020

Find below a list of changes with this release:

  • Bugfixes
    • Fixed a bug where when using a reverse proxy, the extension might block with a redirect. We added a configuration to specify the domain which is visible to the users and to where the redirect will happen. Find more on this here.
    • Fixed a bug for Postgres that when attempting to insert numbers in a text column (usually due to a source field) the timeline would not refresh with the new information.
    • When configuring for the first time, there were some scenarios where the source fields would not reload after clicking the button.
  • UI Improvements and Fixes

    • Removed leading 'x' in the time custom field for Firefox
    • Consistency between section titles
    • Consistency between table colors when editing data in Tabular View

Release 2.0 - 03/04/2020

This release had the goal to provide support to insert data in a tabular form "a-like" Microsoft Excel, making Write-Back much more suitable for forecasting use cases. With this version, we also included support for extension sites. This option allows you to configure different persistence and authentication options inside the same application, by using different trex files. Find more about it here.

Find below a list of changes with this release:

  • Forecasting
    • Users can now configure Write-Back to display a table that is build using input fields and source fields
    • Table supports copy paste from Excel
  • Sites
    • Write-Back users can be segregated by sites each having its own database and authentication options
  • Improved extension usability:
    • Auto-refresh dashboard option, when on will refresh the dashboard after data submission
    • Mandatory fields, it is now possible to define which fields are mandatory both on form and tabular format
  • Authentication methods
    • You can now use LDAP servers to authenticate, not only Active Directory.
  • Security:
    • We now allow the option of ciphering your database password with our writeback-encrypt util. Move over to this section to find more about this util.
  • Load existing datasets
    • We allow loading existing datasets and than used them of a different dashboard or submit as a new one. 
  • Under the hood bugfixes and UI adjustments

Release 1.2.6 - 13/04/2020


  • Fixed a bug for Postgres that when attempting to insert numbers in a text column (usually due to a source field) the timeline would not refresh with the new information.

UI Improvements

  • Removed leading 'x' in the time custom field for Firefox

Release 1.2.4 - 27/02/2020


  • Fixed a bug where you could not connect to some Amazon Redshift schemas.
  • Fixed a bug where sometimes text fields would show as dates in the timeline.


  • Some minor under the hood improvements to column renaming and licensing.

Release 1.2.3 - 10/02/2020


  • UI
    • the date-time in the timeline is now formatted accordingly to your browser settings (24h or 12h format).


  • Fixed a bug where the date-time value inserted by a user, was being saved and then showed in UTC time instead of the absolute value inserted.

Release 1.2.2 - 30/01/2020

Bugfixes (critical):

  • Fixed a bug where the extension would not work in Tableau Server when using Tableau Server or InMemory authentication.

Release 1.2.1 - 24/01/2020

Improved datetime field submission. 

  • It is now possible to submit a date without setting an hour.
    • Default hour in this scenario is 00:00

Release 1.2 - 21/01/2020

This release had the goal to support Hyper Files as another possible persistence storing type. Meanwhile, we also have released an installer for a quick installation (you can find it here!). This installer sets up a ready to use set-up with a Tomcat with the extension, and a Postgres database where the data is inserted too. It also provides the proper trex file so you can start writing back your data!

Find below a list of changes with this release:

  • Support for Hyper Files!
    • This feature is still in Beta mode since the API support from Tableau is also something very recent.
  • Improved extension usability:
    • Login should only be prompted once: when you drag the extension to the dashboard canvas. After that, you can authenticate when you try to configure the screen or add data.
    • You can now delete all the custom fields in the configuration screen
  • Authentication methods
    • You can now specify a site to authenticate to when using Tableau Server authentication.
  • Database connections
    • When configuring the connection to a database in the config.yml file, the schema is now specified there as a parameter. 
  • UI adjustments
    • The size of the pills on the configuration screen has been decreased to match the size of the ones in the add data screen.
    • The names of the pills on the add data screen were not shortening appropriately.
  • Date and time as a new custom field type
    • Now, when setting up a dataset you can create fields with the type "date and time"
  • Added reload button next to the source fields when configuring a dataset allowing to restore removed fields or update the source fields if the worksheet has new ones.
  • Under the hood bugfixes

Release 1.1 - 31/08/2019 

This release had the goal to support additional database engines and add the possibility to authenticate with the Tableau Server user credentials. We also started working towards easing the installation experience of the extension for users.

As such here is what changed:

  • Support for additional database engines
    • PostgresSQL
    • SQLServer
    • Snowflake
    • Amazon Redshift
    • Oracle
  • New authentication method
    • You can now configure the extension to allow using the Tableau Server credentials as an authentication option (see how here).
  • Improved extension usability
    • You can now use Enter key to submit forms.
    • Improved the login mechanic so it does not prompt with every page refresh.
  • UI adjustments
    • Fields are now shown in the order they were inserted in the configuration.
    • Removed the grey line that was always at the top of the extension screens.
  • Bugfixing
    • Fixed a bug where the scrollbars would not work properly and the marks and other UI information would sometimes overlap while using the extension on Chrome (this was due to an update to the browser).
    • Fixed a bug where when using MySQL server, installed under a "non-standard" timezone, it would stop the application from starting up properly.

We also made some under the hood improvements to the internal mechanics of the application.

Known Limitations

Language Settings

Currently, the application must be configured and used always in the same language. This is due to the way Tableau translates some fields (usually generated ones like latitude/longitude, SUM, AGG, etc.) and because of that and to avoid issues while using the extension, we recommend using the same language throughout the whole usage.

Handling Date Relationships 

When using the extension you might come across the need to use a discrete date part as a business key between your dataset and existing data. When that is the case it might happen that the field format might not be the same, this is something that as of now we cannot control on the extension as we don't have access to additional field information such as whether it is a date or not. 

The solution for this is to:

  1. Create a new field where the date format matches the value on the dataset
    1. Format the date as a number, for instance using this formula for a month INT(DATEPART('month',[Analytical Date]))
  2. Create a custom relationship based on this new field for data blending

Hang dropdown options

You might notice that when configuring the extension if you open the options to choose a worksheet, leave it open and move the window around, the dropdown options will not follow the window. This is an issue from Tableau and we are in close contact with them in order to fix this. Do not worry though, since it will not affect the usage of the screen.

Timezone for Dates

Has of now all dates submitted don't have a timezone defined this means a single timezone should be agreed and users should do the conversion before entering the values. We have an improvement for this issue on the roadmap.  

Worksheet limitations

  • Tableau forecasting model

When using Tableau forecast model, due to the way that the Tableau API sends the data from the worksheet, some values can show up inconsistent or null. For the same field there are different values (normal and forecast) and it is not possible to distinguish them on Write-Back and ensure data is correctly added.

  • Multiple types of marks

Due to the way the Tableau API send information, Write-Back cannot properly work when you have multiple types of marks on the same worksheet using the same field. It can happen that the same fields will have different values for each mark, or even, each mark can have a different set of fields.

  • High volume of marks

If you want to use the form to add data with the option of selecting marks please do so without any limitation, however, if you do not want to select marks on the form or use the tabular screen please limit this configuration to sheets with up to 1000 marks on the visualization (shapes, bars, lines etc). In these usage scenarios we need to process all data and therefore beyond this value you might notice a decrease in performance. 

Login while configuring

If you drag the extension and do not finish the configuration process for a dataset, and you go to the data sources tab on Tableau to interact with the data, you might face a Write-Back login pop-up. This happens because Tableau is refreshing the dashboard when something changes within the datasources, and refreshing the datasources will make the extensions to reload causing in it to lose the session. Currently, we do not have a consistent solution to this issue. We recommend in these cases to delete the extension from the dashboard (if you do not configure before changing the tab) and drag again when all alterations to the data source have been done.

  • No labels