Forum Discussion
Do date paramters work properly?
Hi all,
I'm facing a problem with date parameters.
Issue:
When I use filter with date paramters, the results are slightly different everytime, even though the data set being used is the same.
Does anyone know what cause this issue and ways to solve it?
If that helps, the purpose to use date paramters is to create reports regarding a certain date period. The report creating process is as follows.
Report createing process:
- retrive data from databese. => always the same results
- filter by date period in such a way as to
- directrly use date value => always the same results
- designate via date parameters => different everytime!
- use 'slicer' in the report => different everytime!
In terms of datatype in parameters setting, it occurs no matter whether I use 'date' or 'date+timezone'.
Thanks in advance.
Best Regards,
Mario
- Anonymous9 years ago
I see. mario_japan thank you for the update. I'm glad to know that it i ssolved.
If you are no longer facing an issue, could you accept a solution for the topic, so it can be registered?
Thank you, and best of luck in the future.
Best,
Martin
6 Replies
- mario_japanRegular Visitor
Hi all,
I've checked my data in detail, and I found that the circumstance of the data are somehow completely unreasonable as the following.
- almost 70% of data are filtered correctly
- around 20% of data are missing (they are supposed to be unfiltered)
- about 10% of data are dupulicated (there are no reason the data are duplicated, just by filtering)
If someone noticed the same issues, please let me know.
- AnonymousNot applicable
Hi mario_japan
Could you attach the pbix file or sample data, so I can replicate your issue? I've never encountered this before, and I've found date slicers to be completely reliable.
Best,
Martin
- mario_japanRegular Visitor
Hi Anonymous,
Thanks for the message.
I'm now trying to create a test data so that you can check the case.
However, it seems that the matter doesn't occur as long as local data like Excel file is used (whereas it happens everytime when data from Microsoft SQL Server are retrieved).
It can't be a problem with the number of records, because it happened when I tried reduce the number of records from SQL Server to around less than 20,000.
I'll keep investigating and I'd like to let you know when I find something.
Regards,
Mario
- AnonymousNot applicable
I agree with you; It's probably not the number of records. The only possibility I see is if your data is somehow different from SQL to Excel.
I'd still very much like to check this out, so if you can send a test data set anytime, I would appreciate it. I want to make sure I don't encounter your issue, if that makes sense.
Keep us posted!
Best,
Martin