Skip to main content
Question

Lobby element shows correct data but navigation fails

  • May 22, 2026
  • 2 replies
  • 7 views

Hi reader,

IFS V Cloud 24.9

I have a lobby element that correctly displays a count of the two records found, which is correct based on my parameters.

But I am unable to navigate to the Opportunities page via the navigation as i get an error.

If i remove this one line of code from the where clause in the Datasource, so that all other parameters defined are used - then the navigation to opportunities works without error.

...AND (CLOSURE_DATE >= NVL($DATE_FROM$, SYSDATE) AND CLOSURE_DATE <= NVL($DATE_TO$, SYSDATE))... 

Yes, i have also used the Between syntax as well and the tile result count is still correct in the datasource as shown above - so it does not seem to matter.

 

But when I put this line of code back into the where clause of the data element I get an error again on the navigation…

Error details: [{"code":1861,"message":"ORA-01861: literal does not match format string"}]

 

I have tried passing the dates as filter in the url address, as well as many other permutations to the point where it does not work and i have had to give up. 

If anyone knows how i can resolve this - i appreciate your experience and wisdom to help me get this resolved.

Note: i did do a test with hardcoded parameters with the ‘use datasource condition off’ and it works - so i was able to do that ...however, why can i not use the ‘conditiion on’...and plus i have about 15 or so other parameters that I would rather not code in a filter. Although i did think I could used a combo of condition on with filters - but that still errors.

Big thanks to anyone that can show me where I am going wrong.

 

 

 

 

 

 

2 replies

WyrDavidB
Hero (Partner)
Forum|alt.badge.img+9
  • Hero (Partner)
  • May 22, 2026

Have you tried this option in the navigation segment - given everything else you have tried, I suspect you have already - but worth checking.

 


Thank you for taking the time to read the problem I have been experiencing and for making a fix suggestion. Yes, I have tried that several times, too, along with any changes that I have made inside the datasource. But sadly, it does not seem to make any difference :(