Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TOM doesn't show Calculation Item in error state when the expression is invalid #1217

Closed
edhans opened this issue Jan 11, 2024 · 2 comments
Closed
Assignees
Labels
issue: bug Confirmed as a bug in TE3

Comments

@edhans
Copy link

edhans commented Jan 11, 2024

Description

I entered a long expression into a Calculation Item, but missed a closing parenthesis. Long SWITCH() statement. I saved it and the TOM looked ok. Refreshed the viz on the thin report (model in service) and got a gray box.

Note that the DAX Formatter feature does recognize the expression is invalid, but even though this is saved, the TOM shows it is ok.

Tabular Editor 3 Version

3.13.0

Screenshots

image

Steps to Reproduce

Create a calculation item with an invalid expression, save the model and recalc the Calculation Group if necessary in the service, then try and format the expression. It won't format because it isn't valid, but the TOM shows it is ok.

Expected behavior

No response

Crash Report

No response

Windows Version

10

@edhans edhans added the template: issue Issue report created by user, needs to be triaged label Jan 11, 2024
@mlonsk mlonsk self-assigned this Jan 12, 2024
@mlonsk mlonsk added issue: under review Being looked into by TE team issue: bug Confirmed as a bug in TE3 and removed template: issue Issue report created by user, needs to be triaged issue: under review Being looked into by TE team labels Jan 12, 2024
@mlonsk
Copy link
Collaborator

mlonsk commented Jan 12, 2024

Hi @edhans

This is confirmed as a bug. Thank you for reporting, we will keep you updated when we have a timeline to share.

@otykier
Copy link
Collaborator

otykier commented Feb 20, 2024

This is now fixed in 3.14.0. Thanks for reporting!

@otykier otykier closed this as completed Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Confirmed as a bug in TE3
Development

No branches or pull requests

3 participants