Filtering FIDs

Vyom

Hello! I would like to filter the FIDs included in messages. From what I understand, dynamic views let you specify which FIDs you want in your request so you only receive those specific fields—please let me know if I’m mistaken. I also came across the concept of server-side filtering. Could you explain what that entails? Are there any other approaches to limit the bandwidth usage or filter FIDs in the response? Additionally, could you provide a comparison of these different methods and discuss their advantages and disadvantages?

Thank you!

Jirapongse

@Vyom

Thank you for reaching out to us.

API supports two types of fields filtering.

1. Dynamic View. The application can specify the interested FIDs in the request messages and then the application will retrieve only data of the interested FIDs.
2. Update Filtering. This feature is available in RTSDK C/C++ 2.3.0.L3 (3.9.0.L3) and Java 2.3.1.L1 (3.9.1.L1) and it requires ADS 3.9.0.L1. With this feature, the ETA application can specify the UpdateTypeFilter or NegativeUpdateTypeFilter element entry in the login request message. Then, the update type filtering will be used for all subscribed items. For more information, please refer to the ETA Developer Guide in section 3.2.9 Update Filtering.

Yes, you can also configure ADH or ADS to support field filtering.

Like the Refinitiv Real-Time Advanced Distribution Hub, the Refinitiv Real-Time Advanced Distribution Server provides a field-filtering feature, which selectively removes fields in images and updates, thus reducing the bandwidth consumed. The field-filtering feature requires that the Refinitiv Real-Time Advanced Distribution Server cache be enabled. To configure this, you must have a detailed knowledge of the fields needed by the client applications. Also, detailed knowledge of certain Refinitiv Real-Time FIDs and their contents is helpful.

The configurations look like this:

*ads*ELEKTRON_DD*filterField : 259

*ads*ELEKTRON_DD*filterFieldValues : 113, 118, 100

*ads*ELEKTRON_DD*filterList*113*contains : 22, 25

*ads*ELEKTRON_DD*filterList*113*remove :

*ads*ELEKTRON_DD*filterList*118*contains :

*ads*ELEKTRON_DD*filterList*118*remove : 178, 32, 43, 80

*ads*ELEKTRON_DD*filterList*100*contains : 14

*ads*ELEKTRON_DD*filterList*100*remove :

Please check the section 20.15 Field Filtering on the ADS Admin Guide. I assume that it may impact all items of the configured service. Please contact the RTDS support team to verify this.

In short:

• The dynamic view impacts each individual item request.
• The update filtering affects the entire application that uses this feature.
• The server‑side field filtering impacts all users who consume the data for that service on that server.