Hello Team,
We are developing an Interactive Automation Script using the Skyline.DataMiner.Utils.InteractiveAutomationScriptToolkit (v10.5.5.4).
We are trying to configure a Numeric widget to accept and display three decimal places with a 0.001 step size.
SrateSelection = new Numeric() { Decimals = 3, StepSize = 0.001, Minimum = 0, Value = srateValue};
SatfSelection = new Numeric() { Decimals = 3, StepSize = 0.001, Minimum = 0, Value = satfValue};
The user should be able to use the up/down arrows and edit any value with three decimals. The problem Detected is that the widget throws an error (Only Steps of 0.001 are allowed) when the initial value (Value) is loaded or when the arrows are used on specific numbers:
Values like 1.00x and 2.00x for the rest of the values it works well.
We have attempted several workarounds to mitigate the floating-point precision error, including using Math.Round(value, 3) and intermediate decimal conversions. Is there a known bug or limitation for StepSize = 0.001 in this version of the toolkit that causes a precision conflict for these specific values? is there a way I can fix it ?


Thanks in advance !!
Hi Aaron,
Thank you for the update and for letting me know about this future fix.
Do you have an approximate date or estimated timeframe for the release of the web upgrade 10.6.1?
Hi Gina, the 10.6.1 release is planned for Friday Dec 12th 🙂
Awesome! thank you.
Hi Gina,
Have you been able to fix this issue with the 10.6.1 upgrade? If yes, could you select this answer to indicate that this question can be closed an no further follow-up is needed?
Hi Mariake,
I wanted to let you know that the error was fixed after upgrading to DMA V10.5.12 and WebApps 10.6.1. Apologies for the delay in my response; I was only recently able to complete the upgrade of my staging environment to these versions.
Everything seems to be working correctly now.
Hi Gina,
The numeric component has issues in certain situations when using the StepSize in combination with Decimals. It can cause validation errors for specific values (such as 1.00x or 2.00x) due to an internal precision conflict.
This issue will be resolved with the upcoming web upgrade 10.6.1 (releasing soon). To benefit from this fix, your system will need to be running DataMiner version 10.5.12 or higher.