Labels

• content: bpa

  Discussions about Best Practice Analyser
• content: data modeling

  examples and use cases for data modeling in Tabular Editor
• content: data source - databricks

  Importing data using databrics connector
• content: data source - oracle

  Using data from Oracle connector
• content: data source - snowflake

  Using data from Snowflake
• content: data source microsoft

  Topic concerns importing data from SQL server & Synapse
• content: dax

  DAX-related topics, such as syntax, functions etc.
• content: DAX Debugger

  Discussions on the use of the DAX Debugger in TE3
• content: devops

  Discussions regarding devops topics such as source control, deployment, testing of semantic models
• content: Direct Lake

  Topic on Direct Lake semantic models
• content: documentation

  Improvements or additions to documentation
• content: fabric

  Topics surrounding sematic models in Fabric
• content: power bi

  Discussions on Power BI topics
• content: query data

  topics on using TE3 to show data such as in DAX queries and Pivot Grid
• content: script assistance

  Help on C# scripting
• content: ssas/ass

  Discussions on SQL Server Analysis Services or Azure Analysis Services
• content: te license

  Topics on how the different license types of TE3 function.
• content: te3 ui
• feature: backlog

  A feature improvement has been added to the backlog
• feature: enhancement

  Request is a enchacement to existing feature
• feature: implemented

  The feature or enhancement is implemented in TE3
• feature: new

  Request is a new feature for Tabular Editor 3
• feature: out of scope

  the feature request is out of scope for Tabular Editor 3
• feature: roadmap

  These features have been added to the TE3 roadmap
• important
• issue: as engine/TOM

  Issue is caused by a limitation of the AS engine or the TOM client libraries
• issue: awaiting reply

  More information is needed
• issue: bug

  Confirmed as a bug in TE3
• issue: critical

  issue that has severe impact on the core functionality with no workaround
• issue: duplicate

  This issue already exists