SSAS Sort By Column Causing Data Cannot Display Visual Error

[daustin]

Power BI does not seem to understand SSAS attributes that have an order by attribute assigned to them.  When attempting to build a visual, it will X itself out and say that it cannot be displayed.  

Has anyone else encountered this issue?

[tk]

not solved..!

But we have found a workaround. The problem happens with not numeric fields that are bigger than varchar(50). We are changing the field length to less than 50 positions and the problem was solved.

[v-jiascu-msft]

Hi @daustin,

It seems ordering couldn't cause this problem. Could you please check the following?

1. Which visual did you use?

2. Did you connect to SSAS in "import" model or "connect live" model?

3. Did you add other resource to the model if you used "import"?

4. Did you use any measures?

With the information above, maybe I can reproduce the issue.

Best Regards!

Dale

[daustin]

Any visual is having the issue with my Store attribute, which has the OrderByAttribute property set.  Slicers, bar charts, donut charts, anything fails on this attribute only.  If I remove the OrderByAttribute value, it works fine.

I am using a live connection to the SSAS model.  No other data is being used outside of the SSAS model.  I have tried this using measures (charts) and without (slicer) and it is still the same issue.

[daustin]

More specific error details: 

Couldn't load the data for this visual.  The given key was not present in the data dictionary.

Feedback Type:
Frown (Error)

Timestamp:
2017-08-03T16:42:01.7151169Z

Local Time:
2017-08-03T12:42:01.7151169-04:00

Product Version:
2.48.4792.721 (PBIDesktop) (x64)

Release:
July, 2017

IE Version:
11.0.9600.18738

OS Version:
Microsoft Windows NT 6.1.7601 Service Pack 1 (x64 en-US)

CLR Version:
4.6.1 or later [Release Number = 394271]

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

Peak Working Set:
590 MB

Private Memory:
393 MB

Peak Virtual Memory:
3.76 GB

Error Message:
The given key was not present in the dictionary.

User ID:
3b9dc3de-afd8-4b7e-90c1-297edaa8a72a

Session ID:
eafdd4d0-7342-4284-8cd8-9991dbc26ed0

Telemetry Enabled:
True

AS Live Connection:
True

Performance Trace Logs:
C:\Users\xxx\AppData\Local\Microsoft\Power BI Desktop\PerformanceTraces.zip

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_EnableReportTheme
PBI_numericSlicerEnabled
PBI_SpanishLinguisticsEnabled
PBI_PbiServiceLiveConnect
PBI_daxTemplatesEnabled
CustomConnectors

Disabled DirectQuery Options:
PBI_DirectQuery_Unrestricted

Cloud:
GlobalCloud

Activity ID:
null

Time:
Thu Aug 03 2017 12:41:12 GMT-0400 (Eastern Daylight Time)

Error Code:
rsInternalError

OData Error Message:
An unexpected error occurred in Data Shape Query Translation.

DPI Scale:
100%

Supported Services:
Power BI

Formulas:

section Section1;

[daustin]

Still haven't figured it out.  I'll keep talking to myself here.

My time dimension sorts just fine and I don't know how to replicate that behavior.

[daustin · Accepted solution]

I could not get VARCHAR types to sort in my Store Dimension only in Power BI, but if I use Integers it works.  I was able to sort attributes in different dimensions using the VARCHAR type.  It wouldn't work in the Store Dimension even after rebuilding.  Integers it is.

[tk]

I have the same problem. Integer works okay but sorting with an attribute varchar is giving problems.