SYSDATE Syntax {$SYSDATE()$} is Shown in Publisher Report Parameter Instead of Actual Date Value
(Doc ID 1405424.1)
Last updated on APRIL 17, 2024
Applies to:
BI Publisher (formerly XML Publisher) - Version 11.1.1.5.0 to 11.1.1.5.0 [Release 11.1]Information in this document applies to any platform.
Reviewed for relevance 12 Aug 2014.
Reviewed for relevance 3 Oct 2018.
Symptoms
Issue Clarification:
The ability to set a default value for a date field does not work.
This was previously addressed in Bug 11679262 - SYSDATE SYNTAX {$SYSDATE()$} NOT WORKING FOR DEFAULT VALUE IN REPORT PARAMETERS, but there was a re-occurrence.
Users are running reports with no date entry since unable to set the default date.
When looking the Report Layout the {$SYSDATE()$} parameter actually displays the display value of for example, 09-01-2011.
When viewing the report (selecting the View Report button), the date parameter displays {$SYSDATE()$}.
Steps to Reproduce:
Open Data Model.
Select Parameters
Create parameter with default date value of {$SYSDATE()$}
Define Data Type as Date
Define Date Format String as MM/dd/yyyy Z
View Report
Date Field shows SYSDATE instead of actual date value
Workaround:
Manually add the date value in the default date value field.
Impact on Business
When users do not enter date filters it causes slowness and can sometimes crash the reporting server.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |