RDP News in HTML format

we are no longer receiving stories in HTML format. We use the following code for retrieving a story:
try
{
Stopwatch timer = new Stopwatch();
logger.Debug($"Retrieving story id {storyId}");
timer.Start();
var storyDef = Story.Definition(requestStoryId);
if (isHtml)
storyDef = storyDef.HtmlFormat(true);
storiesAPIRequests.Mark();
var story = await storyDef.GetDataAsync();
timer.Stop();
if (story != null && story.IsSuccess)
{
logger.Debug($"Retrieved story for {storyId} in {timer.Elapsed}");
newsStory = new NewsStory
{
StoryId = requestStoryId,
Story = story.Data.NewsStory,
ContentType = story.Data.ContentType,
Retrieved = DateTime.Now
};
}
else
{
string error = story != null ? story.HttpStatus.ToString() : "Unknown";
logger.Error($"Unable to retrieve story {storyId} due to {error}");
}
}
catch (Exception ex)
{
logger.Error($"Failed to retrieve story for {storyId} because of {ex.Message}");
}
The key call here is storyDef.HtmlFormat(true) which should tell the Refinitiv Data Library to return the story in HTML. The HTML would use styles such as scs_html_header which are in the documentation and which allowed us to format the story appropriately. This was working fine in the past, but now no longer does and simply returns the story in text format, which completely destroys the formatting of a story and makes it almost unreadable.
client screenshot rdp news.png
Is there a reason why this is no longer working?
Best Answer
-
Hi @mary.villa
It appears the News Story service has change it's interface. Apparently, the response has changed and now automatically delivers both text-based and html-based data. As a result, the service ignores the HTML specifier. I'm surprised the service did not update the version of the endpoint to protect against change - this is why endpoints have versions so you don't break existing applications.
That being said, the next version of the .Net Library will remove the Html specification and include properties that can extract both text and html content.
In the meantime, you can process the Raw data to pull out the HTML content. For example:
var story = Story.Definition("<story ID>").get_data();
...
var html = story.Data.Raw.SelectToken("newsItem.contentSet.inlineXML[0].$")?.ToString();0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛