Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

when I click on Sort by property of a field, TE3 crashes #868

Closed
paolopedron opened this issue Mar 31, 2023 · 12 comments
Closed

when I click on Sort by property of a field, TE3 crashes #868

paolopedron opened this issue Mar 31, 2023 · 12 comments
Assignees
@DBojsen
Labels
feature: backlog A feature improvement has been added to the backlog feature: enhancement Request is a enchacement to existing feature

Comments

@paolopedron
Copy link

Describe the issue
In most of the tables of any data model, the click on "Sort By Column" property causes TE3 to crash.

** Which version are you currently using? **
Tabular Editor 3, version: Build 3.5.1.1425
Tabular Editor 3 edition: Enterprise

To Reproduce
Are you connected to SSAS/AAS/Power BI or working offline?
Connected

Steps to reproduce the behavior:

  1. Open a model
  2. Go to a table
  3. Select a field
  4. Go to Properties
  5. Select the "Sort By Column" property
  6. Try to place the cursor in the text box or to select a field with the drop-down arrow
  7. TE3 crashes

Expected behavior
A clear and concise description of what you expected to happen.
I expect to see a list of fields to choose from.

Screenshots
If applicable, add screenshots to help explain your problem.
image

image

Desktop (please complete the following information):

  • Windows version: Windows Server 2022 Datacenter Azure Edition

Additional context
Add any other context about the problem here.
@DBojsen
Copy link
Collaborator

DBojsen commented Mar 31, 2023 •
edited by otykier
Loading

Hi @paolopedron

We are unable to reproduce right now - could I ask you to answer below questions.

Does it happen regardless of which model you load, and which field you're working on?
Does the fields in question contain special characters?
Do you see the same issue if attempting from a different server/development machine?

As a workaround for now, you can mark the column and run this C# script:

Selected.Column.SortByColumn = SelectColumn(Selected.Table.Columns);

BR David - TE3 support

@DBojsen DBojsen added issue: awaiting reply More information is needed issue: needs reproducible example Unable to reproduce the issue from the provided description labels Mar 31, 2023
@DBojsen DBojsen self-assigned this Mar 31, 2023
@paolopedron
Copy link
Author

paolopedron commented Mar 31, 2023 via email

@otykier
Copy link
Collaborator

otykier commented Apr 2, 2023

Hi @paolopedron
GitHub doesn't support attaching images through e-mail, so if you attempted to add some screenshot to your previous reply, we can't see them. Could you go to the issue on GitHub: #868 and upload the screenshots there, please? Thank you.

@paolopedron
Copy link
Author

Please see the screenshots
pic1
pic2

@otykier
Copy link
Collaborator

otykier commented Apr 3, 2023

Thanks - we're looking into it. For now, please use the workaround described above, if you need to change the Sort By Column property.

@otykier otykier added issue: bug Confirmed as a bug in TE3 and removed issue: awaiting reply More information is needed issue: needs reproducible example Unable to reproduce the issue from the provided description labels Apr 3, 2023
@paolopedron
Copy link
Author

Dear Team, any news on this? Were you able to reproduce the error?

@DBojsen
Copy link
Collaborator

DBojsen commented Apr 17, 2023

Hi @paolopedron

We still have not been able to reproduce.
Have you had a chance to attempt the same change from a different windows machine?

BR David - TE3 Support

@paolopedron
Copy link
Author

paolopedron commented Apr 17, 2023 via email

@DBojsen
Copy link
Collaborator

DBojsen commented Apr 18, 2023 •
edited
Loading

Hi @paolopedron

In that case, would it be possible to uninstall and reinstall TE3 to see if this is caused by a faulty installation?

BR David - TE3 support

@edhans
Copy link

edhans commented May 2, 2023 •
edited
Loading

I have 3.6.0 and it is not crashing when I set the sort by column property, but I cannot save to the workspace after making the change. I get this:
image
The workaround script above doesn't help as it just sets the property. Same error when saving the model to the Premium workspace.

This is a small table, two fields, two rows. The Unit Type column is string, Sort By is Integer, and Sort By only has a 0 and 1 in it. Unit Type has two different string values.

@edhans
Copy link

edhans commented May 3, 2023

I get the same error with TE 2.18.0.
image

Is that column ID some sort of ID that isn't being properly associated with the Sort By column? The lineage tag is a standard GUID.

{10 minutes later}... Ok, figured it out. The "IsAvailableInMDX" was set to false. Set it to True on the Sort By field, and was able to set it.

The UI should help out here. Not sure how...
When I tried to set IsAvailableInMDX for Sort By back to False, I got this error:
image

It is just 2 records, so immaterial for performance, but BPA told me to change it.

I think at the very least, invalid fields (those with IsAvailableInMDX set to false should not show up in the Sort By field dropdown, but that just prevents the error. Doesn't explain why the field isn't there. Maybe add more text down here (yellow area) to explain that? Still somewhat hidden, but it would prevent guessing or thinking there was a bug.

"If you don't see the field in the dropdown for the Sort By Column property, make sure the IsAvailableInMDX property for the desired Sort By column is set to TRUE" - that assumes you hide the fields that aren't valid for Sort By in that dropdown.

@DBojsen DBojsen added feature: enhancement Request is a enchacement to existing feature feature: backlog A feature improvement has been added to the backlog and removed issue: bug Confirmed as a bug in TE3 labels May 3, 2023
@DBojsen
Copy link
Collaborator

DBojsen commented May 3, 2023

Hi @edhans

Thank yor for your hard work determining the root cause.
I have added an item to our backlog to display a warning if a column has a SortByColumn, which has IsAvailableInMDX set to false.

BR David - TE3 Support

@TabularEditor TabularEditor locked and limited conversation to collaborators Oct 12, 2023
@mlonsk mlonsk converted this issue into discussion #1032 Oct 12, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees

@DBojsen DBojsen

Labels
feature: backlog A feature improvement has been added to the backlog feature: enhancement Request is a enchacement to existing feature
Milestone
No milestone
Development

No branches or pull requests
4 participants
@otykier @DBojsen @edhans @paolopedron