topic Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0) in Workato Pros Discussion Board

Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

rpatrick_ — Mon, 17 Nov 2025 22:36:31 GMT

Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

I need help figuring out what this error means--why does it expect 0 arguments? How can I fix this?

This is the formula that I have mapping to the field: [DATAPILL]&.to_date(format:"MM/DD/YYYY")

Please let me know if any additional info is needed. Any guidance is appreciated, thank you!

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

rajeshjanapati — Tue, 18 Nov 2025 05:45:56 GMT

Hi @rpatrick_,

your pill may be "now" or "today", which does not return a datetime input as a user-defined string by default, so you need to add "strf" formula to make it user-defined string, because of that, it is throwing an error. Please check the below attached image and try it out once, if you face any error again, please do posted here.

Thanks & Regards,

J Rajesh Kumar.

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

shivakumara — Tue, 18 Nov 2025 07:23:40 GMT

Hi @rpatrick_ ,

After reviewing the requirement, it appears you are passing dateTime or date as input, which is causing the error:
Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)
This happens when using the to_date formula, which returns the format YYYY-MM-DD (Required response).

If you are passing a date or dateTime value to to_date, try converting it to a string first. (A sample example is provided below.)

Thanks and Regards,
Shivakumara K A

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

rpatrick_ — Tue, 18 Nov 2025 15:17:35 GMT

Hello,

I think you are correct about the type of input being the issue. I first tried with the formula as you've shown, but it still errored. I changed the formula to: &.to_s.to_date(format:"YYYY/MM/DD") - this time getting the nil input error. I then tried: &.to_s&.to_date(format:"YYYY/MM/DD"), and it no longer errors on empty inputs, but it does say invalid date for datapills that are not empty. I noticed that the trigger output has 0022 as the year instead of 2022, so I changed the formula format to be YY/MM/DD, but I still see invalid date.

What do you think I am missing?

Thanks for your help,

Renee

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

gary1 — Tue, 18 Nov 2025 19:51:11 GMT

If your Last Provision Date is "0022-05-15", you're kind of hosed because that's not a valid date whether it's a string type or date type. You need to fix that first -- which should probably be fixed upstream in the source application providing the data. The to_date method won't work with "22-05-15". The year needs to be a 4-digit year value.

You can do something wild like this. It assumes all years are 2000 or greater. If you have a year in the 1900s, you're hosed again.

["0022-05-15".split("-")[0].to_i + 2000, "0022-05-15"[5..-1]].smart_join("-").to_date ## output >> "2022-05-15" as date type

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

saraiva — Wed, 19 Nov 2025 21:38:55 GMT

Hello!

Is your input a text or date/time input?
Can you paste here the schema of that input field specifically just to confirm it is using the correct type?
Sometimes the platform screws up by setting the render_input and parse_output attributes.

If you have something like this:

{ "name": "test", "type": "date_time", "optional": false, "label": "Test", "control_type": "date_time", "render_input": "date_time_conversion", "parse_output": "date_time_conversion" }

...or this...

{ "name": "test", "type": "text", "optional": false, "label": "Test", "control_type": "date_time", "render_input": "date_time_conversion", "parse_output": "date_time_conversion" }

Just remove the render_input and parse_output attributes, since your Jira action is expecting the date not in ISO8601 format.

Cheers!

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

rpatrick_ — Wed, 19 Nov 2025 22:59:29 GMT

Thank you, this advice has helped me reach a solution. I did need to alter the datapill date instead of just the formatting, which I did with a string instead of the suggested integer conversion method. This is ultimately what worked:

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

saraiva — Wed, 19 Nov 2025 22:59:05 GMT

That "Service Date" field - is something you have access to check the schema?

If so, can you paste it here?

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

saraiva — Wed, 19 Nov 2025 23:11:45 GMT

I have the same concern as @gary1 regarding those 'dates' you're receiving. 22 can be either 2020 or some other year of any other century (I'm ignoring your business logic and industry).
In any case, if you still want to go hardcore with such solution, you need to correct your example to add these parenthesis:

Re: Error calculating input for field 'myField': wrong number of arguments (given 1, expected 0)

gary1 — Wed, 19 Nov 2025 23:57:33 GMT

Update: I tested the original formula and it outputs "20022-05-15", so maybe that's a valid year, but it's obviously incorrect.

Original post:

rpatrick said it worked, but I'm kinda of surprised...

I think the first parenthesis needs to come after "2" + ( like this:

"2" + ( [Last Provision Date]&.to_s&.slice(1,9) )&.to_date

If the intent is to slice "0022-05-15" to "022-05-15"...

And then concat "2" + "022-05-15" to make "2022-05-15"

This way the slice happens before the concat, otherwise it would end up as "20022-05-15", and then the slice would output "0022-05-15" again! Maybe?

Side note: I had no idea you could use "if" in formula mode. I always used the short form ternary operator, like:

[condition] ? [if true] : [if false]

In this case you could do:

[Last Provision Date].present? ? "2" + ( [Last Provision Date]&.to_s&.slice(1,9) )&.to_date : "" ## or nil