Changes were applied to improve security. See ADV-058 in Security Bulletins for more details.
解決済みの問題
| 問題 ID | 説明 |
|---|---|
|
1153617
|
"Flow execution error: Failure parsing AQL - LogicAssert itrColumns != inputQueryColumns.end()" could occur when running a flow. |
|
1152115
|
CEILING() function could return incorrect results when using a scalar or a constant as the argument. |
|
1189154
|
A system error would sometimes occur when running the sample flow. |
|
1139220
|
The CEILING() function would sometimes return inconsistent results and also varied from Tableau Desktop. |
|
1163430
|
When running a flow that contains a pivot step, an error would sometimes display, "Failure parsing AQL: No such column {[field]}." |
|
1177414
|
The command line option to run a flow containing a TabPy script would sometimes display an error, "The Tableau Python (TabPy) server configuration is required. Enter a valid server configuration, then try again." |
|
1176110
|
Published data sources would sometimes not be displayed in the Connections pane to search for data. The message would display, "Error: The server encountered an error. Try again." |
|
1172224
|
A "collation mismatch" error could occur when running a flow with Microsoft Sql Server that contained a union and a join. |
|
1169229
|
When using the command line option in 2020.3, Java warning messages could occur when publishing output. |
|
1180432
|
It would not be possible to complete the Analytics Extensions Connection sign-in when the "Require SSL" checkbox was also marked and a valid SSL certificate was designated trying to access TabPy or RServe. |
|
1164374
|
When the command line is used to run a flow, an "errorlevel" of 0 would return even if the command failed in some versions. |
|
1162297
|
The user interface could become unresponsive when trying to copy and paste steps by "Ctrl+c" and "Ctrl+v". |
|
1161566
|
On Macintosh OS, a CSV file with a Japanese file name could not be read. |
|
1137333
|
When running a flow using an incremental refresh of Salesforce data, an error could occur stating "No such function ISNULL that takes arguments of type (datetime)." |
|
1131883
|
A flow execution error could occur after joining an extract and an Excel file, "No such column [Item Name-1]." |
|
1130438
|
The output step after a Left Only join could produce more rows than expected. |
|
1115348
|
An error would sometimes display when a pivot is performed, "Query Text Limit of 67108864 Bytes Exceeded." |
|
1169565
|
2020.3.3 以降、ユーザーフローの既存の高度な不連続の値フィルタリング、またはグループ化されたステップで作成された新しいフローでは、変更を確認・編集するための注釈がプロファイルカードに表示されない。左側の変更内容ペインを使用するか、上部のフロー ペインから高度な不連続の値フィルター注釈/変更を行うと回避できる。 |