DATE PARAMETER WITH 'DATE FROM' RETURNS ERROR: 'ENTERED DATE IS NOT IN RANGE
(Doc ID 2645950.1)
Last updated on MARCH 18, 2020
Applies to:BI Publisher (formerly XML Publisher) - Version 12.2 and later
Information in this document applies to any platform.
- Navigate to any data model
- Create the date report parameter and select the data format string as dd.MM.yyyy
- Entered the Date From range '01.01.2005'
- While testing, tried to enter the date manually as 13.01.2007, but returned error popup "Entered date is not in range. Please enter a date after 01.01.2005
So dates with day of the month higher than 12 will return the "Entered date is not in range" error, in spite of respecting both the defined "Date Format String" and the "Date From" parameter attributes
Basically when a date parameter has its range defined (in this case only the starting/minimum date value), if the user fills the parameter manually with a correct date and then leaves the field (via tab or by clicking on a button).
Further research shows that the not only the actual date value is relevant but also the parameter's "Date Format String". In this case let's assume "dd.MM.yyyy" as the "Date Format String" and "01.01.2005" as "Date From" are set in the parameter.
In order to reproduce the issue the first date format element should be "dd". What happens is that the first date element representing the day of the month cannot exceed "12". So up to "12.01.2007" works. "13.01.2007" onwards returns the error.Apparently, in spite of the "Date Format String", the month is always expected as the first element in the date value passed to the parameter.
BIP will output a message like "Entered date is not in range. Please enter a date after 01.01.2015."
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document