Skip to main content
Question

Date Parameter in Lobby Navigation

  • August 19, 2026
  • 3 replies
  • 18 views

Forum|alt.badge.img+11

I’m trying to navigate from a lobby element to the Document revisions tab.  I’m getting an error calling out invalid date format.  This is my SQL that works great for the lobby element, but won’t allow navigation to the document revisions.

 

DOC_CLASS in ('NDA SUPPLIER', 'SUCONTRACT', 'SUISO', 'SULIABIL', 'SUPRICE') and OBJSTATE <> (select &AO.DOC_ISSUE_API.FINITE_STATE_ENCODE__('Obsolete') from dual) and (DT_PLANNED_FINISH < trunc(to_date( '#TODAY#', 'YYYY-MM-DD-HH24:MI:SS' ))+ 90 or DT_PLANNED_FINISH is null)

 

Does anyone know how to code this so I can use the navigation?

3 replies

Abdul
Superhero (Partner)
Forum|alt.badge.img+20
  • Superhero (Partner)
  • August 19, 2026

Hi ​@TosohLBlum,

I tried below steps with your SQL statement, and it's working fine. 

  1. Create Lobby Datasource with your SQL Statement (count is 0 since Doc classes does not exist in my env).
  1. Created Counter type Lobby Element where I enabled Use Datasource Condition toggle for navigation.
  1. System opens Documents Revision screen with Datasource Condition.

 

Hope this will help.

 

 


Forum|alt.badge.img+11
  • Author
  • Hero (Customer)
  • August 19, 2026

Mine looks just like that and I get the error below.  What version are you running?  I’m working in 25R1 UPD14. (It does the same thing in our PROD environment UPD4)

 

IFS Web Version: 25.1.14.20260709072516.0

Date: 2026-08-19T14:29:20.599Z

 

---------------------------------------------------------------------------

 

DocumentRevisions/List (server error)

Database error occurred. Contact administrator.

Error details: [{"code":1821,"message":"ORA-01821: date format not recognized"}]

 

Server stack trace error(s):

  Failed to execute the generated database statement

  ORA-01821: date format not recognized

 

  ORA-01821: date format not recognized


Abdul
Superhero (Partner)
Forum|alt.badge.img+20
  • Superhero (Partner)
  • August 19, 2026

@TosohLBlum, I configured in 26R1, and tried the same in 25R1 UPD12 as well, it’s working fine there also. I will suggest, raise a ticket with IFS.