Support Alerts

Tableau Sites are required to use Multi Factor Authentication and enforcement is coming soon. We have a special webinar dedicated to this topic that’s offered in all time zones. Please navigate here, and register for one of our live sessions.

Product release and download

Tableau Desktop 2018.3

Vi rekommenderar att du använder den senaste underhållsversionen, som innehåller ytterligare korrigeringar.

Download Tableau Desktop 2018.3 Ladda ner den senaste versionen (rekommenderas)

Ladda ned från en dator

Tableau Desktop är inte tillgänglig för mobila enheter. Logga in från en dator om du vill ladda ned.

Download Unavailable

The download file for this version has been removed due to the security issues currently identified in CVE-2021-44228 and CVE-2021-45046. In order to address these security issues, you must update to the newest version of your desired Tableau product. For more information please see the Knowledge Article, Apache Log4j2 vulnerability (Log4shell)

Resolved Issues

Problem-id Beskrivning

In some cases, opening a workbook would result in an error "Internal Error - An unexpected error occurred and the operation could not be completed" and in a LogicAssert error "Clip value out of range" in the DatePartValues.cpp file.


When a data source filter is applied, the extract history is not updated after an incremental refresh.


Some Japanese prefectures (三重 Mie, 京都 Kyoto, 和歌山 Wakayama, 埼玉 Saitama, 大分 Oita, 奈良 Nara, 富山 Toyama, 山口 Yamaguchi, 山梨 Yamanashi, 岐阜 Gifu, 岩手 Iwate, 新潟 Niigata, 熊本 Kumamoto, 神奈川 Kanagawa, 福井 Fukui, 秋田 Akita, 茨城 Ibaraki, 青森 Aomori, 香川 Kagawa, 高知 Kochi, 佐賀 Saga) were not recognized as geographic roles without the the suffix appended ( like "県” or "府”)


Maps using custom polygons were blank, distorted, or rendered as a single color box.


When you used a filter on a data source with a non-January fiscal year start, sometimes an "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed" error occurred.


Selecting Total Using > Server with an ASO cube resulted in a “value 'Server' not in enumeration” error.


Creating an extract in a remote shared folder using Tableau Desktop 2018.2 on a Mac failed with an "fcntl(): Operation not supported" error.


When using a cluster in a workbook, extract refreshes sometimes failed with the error "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed."


int64 field in OData sometimes rounded incorrectly.


When using Tableau Desktop with Microsoft Office IME 2010 Japanese, re-entering Japanese words do not convert them properly in the field name search. It looks like incremental auto-search is interrupting the IME character conversion and resulting in unintended characters appearing in search string.


When you connected to an Odata feed from a non-default namespace, an "Odata: Cannot find corresponding ComplexType" error occurred.


When doing a wildcard search on a pivoted field based on a .csv data source, a "collation mismatch" error sometimes occurred.


When you added description text to a story point, and then deselected the text object, you could not format the description again.


Using a calculated field containing a spatial geometry field and an failed conditional statement could result in an error: "unable to deduce expression type, use 'NULL::' to specify the type"


Updated province data for the Democratic Republic of the Congo.


Updated Turkish postcode data.


Many Thai vowel characters were not rendered correctly in Tableau Desktop.


After you refreshed an extract, saving the workbook would silently fail to retain the extract location if the extract was also open in another instance of Tableau Desktop, resulting in an "Extract not found" error upon reopening the workbook. There is now a warning for the failure and you are prompted to specify an alternate location to save the new extract data.


Updated Australian postcode data.


Updated German postcode data.


Updated German county data.


Sometimes, nested level of detail calculations in a workbook produced an "Error occurred communicating with the data source. No such column [Calculation_]." error message.


When trying to create an extract of Sybase ASE using a MAX() or Top N extract filter, the extract would fail.


When using the NOW() function with a live connection to Snowflake, Tableau followed the data source location time instead of the time configured on the data source server.

Hämta filer

Har du redan ett konto på

Logga in för att ladda ned dina filer

Logga in nu

Ingår med ditt konto på

De senaste produktuppdateringarna

Åtkomst till personanpassat innehåll

Åtkomst till låst innehåll med ett enda klick

Du hittar mer information på din My Tableau-sida

Skapa, ändra och dela visualiseringar i molnet.

Förbered, anslut och hantera din data var som helst.

Analysera tillsammans med ditt team.

Inkluderar Prep Builder och Data Management.

Behöver du ett konto?

Ladda ned dina filer genom att skapa ett konto för med formuläret nedan. Du får även åtkomst med ett klick till allt från låst innehåll på hela webbplatsen och framtida produktuppdateringar till anpassade erbjudanden som Tableau Blueprint-utvärderingen och mycket mer.




Mån, 29 Oktober, 2018

Installera Tableau Desktop

Planerar du att uppgradera?
Sida för Tableau Desktop-uppgradering