Issues & Known Limitations

Important Issues

This is the list of important limitations that are either being solved by the development team or are being addressed by Tableau: 

HTTP/2 Zero-Day Vulnerability 

We are aware of the recently HTTP/2 Zero-Day Vulnerability (CVE-2023-44487) and Write-Back is not affected by this vulnerability

More info: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-44487

Starting on Write-Back 4.1, a proxy server is now included alongside the installation, so, by default, Write-Back is automatically protected against this type of attack, including this one.

More on this here: https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html 

Springboot Vulnerability

We are aware of the recently disclosed Springboot vulnerability (CVE-2022-22965) and Write-Back is not affected by this vulnerability

More info: https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement

Log4j Vulnerability Fixed

We are aware of the recently disclosed Apache Log4j2 vulnerability (CVE-2021-44228) and we have already provided fixes for Write-Back 3.1 and 3.2 available on Support & Resources

Please ensure you upgrade to latest versions. 

Blank Screen on Tableau Server

If you are experiencing the extension staying blank on Tableau Server, this is a known issue from Tableau and they already provided a fix for it.

The fix has been applied to Tableau online in January and to Tableau Server in:

2021.4.3
2021.3.7
2021.2.8
2021.1.11

For more info: https://github.com/tableau/extensions-api/issues/449

Write-Back Frozen on Tableau Desktop

We have detected an issue with Tableau Desktop 2021 that will make Write-Back appear to be frozen and it can happen when navigating between data sources and worksheets or simply duplicating a dashboard.
This is affecting all dashboard extensions and Tableau is already aware of this issue.

For the moment, as a workaround, resizing the dashboard should "unfreeze" the extension and make it go back to normal.

Using Special Characters

We have detected an issue with Tableau Desktop 2020.4.2 which prevents using special characters that are inputted with ALT GR such as '{', '[', ']', '}', therefore this makes it so that to write conditional fields, you have to copy and paste the character from outside of the extension first.

The same issue was found from 2020.2.7 onwards and 2020.3.6 as well.

UPDATE: Tableau has informed us that this is an issue on their side and they are working on it.


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

Hanged 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

As of now, all dates submitted with the Write-Back data and time field 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.  Dates created automatically by Write-Back, for instance for auditing purposes, are stored on the server timezone and UTC.

Worksheet limitations

  • Tableau forecasting model

When using the 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.

You can read more about Tableau forecast models here

  • Multiple types of marks

Due to the way the Tableau API sends 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 data sources, and refreshing the data sources 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 it before changing the tab) and drag again when all alterations to the data source have been done.