Skip to main content
Question

How to use SYSDATE as in parameter to a method call in Aurena ?

  • February 22, 2021
  • 3 replies
  • 409 views

PlaChintW
Sidekick (Partner)
Forum|alt.badge.img+5

I have a method that accept company and the system date as in Parameters. But when I specified ${TRUNC(SYSDATE)} when map the values to parameter it gives the error saying “Sorry, there was an unexpected server error.”

This topic has been closed for replies.

3 replies

EntNadeeL
Hero (Partner)
Forum|alt.badge.img+10
  • Hero (Partner)
  • 181 replies
  • February 22, 2021
PlaChintW wrote:

I have a method that accept company and the system date as in Parameters. But when I specified ${TRUNC(SYSDATE)} when map the values to parameter it gives the error saying “Sorry, there was an unexpected server error.”

Hi @PlaChintW ,

Could you please try removing the trunc?

Also are you trying to pass the parameters from a command? Hope I understood this correctly.

Thanks,

Regards,


PlaChintW
Sidekick (Partner)
Forum|alt.badge.img+5
  • Author
  • Sidekick (Partner)
  • 7 replies
  • February 22, 2021

Hello Nadeesha,

Thank you for the reply.

I have changed the in parameter to ${SYSDATE}, but the error is still there.

Parameters defined as follows.

the error message is as follows.

Thank you and best regards,

Chinthaka


EntNadeeL
Hero (Partner)
Forum|alt.badge.img+10
  • Hero (Partner)
  • 181 replies
  • February 23, 2021
PlaChintW wrote:

Hello Nadeesha,

Thank you for the reply.

I have changed the in parameter to ${SYSDATE}, but the error is still there.

Parameters defined as follows.

the error message is as follows.

Thank you and best regards,

Chinthaka

Hi Chinthaka,

I tried this out myself and it worked fine. 

You have added the Company parameter correctly. same way it should work for the SYSDATE too.

try passing your SYSDATE as $[sysdate]. 

Adding the documentation link for future references.

Adding Commands (ifs.com)


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings