BUILDER: if I create a field DECIMAL and then in the validation rule I make for example a rule to have a value like:

decimal (11, 7)

the validation rule works perfectly, BUT the value is not stored correctly in the DB, because the SQL code to create that field at the installation process of the component, is wrong.
It still create a field:

decimal (10, 2)

When you create the decimal field type, are you also adding in the precision and scale to the field properties on the table?

I've done this with no problem at all previously with height, width, price and percentage type data combined with a custom regex validation too.

Gez

Hi, thanks for the reply.
where should be the option?, I didn't find it any other options except these:

Hi @Tomaselli,

When you add the field to the table, select the decimal data type then you'll see precision/scale input properties on the field underneath the required, unique etc...

Then, when you type into precision/scale, a rule/handler will be created. You can and probably should override the handler and regex with your custom validation.

Hope it helps,

Gez

thanks, I found it, the problem was because I created the table field from the FLOAT instead to use the DECIMAL, even if at the end....the final field table type it's the same.

but it shouldn't be like that.

Tomaselli wrote: what do you mean - that it shouldn't be storing it as a float when decimal fieldtype is set?

At the beginning I selected a FLOAT type, then I modify the validation rule, to work as a decimal (11, 7).
I saw on the SQL file generated, it was generated a decimal (10,2), so I thought the jcook builder recognized my will and it generated a decimal field, but the precision, scale was wrong.

So I made the post.

Then you pointed me to the fact I did a mistake chosing the FLOAT, but I should have choosen a DECIMAL type, otherwise the precision, scale options will not appear.

so my thoughts are:

1) if the jcook generated a decimal field instead of the initial float field, why didn't jcook generate a correct precision, scale (decimal(11,7))?

2) IF jcook wasn't supposted to generate a decimal field from an initially choosen FLOAT field type, why did it generate a decimal?

I hope my explanation is enough understandable.

Hi @Tomaselli,
Don't apologise! All feedback - whether they turn out to be issues, or not - are really helpful in identifying areas of the ever-evolving interface that could be further explained and/or documented.

As always, your input is always valued!

Thanks,

Gez