New path to the XML Schema definition XSD
Hi all
I just wanted some advice around the new xsd path that should be included in the request XML that is sent to Refinitiv.
This is the URL that we have updated in the XML that we generate
"http://www.refinitiv.com/Datascope/ReportRequest.xsd"
Could you please let us know if you see any issues with this ?
We are also in the process of updating the SFTP connection URL to select.datascope.refinitiv.com.
So, I wanted to check in case there is any significance of what sequence these 2 changes are done ?
Since both old and new URLs are active in parallel from Refinitiv, I think ideally it would not make a difference in which sequence the above changes are carried out ?
Please let me know in case any further details are required.
Thanks in advance
Best Regards
Sid
Best Answer
-
From my checking, both old and new endpoints currently use the new namespace.
<ReportRequest xmlns="http://www.refinitiv.com/Datascope/ReportRequest.xsd">
The new namespace works with both old and new points.
Therefore, you can change the namespace first and then change the connection to select.datascope.refinitiv.com.
For more information, you can refer to the Refinitiv DataScope Select FTP User Guide.
0
Answers
-
Thanks for the quick response and confirming the new namespace.
0 -
Hi, one quick question based on what I asked earlier
Since the old URL's for both schema and SFTP only get discontinued after 31st July, does it matter which URL we change first before 31st July ?
Suppose we are testing this week, would it matter which URL we change first ?
0 -
From my understanding, the URL in <ReportRequest xmlns="..."> could be anything that is a unique name to identify the corresponding elements of the report request file. If you try to access that URL (http://www.refinitiv.com/datascope/reportrequest.xsd), it will return "Page not found".
The important one is the DSS FTP server URL which is select.datascope.refinitiv.com.
0 -
Ok great, so it should not matter then if we update the SFTP URL first, and then update the XML Schema definition URL in the generated request file a little later this week. Since both old and new URLs would be valid till 31st July.
Thanks for confirming
0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛