Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Qlik Community,
I'm having some trouble figuring out this problem:
In 2 of my visualizations I use the same dimension and sorting parameters, yet the sorting is different.
In attachment "qlik.png" you can see that the month November is slipping in between the others as "2017-Nov".
In attachment "qlik3.png" you can see the other visualization, where the sorting is correct.
Granted, the sorting is set to "auto" at the moment, yet the other options didn't make a lot of sense either.
The used dimension is described as follows:
=Year(floor([transactions.date])) & '-' & Month(floor([transactions.date]))
I have considered using the wildmatch function as a sorting expression, but that won't let my sort by year first.
Can anyone help me sort this out?
Don't know really know why, but this works
=MonthStart(Min({1}[transactions.date]))
Use this as your dimension
Date(MonthStart([transaction.date]), 'YYYY-MMM')
and then sort numerically
Hi Sunny,
nice to meet you here again.
I tried your solution, and it works in principle, but the formatting of the labels is off.
As you can see in the attachment it still uses the date produced by the MonthStart function.
Any hints?
PS: This is how my dimension looks like: "=Date(MonthStart([transactions.date]), 'YYYY-MMM')"
Edit: Seemingly also because of this change, there appears a useless scrollbar beneath the visualization. It does not disappear if I increase horizontal or vertical size of the visualization.
I guess continue using this as your dimension
=Year(floor([transactions.date])) & '-' & Month(floor([transactions.date]))
but sort using this expression
(MonthStart([transaction.date])
I tried that, but the original error reoccurred.
original error?
Well, the November entry is back between the others again, as described in the question description.
Would you be able to share a sample where we can see the issue?
Mocked up data will work as well... all that matters is that you can recreate the issue in a sample file
Well this took some time.
Tried to keep it as close to the actual data as possible without revealing anything important.