If you set the MinDate on an UltraDateTimeEditor to a date that is today or in the past and then type in a date that is before the MinDate, the control clears the date (desired outcome). If you set a MinDate that is in the future and type in a date that is before the MinDate value, the control acts oddly.
Example
MinDate = 1/29/2014
Type in = 1/1/2014
Tab out of the control
Date control shows 1/1/2020
After some trial and error, it appears that the control is taking the first two spaces in the year (2014) and treating it like a 2-digit version of the year (20).
If you type in 1/1/1500, you get 1/1/2015. If you type in 1/1/1900 you get 1/1/2019.
Is this a known issue (I couldn't find anything on it)? Is there a workaround that allows both the limiting of the dates on the dropdown, but also won't result in the odd behavior when a user tries to type a date in?
I made a quick test using version 12.1 with the latest available service release - 12.1.20121.2135 and I could confirm that the issue is fixed. Please try to upgrade to latest available service release of version 12.1 or to one of latest versions (for example 13.1 or 13.2) where the issue is fixed.
Let me know if you have any questions
Related
I have one query can somebody please tell how to show Latest date in a date format
So basically, I want to show the latest date selected by default and if the user wants to select other dates they can change manually but the latest date should be in a date format
Date = IF('Query'[Date] = MAX('Q'[Date]), "Latest Date", FORMAT('Query'[Date], "MM-DD-YYYY"))
Please help to show the latest date in a date format
eg: MM-DD-YYYY
First of all, unless you use a static value like "Latest Date" as you have done in the column above, you will not be able to set the slicer to the latest date. However, you can have your report behave as though the latest date were selected if nothing is selected.
Based on your formula, I am assuming that the table Query holds the static latest date of the model and that the table Q is your calendar table.
Create these measures:
Pivot Date = MAX(Query[Date])
Earliest Selected Date = IF(ISFILTERED(Q[Date]),MIN(Q[Date]),[Pivot Date])
Latest Selected Date = IF(ISFILTERED(Q[Date]),MAX(Q[Date]),[Pivot Date])
Now the hard part is you need to write all your measures to use the date range defined by Earliest and Latest Selected instead of just leaving it up to the slicer to control the dates. This allows you to control what's displayed when nothing is selected.
ExampleMeasure =
var start_date = [Earliest Selected Date]
var end_date = [Latest Selected Date]
return
CALCULATE([Some Measure], removefilters(q[date]), q[date] >= start_date, q[date] <= end_date)
One of the drawbacks of this approach is that you may be depending on your slicer to show the user which dates are selected. To overcome that, add an unobtrusive visual that shows the dates in use. I like to use a Multi Row Card for this and place it in the top right corner of every page. I include these measures: Available From, Available to, Selected From and Selected To. That way viewers know how much data is in the report overall, and they know what's selected at this time. Placing this in the same place on every page in every report is an excellent practice as your viewers will become habituated to consulting this spot for date info.
Finally, I want to point out that you could implement this logic with calculation groups, and that is how I would do it in one of my own reports. Doing so would eliminate the need to modify all the measures you already have, but it would introduce a number of complexities. Calculation Groups have a big learning curve, so you need to be prepared for that journey. The alternative I have suggested will be quicker than getting up to speed on Calculation Groups. However, you should learn how to use them. I highly recommend everything at sqlbi.com on this topic. They have an excellent search tool on the site to find all their content related to Calculation Groups.
We updated apex to version 21.2.
Now we are having issue with datepicker component. When we select any date up to the 28th of the month, the date is correct in the component. But for dates greater than 29, the dates are wrong.
For example, if I choose the date 29/03 becomes 01/03, if I choose 30/03 it becomes 02/03.
The date format choose is DD/MM/YYYY.
Any ideas?
[For example, when a choose 30/03 (march)][1]
[1]: https://i.stack.imgur.com/eiNY6.png
it turns like 02/03
This is a bug introduced in the 21.2.2 PSE caused by changes to the underlying date parser & formatter because of other bugs in this area.
It has been fixed in patch 21.2.3.
c.f. https://twitter.com/JKaschuba/status/1487556202242400260
I would like to be able to have a slider on my PowerBI report which is set to the previous months range, but allow the user to extend this range if they want to.
I have a lookup table which has the previous years dates in. I am new to PowerBI so am unsure how to go about this.
At the moment the slider is defaulting as the min and max in the table. I want to have those as options, but when opening the report, the default is the previous month start and end date.
I am using the web based version and not the desktop version. I am unable to use the desktop version for this report.
This is what I am currently getting.
this is what I want it to look like, with the option to expand the slider to show a wider date range.
In my report, my date dropdown slicer looks like this when the report first loads:
I want it to display without all the extra time and timezone nonsense like it does when I manually select one of the boxes after the report loads:
Does anyone know why this happens or how to fix it?
Edit: Here's a minimal .pbix example: Link to File
I'm on the August 2018 version now, and it seems to me that this issue has been fixed.
At least I'm not able to reproduce it.
With a dataset like below, a Line Chart and a regular Slicer, I get this:
Date,Value
2017-01-12,1
2017-01-13,4
2017-01-14,2
2017-01-15,4
2017-01-16,2
2017-01-17,2
2017-01-18,2
2017-01-19,5
2017-01-20,5
2017-01-21,5
2017-01-22,5
2017-01-23,6
2017-01-24,3
2017-01-25,6
2017-01-26,6
2017-01-27,5
2017-01-28,8
2017-01-29,4
2017-01-30,2
The slicing details (the All part in Date All) can be turned off by setting Filter Restatement under Slicer Header to Off. Maybe that would have solved the issue?
Please note that I've ignored the date hierarchies in both the Line Chart and the Slicer:
As a suggestion, you might want to try creating a new Column using the FORMAT function.
This is something I often do to provide a more human readable date for my slicer.
EG:
DisplayDate = Format([SomeDateField], "ddd d mmm yyyy" )
Once done - you will want to select the column - then SORT by your original date column. Otherwise you may get some odd results ;)
I'm writing a program in c++/cli visual studio 2010 and I don't know how to set a specific date into my datetime picker.
I also want to know how do I set the default day to today, so you can't go to dates that has already passed.
Use Value property to set the current date/time, and MinDate to set the earliest date that can be selected.
dateTimePicker1->MinDate = DateTime::Today;