Issue with date ranges in selections reverting to "Earliest to Latest" on Q1 2024 release.
Several users reported an issue that when creating selections within FastStats which included a date variable and contained a selection using a Date Range,. They found that after making changes to the other parts of the selection and subsequently reviewing the date variable selection, the values within that range had changed from their selected values to a default of The Earliest Date to The Latest Date.
e.g.
The issue was caused by a date rule memory issue in the FastStats UI.
The solution is to:
1. Install a version of the FastStats Configurator version 13.24029.23 or later (this is contained within the Web Service.Zip file).
2. Use the Web Service within FastStats Configurator to upgrade the Client Binaries to version 1.1.24029.45 or later.
The Date Range entered will then be retained.
Related Articles
FastStats not showing most recent release on splash screen launchpage
When you run a FastStats Launcher (or FastStats local) then the log in page should show a list of features in the splash page to the right of the log-in panel: If this is not showing the release notes which correspond to the software version (you can ...Import a list of dates and URNs and run a selection to find the date in the system with the same URN and previous to the one in the list.
A client asked us for a method of importing a list of URNS and Dates, into an existing FastStats system, and then to suggest a method to compare the imported date to other dates for the same URN in order to then provide the previous date attached to ...Counting specific days \ day types between 2 dates.
A user asked it was possible to count the number of working (weekdays) between 2 dates. They had considered the function Datediff() within an expression but realised this simply counts the total number of days between 2 dates. Our suggestion was to ...Limits issue within FastStats
We’ve found and fixed an issue with the query component, where in rare situations we didn’t fully clear the limit properties between queries. This could cause a query limit clause to be mistakenly applied to a subsequent query. To apply this fix: ...One Per Aggregations in PeopleStage
One Per Aggregations in PeopleStage are useful when you want to campaign to a Person level but output transactional fields. For example, in our Holidays demo data, we have a Bookings table which is transactional to the Person table. We might want to ...