Upgrade to 2026.100.x broke BPMs

Kinetic ERP
1

Hi all,

The upgrade to ERP 2026.100.x has brok BPMs.

We usually just need to enable the compatible checkbox, which resolves the issues with any BPMs, however I have one BPM that won’t save due to the following error:

InTran.bpm_SalesOrderPr.cs(193,111): error CS1503: Argument 3: cannot convert from ‘System.DateTime’ to ‘string’

As per the image below; I’m pretty sure the issue is related to the ShipDate>Today condition and Set Priority 5 set field widget.

image
image1432×807 40.5 KB

image
image1438×601 20.7 KB

image
image1018×634 30.4 KB

Can anyone shed some light on why its trying to convert a DateTime to a string?

The Set Priority 5 widget MtlQueue.Priority field is an int32, and the 5 expression is also an int32.

image

image
image408×154 4.45 KB

If you need any more info, please just ask.

Thanks,

2

There’s somewhere in your BPM where you are setting a string to a DateTime. I’m not seeing it based on the screenshots you posted so far.

3

that’s what I thought I noticed too…

4

I found the problem.

Its the ShipDate>Today condition thats the issue.

image
image1071×532 19 KB

If i change Filter Value to BAQ Today Constant (As a test) it works fine.

It doesn’t like the Current date filter.

How can I achieve -2 days without using Current Date filter?

Thanks,

5

Managed to fix this using a variable and set argument widget.

I added a variable called TargetDate as a DateTime.

image
image907×178 3.64 KB

Then added a Set Argument/Variable before the condition, and set the variable to TargetDate and the expression as 'BpmFunc.AddInterval(DateTime.Now, -2, IntervalUnit.Days).

image
image1062×648 31.5 KB

image
image826×273 7.13 KB

Then in my condition query i set the filter to my variable TargetDate parameter.

image
image1078×556 15.5 KB

Thanks,

6

I’m very happy you have a work around. that said a lurking developer who you all know but will not name, created a bug report and we have hte fix in go forward code. it will be coming to an update of 2026.100.x as it finishes QA testing and automation as that should work.

I’m adding your work around to the problem case

problem number if you want to link a support case to it: PRB0319825

7

Cough @JeffLeBert cough

8

I do like taking credit for fixing stuff. It’s even better when I actually deserve the credit, but it wasn’t me. :wink: