Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • EMA /
avatar image
Question by kc_1905 · Jul 16, 2019 at 06:37 AM · emafieldsfield namedifferent field names

UpdateMsg field name differs from spec

Hi

We noticed that some field names being returned from our queries have different field names when compared to the refinitiv model.

Example:

FieldEntry fid="12963" name="PRE_1ET262" dataType="Enum" value="10"

When cross-refrenced to the refinitiv model and data dictionary it is called DCNT_BAS1

Any particular reason why the name differs?

The UPA server Im connecting have this version

UPA server component version: ads2.6.2.E1.linux.tis 64-bit

No idea if the version is relevant.

Many thanks

Tim Smith

People who like this

1 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by umer.nalla · Jul 16, 2019 at 06:46 AM

Hi @kc_1905

If your application is downloading the dictionary from the server (which is the default), then this means the data dictionary files on the ADS server are out of date

For example if I look at a dictionary version Version 4.20.21_TREP_15.91 from 2015 then FID 12963 is defined as PRE_1ET262

But if I look at a data dictionary file from 2018 then 12963 is defined as DCNT_BAS1

Please ask your market data team to update their ADS and ADH to more recent versions of the data dictionary files RDMFieldDictionary and enumtype.def

If however, you are using local data dictionary files - then your local files are out of date.

New versions of Data dictionary files are released several times a year and your Market Data team should be updated their ADH + ADS component dictionaries on a regular basis.

Comment
kc_1905
Tim Smith

People who like this

2 Show 2 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
kc_1905 · Jul 16, 2019 at 06:50 AM 0
Share

is there a way via EMA API to check what dictionary version the server is sending? We are not using local dictionary files so Im sure the server is sending outdated files.

Many thanks for the swift response.

avatar image
kc_1905 kc_1905 · Jul 16, 2019 at 07:28 AM 0
Share

Managed to find out the version the server is using by sending a Dictionary Request Msg

Good example to use for reference is

series300/example332__Dictionary__Streaming/Consumer.java

from EMA github

avatar image
REFINITIV
Answer by Tim Smith · Jul 16, 2019 at 06:48 AM

Hi,

Very good question and it comes down to the version of the field list you are using.

To be a bit more flexible and *hopefully* speedier to market when we need to create new fields on our Realtime network we have a number of predefined fields available. These are created using the prefix PRE* followed by text to describe the type of field.

When we have a need to use that field for a particular piece of data that we havent come across before then we rename the field to describe the content we are then using the field for.

In this case field 12963 has been renamed to reflect it is now being used for the Discount basis for a bond.

https://refinitiv.fixspec.com/specserver/repo/elektron/thomson-reuters-elektron/field/dcnt-bas1

I am not quite sure when this field was renamed but it effectively means you are not on the latest version of the data field list (sometimes known as appendix a or RDMD). To get this file updated will depend on your infrastrecuture as to whether it is managed locally at your site or with us so you may need to log a query.

Generally we recommend to use the field number in coding if possible as that never changes.

Comment
kc_1905

People who like this

1 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
9 People are following this question.

Related Questions

When do we use update message processing by EMA?

Linux example based on 110, cannot find RDMFieldDictionary

EMA Webinar Nov 2: Is it possible to publish/receive a yield curve?

EMA interval based subscription

decode of just encoded object in EMA C++

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges