When performing a DataMiner soap call with function GetTableWithFilter we have a problem when filtering on a rounded number.
In Cube the value is being displayed as 4171.8972 MHz, however it looks like the value is actually 4171.89719 MHz.
When filtering in Cube in the table on value 4171.8972 returns the row, but not when filtering with the soap function.
There it seems to look only in the Value tag and not in the DisplayValue tag.
Can this be seen as an issue, or is there another way to perform the filter on the display value?
Following is a screenshot with the issue
The API method passes-on the filter to the DataMiner server, which will filter the data (as performant as possible, maybe even at database level) before it is returned, while not knowing the display value at that stage.
Cube has the display value of the displayed data, and is able to filter it at the client side. You could do the same as Cube, by getting the entire table via the API, and then filter it yourself on the display value. Note that client-side filtering might not always show all results in case of partial tables.
ok, that’s clear. I believe I found a workaround:
value=1008 >= 4171.8971
value=1008 <= 4171.8972