Bug with large numeric fields in grid (version 9)

Christian Sennewald

Hi

 

I found a bug while handling with large numeric fields and grids in metastorm bpm v9.

 

When you have a table with a numeric(19,0) field (in my case it was an "id" field) and you bind this table to a BO all is fine so far.

When you have a look at your table in the BO Browser all looks fine too.

When you now bind your BO to a grid on a form metastorm bpm indicates the field as an integer (or numeric) field. You can see this at the icon in DataAccess->"YourBO"->Variables

The problem here is that the numeric field is not the same field as in your database. Don't ask me why but the field is now rounded to 16 digits. So in my case my id in origin was "7167035734274173356" and the grid shows me this id as the following "7167035734274173000"

 

So as you can see the last three digits are "0" in my case. ;(

 

The quick workaround is to cast the numeric field to varchar in the BO definition. (in my case: CONVERT(VARCHAR(19), id) as id)

 

I will open a ticket in a few minutes. 

First of all I need something to eat against the disapointments

 

regards

 

Chris

Carolyn Anderson

Can you have a 15 digit numeric instead? Some systems do only accept 15 digit numerics, happens in Foxpro too apparently. Don't know why the two sections are operating differently, maybe they're written with different technology, but I do know it's a datatype roudning problem of some sort.

 

Make it a string if you really need so many digits.