Can we pass FID Name while creating view and receive payload of the same only?

While creating view, We observed that with intValue it is working as expected. for example.

array.add(EmaFactory.createOmmArrayEntry().intValue(70));

but when we use ascii value, the payload is full IMAGE message. Is there a feasibility in EMA to retrieve only the single FID in payload by passing name like :-

array.add(EmaFactory.createOmmArrayEntry().ascii("SETTLE"));

Please advise!

Note that view type for integer is

view.add(EmaFactory.createElementEntry().uintValue(EmaRdm.ENAME_VIEW_TYPE, 1));

and for Name is shared as

view.add(EmaFactory.createElementEntry().uintValue(EmaRdm.ENAME_VIEW_TYPE, 2));

ViewType --> 2 resulting in --> state="Open / Ok / Unsupported view type / 'All is well'"

Please let us know if we are missing something here.

@nick.zincone, @umer.nalla, Can you please advise here?

Find more posts tagged with

elektron

elektron-sdk

refinitiv-realtime

Accepted answers

pimchaya.wongrukun01

Hello @gaurav.mahajan

What your application can do is to find out the field numbers
according to the input field names by looking into the dictionary. Then, set the field numbers to the array as an
integer with View Type 1 in the request sent to ADS because ADS does not
support View Type 2. The reason is the feed sends data to ADS in the format of field
ids with their values as an example shown below:

<fieldEntry fieldId="1" data="19A2"/>
<fieldEntry fieldId="2" data="40"/>
<fieldEntry fieldId="3" data="5448 4F4D 534F 4E20 5245 5554 4552 53"/>
<fieldEntry fieldId="4" data="02"/>
<fieldEntry fieldId="6" data="0802 BCFD 20"/>
<fieldEntry fieldId="7" data="0802 BCFD 20"/>
<fieldEntry fieldId="8" data="0802 BCFD 20"/>
<fieldEntry fieldId="9" data="0802 BCFD 20"/>
<fieldEntry fieldId="10" data="0802 BC87 F0"/>
...

Hence, ADS filters fields using field ids (View type 1 or FIELD_ID_LIST
) and not support field names(View Type 2 or ELEMENT_NAME_LIST).

All comments

pimchaya.wongrukun01

Hello @gaurav.mahajan

You are not missing anything. EMA can set ViewType 2 and the list of field names (ascii values) in a request which you are doning properly. Unfortunately, ADS which receives and processes the request from your application does not support the ViewType 2 currently. That’s why you get Unsupported view type in the state and a full IMAGE message instead of your requested field names from ADS. Hence, to get your preference fields, only ViewType 1 and the list of field ids can be set in the requests.

gaurav.mahajan

Thanks @pimchaya.wongrukun01, Is there anything we can add or do from our side to get support for View Type 2. OR this is something our of our control and we cannot get this ?

pimchaya.wongrukun01

Hello @gaurav.mahajan

<fieldEntry fieldId="1" data="19A2"/>
<fieldEntry fieldId="2" data="40"/>
<fieldEntry fieldId="3" data="5448 4F4D 534F 4E20 5245 5554 4552 53"/>
<fieldEntry fieldId="4" data="02"/>
<fieldEntry fieldId="6" data="0802 BCFD 20"/>
<fieldEntry fieldId="7" data="0802 BCFD 20"/>
<fieldEntry fieldId="8" data="0802 BCFD 20"/>
<fieldEntry fieldId="9" data="0802 BCFD 20"/>
<fieldEntry fieldId="10" data="0802 BC87 F0"/>
...

Hence, ADS filters fields using field ids (View type 1 or FIELD_ID_LIST
) and not support field names(View Type 2 or ELEMENT_NAME_LIST).

gaurav.mahajan

Thank You for sharing details! We can work it out by parsing dictionary. But i still do not know, why ADS does not support that. Is this subject to some difference licensing ? I am assuming if API has support for type 2 so infrastructure should also support the same unless it is restricted.

pimchaya.wongrukun01

Hello @gaurav.mahajan

I am not ADS specialist so I cannot answer why ADS RSSL(Reuters Source Sink Library) connection EMA connect to does not support field names(view type 2). Anyway, you can ask ADS specialist by submitting this question via Get Support . After you log in, select your subject e.g. "The product does not work as expected". At "Product", select the ADS i.e. “ADS-Advanced Distribution Server”. If you face any difficulties submitting the query, please contact the Account team.

EXPLORE OUR SITES