Forum Discussion
(Another) Sort by another column problem
- Anonymous6 years ago
I believe I've solved this problem. It was caused by a relationship between my date table and a fact table. The relationship was between a calculated column in the latter that looked up a value from a column in the former. Power BI allowed it, but it seemed to affect the behaviour of reports built using the dataset.
Removing the relationship means I can perform the sort I need.
To recreate the relationship, I've calculated a table in the query that include only the columns I need and inserted this between to the two tables in my model.
Anonymous -
What is the error you received?
- ChrisMendoza6 years agoResident Rockstar
Anonymous -
You've identified this table as a 'Mark as Date Table' correct? Can you provide a sample?
- Anonymous6 years agoNot applicable
No, I haven't marked it as a date table. I don't need to use the time intelligence fucntions as my calendar has custom periods. I'd be happy to provide the csv but I don't have anywhere I can upload it that I can access as work.
- ChrisMendoza6 years agoResident Rockstar
Anonymous -
Are they not custom periods based off of sequential dates? Those dates become the sort order. Time Intelligence functions do not need to be utilized just by marking as a date table.
I built a custom period calendar table, marked as date table, and have had no issues with sorting. Possibly it is just the implementation you've chosen that is causing intermittent successes.