Random unknown value writing to DB instead of value in PM?

RE: Random unknown value writing to DB instead of value in PM?

Mathieu Drouin — Thu, 24 Apr 2025 21:34:53 GMT

I would bet on something (rule input, process variable etc) that has an unexpected type somewhere.

RE: Random unknown value writing to DB instead of value in PM?

KristinForeyt — Thu, 24 Apr 2025 17:30:28 GMT

I will continue to look into it. It's odd because it was working fine before, not sure what changed as we weren't working on any code/objects related to this piece. Thank you for taking the time to reply!

RE: Random unknown value writing to DB instead of value in PM?

Mike Schmitt — Thu, 24 Apr 2025 17:24:09 GMT

Then I'm guessing something goes haywire at some point while a number is being converted - it's hard to say without seeing the code / process steps involved.

RE: Random unknown value writing to DB instead of value in PM?

KristinForeyt — Thu, 24 Apr 2025 14:52:35 GMT

The field is text, and the DB field is varchar:

Most of our numbers associated with this app (filing #s, etc.) have a type of text because the value for some of them can get so long that it exceeds the integer value.

RE: Random unknown value writing to DB instead of value in PM?

Mike Schmitt — Thu, 24 Apr 2025 14:34:20 GMT

Look how similar your mystery value is to the "negative integer overflow" (the lowest negative integer you can store before it overflows). The most curious thing here is that it's slightly off. But either way, this suggests to me that the value is being set to something totally bonkers, like an accidentally blank but not null value, or something else.

Oh wait - are you trying to save a field of type "text" to an integer field? I expect that might have highly unexpected results (like the above). Why can't you either make your DB field TEXT or change your RecordType field type to INTEGER?