Content filters seem to work on DynamicData - at least when key fields are used in the expression. I assume this works
because key fields are used to constuct the instance handle and filtering is possible without deserialization. I have not
tested this, but will filtering work on non-key fields for DynamicData ?
Thanks
Nico.
Hi Nico,
Dynamic Data is a wrapper API for managing the CDR representation of any type, in a type-independent manner. It gives the user the ability to inspect objects of any type, given that the type representation (definition) is known. The Dynamic Data API works independently of sample filtering, as filtering is applied at the presentation layer, when the sample is received (or to be sent, in the case of writer-side filtering). Thus, there should be no problem filtering on non-key fields.
Hope this helps.
Thanks,
Juanlu
Ok thanks, that helps.