Forum Discussion

amit_saroha's avatar
amit_saroha
New Contributor III
3 years ago
Solved

Date Issue in Pipeline Parameter

Hi All,

I have a requirement to pass date in YYYY-MM-DD format and I am using the expression “Date.now().toLocaleDateString()” but I have the below issue.

When I use it in pipeline parameter “Effective_Date” then use _Effective_Date in the pipeline it fails but when I use it directly it works. When I pass something hardcoded in the pipeline parameter it also works e.g. 2022-01-01

Could you suggest what is happening here and what is needed to get it fixed?

Below is not working

Below is working

8 Replies

    • bojanvelevski's avatar
      bojanvelevski
      Valued Contributor
      3 years ago

      Hi @amit.saroha,

      The values that are passed from parameters, are always a string. So in your case, you’re not passing a function, but a string.

      In order your pipeline to work is, either leave the BatchParameter to get the date directly from the pipeline execute like shown on the picture above, or, use the eval() function with the parameter.

      eval(_Effective_Date)

      That way your function passed like a parameter, will be evaluated and considered as a function.

      Hope this helps,
      Bojan

      • amit_saroha's avatar
        amit_saroha
        New Contributor III
        3 years ago

        Thanks @bojanvelevski - It works but when I pass 2022-11-20 in same parameter instead of expression the eval (Effective_Date) returns 1991 but I need it as it is 2022-11-20.

        Please suggest if there is a way to do it, I want both the options working.

  • amit_saroha's avatar
    amit_saroha
    New Contributor III
    3 years ago

    Hi @bojanvelevski, yes, it will be a manual run. I tried the expression you have suggested but it didn’t work. Could you suggest what is wrong what I have done.