Hello,
I have an integer required field, that can be equal to zero. (must be in some cases).
When setting this field to 0, through a trigger, I am getting an error saying that this field must have a value.
Looks like the value '0' is interpreted as empty for integer fields. Is that a known issue please ?
Thank you,
Meryem
Hi MeryK,
Just an update. We will deliver this in December release. :)
Regards,
Harsha.
Hi MeryK,
Are you trying with object script trigger with rbv_api.setFieldValue() API?
Try using "Update Field Value" trigger its not throwing the error.
Make sure integer field should not be in create page.
If integer field is in create page as it is required record creation will fail.
Hope this helps
Hi Rajkumar Mateti,
No, I am using rbv_api.updateRecord() in a trigger, as I am updating other fields as well. And then calling this trigger after update.
I have this field on a New page. But I am setting it and hiding it.
When setting the integer required value to 0 from that trigger I described above, the value is considered as empty.
Yes I understand that if the field is required and empty then the creation will fail, but I am setting to '0'. '0' is a value, it is not empty.
Do you get my point? & were you able to reproduce that ?
Thanks
Meryem
Hi guys,
Anything new on this please?
As I said, I am using a trigger to update the record, and some fields are integers and need to be equal to '0' sometimes. In that case rbv_api.updateRecord is not working..
Is that a known behavior ?
Thank you,
Meryem
Hello,
Can someone have a look to that please as we need a reply urgently ?
Thank you
Meryem
HI MeryK,
Yes, it is an issue we are unable to set value as 0 for integer field using server side APIs. We will log a defect and let you know once its fixed.
Thanks,
Rajkumar
Hi,
Thank you for the reply. This is quiet critical for us. Can you let us know if it could be solved for December release please?
Cheers
Meryem
Hi MeryK,
Just an update. We will deliver this in December release. :)
Regards,
Harsha.
Good, thanks !
Meryem