Hello
I've created a new computed Attribute and want to add it to the filter.skipAttribute parameter.
What I notice is that the application does not recognize it so it still filters all records containing this attribute.
If I put in config parameter for example "ignition" then the recordings normally skip all filters.
Here you see what I've done..
<entry key='filter.skipAttributes.enable'>true</entry>
<entry key='filter.skipAttributes'>engine,result</entry>
And here is the computedAttribute
engine
power ? power > 13.1 : null
Boolean
Also in the state of the device I normally see the new attribute.
My question is if computedAttributes can be applied to the filter.skipAttributes parameter.
Thank you
Anton any answer on this?
As far as I remember, computed attributes are handled after filtering, so the answer is NO.
Hello
I've created a new computed Attribute and want to add it to the filter.skipAttribute parameter.
What I notice is that the application does not recognize it so it still filters all records containing this attribute.
If I put in config parameter for example "ignition" then the recordings normally skip all filters.
Here you see what I've done..
<entry key='filter.skipAttributes.enable'>true</entry> <entry key='filter.skipAttributes'>engine,result</entry>And here is the computedAttribute
Also in the state of the device I normally see the new attribute.
My question is if computedAttributes can be applied to the filter.skipAttributes parameter.
Thank you