Fusion 23B : Publisher Date Parameters Having Date Function Getting Reset
(Doc ID 2945365.1)
Last updated on AUGUST 03, 2023
Applies to:
Oracle Fusion Financials Common Module Cloud Service - Version 11.13.23.04.0 to 11.13.23.04.0 [Release 1.0]Oracle Fusion Inventory Management Cloud Service - Version 11.13.23.04.0 to 11.13.23.04.0 [Release 1.0]
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.23.04.0 to 11.13.23.04.0 [Release 1.0]
Oracle Fusion Self Service Procurement Cloud Service - Version 11.13.23.04.0 to 11.13.23.04.0 [Release 1.0]
Information in this document applies to any platform.
Symptoms
Date Parameters that have a Date Function set as Default Value get reset when another Parameter that has "Refresh other parameters on change" property enabled is provided an input.
Report will work fine when
- "Refresh other parameters on change" checkbox is not enabled for any parameters in the Data Model
- Date Type parameters are not defaulted with Date Functions or if Static Date value has been entered
Steps :
- Create a Data Model, create a Date Type parameter, and add a Date Function in the Default Value column, examples of Date Functions "{$SYSDATE()$}", "{$FIRST_DAY_OF_MONTH()$}" etc
- Create a Text/Menu Type parameter and check the "Refresh other parameters on change" checkbox
- Save the Data Model and create a report for this Data Model
- Run the Report, You will see the Date parameter with the default value derived from the Date Function defined in step 1
- Change the Date parameter's value
- Select/Change the value in the Text/Menu Type parameter defined in step 2
- Notice that the Date parameter change you made in step 5 is reset and the Date parameter shows the Default value now
This is illustrated in the attached document as well.
Changes
Fusion environment upgraded to release 23B
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 |
Steps : |
Changes |
Fusion environment upgraded to release 23B |
Cause |
Solution |
Workaround : |
References |