I have an issue I'm stuck on. We have this value writing to the DB for this column: It writes this exact value for about 75% of entries. The weirdest thing is, this value is not in the values in the PM.This is from the script task where the values are set:And here it is after the Write to Records node:
And you can also see here in the variables tab:Does -2137483649 mean anything in the crazy world of data? I tried searching it but didn't return anything useful.
Discussion posts and replies are publicly visible
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?
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.
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.
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!
I would bet on something (rule input, process variable etc) that has an unexpected type somewhere.