Skip to content

Commit

Permalink
added known issues section (#155)
Browse files Browse the repository at this point in the history
  • Loading branch information
otykier authored Feb 28, 2025
1 parent 03e3e7a commit aa5fbc0
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions te3/other/release-notes/3_20_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,7 @@ Check out our [release blog](https://blog.tabulareditor.com/2025/02/21/tabular-e
- We've made several improvements to our **Diagram View**. Most importantly, it now renders much faster, especially when many tables/relationships are present. But there are also several visual tweaks.
- We've improved the C# auto-complete feature, so that it now shows only items that are relevant for the current target. For example, if you type `Selected.Column.DataType = `, the listbox will now only show the valid [`DataType` enum values](https://learn.microsoft.com/en-us/dotnet/api/microsoft.analysisservices.tabular.datatype?view=analysisservices-dotnet#fields). Moreover, if the same type exists in different namespaces, we now show the namespace in a parenthesis, to disambiguate the items in the list.
- Updated AMO/TOM to the latest version [19.88.3](https://www.nuget.org/packages/Microsoft.AnalysisServices/).
- We have added auto-complete support to the new DAX scalar inspection functions, [`ISINT64`](https://dax.guide/isint64), [`ISBOOLEAN`](https://dax.guide/isboolean), [`ISDOUBLE`](https://dax.guide/isboolean), [`ISDECIMAL`](https://dax.guide/isdecimal), [`ISDATETIME`](https://dax.guide/isdatetime), [`ISSTRING`](https://dax.guide/isstring), and [`ISNUMERIC`](https://dax.guide/isnumeric).

## Bugfixes in 3.20.0

Expand All @@ -82,6 +83,12 @@ Check out our [release blog](https://blog.tabulareditor.com/2025/02/21/tabular-e
> [!IMPORTANT]
> Due to technical limitations, previous versions of TE3 might sometimes allow **Business Edition** license holders to connect to Power BI Premium / Fabric Capacity workspaces, even though [this is not allowed per the Business Edition license terms](xref:editions). If you are facing issues connecting to the Power BI XMLA endpoint after upgrading to 3.20.0, please reach out to [[email protected]](mailto:[email protected]) so we can assist you in finding a suitable solution going forward.
## Known issues in 3.20.0

- The Semantic Analyzer doesn't correctly detect relationship activations with `USERELATIONSHIP` when there are only inactive relationships between two tables.
- The Semantic Analyzer doesn't always infer the correct data type for the column returned by the [`GENERATESERIES`](https://dax.guide/generateseries) function.
- The new **Diagram view** does not correctly indicate bi-directional relationships.

---
## Coming from Tabular Editor 2.x?

Expand Down

0 comments on commit aa5fbc0

Please sign in to comment.