Hey @Jesse if you come across the link, that would be fantastic. I probably have it book marked but searching my book marks is becoming harder!!!
I’ve managed to filter reports for clients using in built date filter (manually typed) for as long as they wanted. A remember a client asked he wanted quarterly period reports back dating the first ever work period started. So using the the first column to date before first ever period(just to be safe) and second column inserted 3 months later and it successfully filtered it. What I did find is that any typos in the columns will not make the filter work. Had to be exactly same as it shows originally for it to have worked for me.
Edit: but I have to admit at the beginning it was a little confusing to work out as there was no text to state start date and end date next to the columns . and it doesn’t quite have the selection of dates like you have in the ticket screen, nor the recently built date picker that emre made a tutorial about
Giday Shivan
Are you talking about the filters as I have shown in my first image first post above? Interesting there obviously is a set of Rules that the control uses - it is just guessing what they are.
While implementing work periods I intended to create reports that validates each other. I mean when user creates a work period report; payments, sales and cash amounts should match with other reports. Using work periods properly ensures all tickets closed and all transactions submitted. We report sales and payments separately for good reasons and allowing reporting from the middle of a work period may lead to unmatching numbers and that instantly makes people to think SambaPOS deleting tickets or missing payments. When I explain that people always say “staff forgeting closing work period” well… these staff also forgets closing latest tickets and these tickets closes on next day by morning staff. So more or less you’ll have tickets closed on next day. Obeying work periods while reporting solves that. Even they close work period in the morning and start another one SambaPOS automatically process them as yesterday’s tickets as it checks start and end of work periods. You may not be aware of it but it really really solves lots of reporting issues. Tell your customers to use work periods and you’ll never deal with unmatching numbers in reports.
Yep. If its the first screenshot your talking about then yes. When I change the start date in exact format to a different date regardless of how long ago the work period dates back to, and put an end date, it actually generates that report and the report does show exactly the dates I’ve specified. Also having a really long work period… Let’s say you started one today and didn’t end till 10 days later… Then you try to filter within that 10 day period, it will only show that particular work period… Since filter checks the date you entered, and puts it against the date of the nearest work period for that period…
Example… I started a work period on the 1-7-2016 and end it on 10-7-2016… If I try to search a period from 1-7-16 to 5-7-16 it will show the work period of 1-7-16 to 10-7-16 since that’s the only record it has…
Hence the importance emre is emphasizing of getting workers and people to start and end work periods according to working days… For test purposes though, it works exactly same way as live machine… So if you wanted a more accurate reading you’d have to start and end work periods accordingly…
The other thing is no matter how many work periods you have within a month, if you put a start and end date, it will pile all the work periods within the period of time you specified and add them together.
If you have a work period started on day 1 and end it on day 2 then start another, the only accurate way to get the reading is by filtering start date to day one and ending in day 2. I hope I’m making sense
Also Paul. I just checked your work periods in the second screenshot. Noticed you started one in may 21 and ended June 19. Then made another in June 19 then ended June 19. Then made another from June 19 to possibly right now as I don’t see an end date. So if you let’s say filter your start date to 15 may and end date let’s say 10 of June. Since 15 is closer to 21 of may, it will filter 21- may. But if you do 4- may to let’s say 26 may. It would show 4 may to 21 may because that’s the closest work period it found. If you do 4 may to jun 19 then it should filter it properly. I think. I did some tests to confirm this when had a few clients calling up and saying the work period report showing inaccurate results… Only to find out that it was because they were opening a work period and closing it the next day. So I filtered start to that original day and filtered end date to second date and it actually gave an accurate reading. Then I taught them to make sure work periods are closed when shop is closed, rather then just before they leave which is around 1am every night 
@Shivan I made few regarding changes on latest beta. Let me know if it works fine for your case.
Thanks Guys - some good tips I will enforce on site! Appreciate all the comments.
@emre are you talking about the calendar or date elector for report filters or the color picker I mentioned in a tutorial?
Hi emre. I checked the calender in tickets menu and its working beautifully with latest update. You reckon you could apply the same calender to reports menu also for filtering? It works fine, but from a user perspective, highlighting the start and end filter, then bringing up keyboard, then typing the date and making sure formatting is correct , then making sure the dates are correct by checking windows calender or another calender source can be a bit much just for filtering. (From my perspective I think its fine and can live with it, but I had a few client comment on finding it a bit tricky to filter since they assume date filtering should be straight forward quick and easy.)
That would be also possibly removing the possibility of bad formatting issues, and possible typing corrections when using inbuilt keyboard on a touch screen