[SMITHGDWG]

Our Sandbox account was updated to 2018.1 and I noticed one of my scripts written in SuiteScript 2.0 is failing because when it grabs the inactive checkbox on my custom record it is returning “F” instead of false which eventually causes the issue. I didn’t see anything in the release notes that would cause this and it seems like a bug. Has anyone else noticed this? It seems to be getting the value as a SuiteScript 1.0 script.
This is a cached copy. Click here to see the original post.

[SMITHGDWG]

It actually looks to only be happening with Workflow Action scripts when you use the new record. I attached a sample script that will log “F” when using it in a workflow for a custom record. If I load the record and then get the value it returns false, which is what is expected.

Attached Files

[mschuette]

I noticed this alternating in certain places too. I put a formula using a case statement in a custom field looking up a check box value in another field, and used the same case statement in a search result. One needed F to work, and one needed False to work. I can’t remember which was which now. Now when I write a formula I usually write it as {field} = ‘F%’ to just avoid figuring out which one to use in different places. Not sure why this is. I’d be curious if anyone knows more about this.

[Author]

Posts