Do you have a value in your table that is set to Integer, that maybe you are trying to put something other than numbers into?

I think i know what happens here in my case, say you set up a lookup table and load some data. At the time of import the table sets the datatype.

Then create a rule and plug that into a workflow and test only to find CAST error. But where is it, it doesn't say... So trial and error, go back to the table and reimport the data, changing the suspicious datatypes maybe from number or date to text - this is where an invisible issue can arise.

Inside the rule, the data is not visibly typed - i can see nothing to say if the data is a number or a string however i believe it holds on to the type when the rule was created.  Updating the table does not cause it to refresh.  The solution is simple, remove all the select and where clauses and add them back in again to rebuild the rule.  That seemed to fix the issue for me. 

I'm having trouble with a function in Laserfiche that seems to be giving me persistent issues. I have a business process (BP) with a table containing dates, which are passed to a workflow via a dateTime parameter (e.g., 12/30/2024 12:00:00 AM, 12/30/2024 12:00:00 AM). However, when the workflow inserts the date into a dateTime formatted column in a lookup table, I get a cast error.

I’ve tried using the token calculator with datevalue(12/30/2024 12:00:00 AM), but it doesn’t work. I also tried parsing the date to extract the year, month, and day, and then using date(vYear, vMonth, vDay). This works in the token editor but fails during runtime.

Why is it so difficult to pass a Laserfiche date between its own modules without needing conversions? I’m working entirely within Laserfiche and simply trying to pass a date from one module to the next. Can anyone shed light on why this might be happening, is it regionals settings?

When i extract the year, month, day im using regex that works on the date as its written in the token (12/30/2024 12:00:00 AM) but at run time I'm getting a date (1,1,1) so its writing in a date from 1899. At least the cast error has gone but I'm suspecting the date displayed in the BP and WF token is displayed human readable, but its stored/processes as a datetime. My regex works on the date string but fails at run-time so if the "date is a date" then why the cast error inserting into a lookup table?

Got it! Bipin's post got me there. Look in the rule, test it and see that it's expecting a date 'yyyy-MM-dd' so in the Workflow rule activity just add that formatting there and it works great.  Here is a screen shot to show.