Uniqueness of ACRONYM and FID
For a given field ACRONYM (eg: "LAST") can we assume the FID will not change across different dictionaries or across different versions of the same dictionary?
Best Answer
-
Hi @kelvinyoung048 on Elektron we do not change field acronyms once they have been defined. In fact we do not curretly change any aspect of the field once it has been defined eg type of field, field length etc. So essentially once we create the field (even if we have created the field incorrectly) we do not go back and change anything - its effectively written in stone.
Having said that, we have a set of pre-defined fields within the data dictionary that we have pre-created to ensure that we can react quickly to market events and not have to wait for the next dictionary release to provide clients with that piece of data. These "pre-defined" fields are created in the data dictionary and available to view now. Once we need them we allocate the field internally and assigned to a venue. Upon the next update of the data dictionary we will then change the name/acronym of the predefined fields to something that better represents the content we are trying to publish.
We are also looking at the possibility of changing some of the field attributes and how disruptive that could be to user eg increasing the field length so we don't need to introduce an entirely new field and retire an older one, for example.
I'm not sure of the reason for the question, but we do always encourage users to try to use the field number rather than the name of the field in any coding.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛