RSearch(): Maximum number of instruments retrieved
It seems that the maximum number of instruments retrieved for RSearch function is 2000. From the help file, I notice this limit is defined in administrative service. Can anyone tell me where it is? Much appreciated!
Best Answer
-
From a developer perspective this limit is hardcoded. It can only be changed centrally by Thomson Reuters, and I'm afraid the company has no plans of changing it.
0
Answers
-
Hi, I would like to ask if there have been any developments on this and whether it is now possible to change the default limit.
The Eikon help file still includes that the default limit can be changed through editing the POWERLINK.RSEARCH.DEFAULT.NBROWS setting. And having had a look through the Config folder in the installation path, the LMO.USERPROFILE.xml file describes that this setting (as well as the POWERLINK.RSEARCH.MAX.INSTR.PER.QUERY setting) can be overridden at user level.
If it is possible, could you please help me with adjusting the limit?
Many thanks,
Marek
0 -
There have been no changes regarding the max number of instruments that can be returned using RSearch Excel function or RSearch COM API. Neither of the parameters you found has any effect.
0 -
If you need the search to return more than 2K rows, the only way to do this is to order the result by some criteria and use the result of the previous query to construct then next one. E.g. if you need to retrieve the listing of a stock exchange you can set the exchange as the criteria and order the result by market cap descending. Once you retrieve the first 2K stocks, you can retrieve market cap for them. And then for the next query you add the criteria that market cap is less than the smallest market cap returned for the stocks in the previous query, retrieve the next 2K stocks and so on.
0 -
Thanks for explaining Alex. It's a shame there's such a limit! Especially since there is very limited search functionality on the Data API. I would suggest that the information in the help file is either at least removed given it's misleading or it is indeed implemented.
Thanks
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 625 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛