nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Decimal values are incorrectly processed in text algorithms

OSchulz

Hi,

I need to lock/unlock the data entry based on configured thresholds, therefore I need to work with decimals (stored in a cube) in text algorithms (input data validation rules for data entry in data views), but this leads to problems, because they are incorrectly processed and because of that its not working - see screenshots, where I display cube values by a numeric algorithm and by a text algorithm:

I see the same behaviour when I use this data in an input data validation rule for the data entry.

I tested it with a cube with data type single and double - the problem is the same.

How can I fix this or is this a board bug?

Find more posts tagged with

Accepted answers

Robert Barkaway

No differences for me.. What version of Board are you using? I'm testing on 14.4 currently but I can try a different version if needed.

All comments

Robert Barkaway

Hi, what you're seeing there is to do with the way in which Float values are stored, for numbers to several decimal places it can cause slight differences, yes. I'm not sure I understand why you're needing to convert the number to text though?

OSchulz

Hi Robert, thank you. Based on this decimals I want to control a data entry - an entered value should only be valid, if its above the configured decimal. And the input validation rules for data blocks in data views are text algorithms. Is there a different way to achieve this?

OSchulz

I see this for all decimals, even for x.1. The only case which works is x.5

Robert Barkaway

I'm not sure what you mean about the validation rules being text algorithms, here I've created a validation algorithm which is entirely numeric and it's working fine for me?

OSchulz

I think you will get/see the problem, when you try to enter the exact same value - e.g. 13.270 in column "test locking 2" for row manchester

OSchulz

at least thats the case for me

OSchulz

I think you dont the see problem, because you used >= for your example, and the text algorithm changes the decimal to a slightly smaler value, so then you dont get into the trouble I do, because I need to use it with <=

Robert Barkaway

No, still works fine for me

I can only think that there's a tiny difference between yours at a decimal level, beyond the 3dp you're showing, I can't see why else it would be seeing a difference.

OSchulz

Did you also try it with <= instead of >= ? and then entering the exact same value

Robert Barkaway

Yep

OSchulz

Robert Barkaway

No differences for me.. What version of Board are you using? I'm testing on 14.4 currently but I can try a different version if needed.

OSchulz

Thank you, Robert, for testing - I think I have found the issue. I realized the threshold values weren't entered, originally, they were calculated before in a procedure

Robert Barkaway

Aha, yes that would explain it. No problem, here to help if you have any further issues.