@cmendolsohn

I am using 1.0.0-beta5 and it can return that news story properly.

However, after downgrading to 1.0.0-beta4, I got null for this news story.

 var story = Story.Definition("urn:newsml:newsroom:20230710:nNRAp6cmnn:0").GetData();

                            Console.WriteLine($"\nHeadline: {headline.Data.Headlines[0].HeadlineTitle}");

                            if (story.IsSuccess)
                            {
                                Console.WriteLine($"\nStory (Plain text): {story.Data.NewsStory}");
                                if (story.Data.NewsStory == null)
                                {
                                    Console.Write("\nBlank Story");
                                    Console.ReadLine();

                                }
                             
                            }

Nick is correct. Please upgrade to 1.0.0-beta5.

@cmendolsohn

Thank you for reaching out to us.

I can run the code properly with a Console application and .NET Framework 4.8.

You may need to enable logging in the API to verify what the problem is.

using Refinitiv.Data;
...
Log.Level = NLog.LogLevel.Debug;
Log.Output = (loginfo, parms) => Console.WriteLine($"Application: {loginfo.Level} - {loginfo.FormattedMessage}");

You can enable network tracing in the .NET Framework by adding the following configurations in the App.config file.

<configuration>
...
<system.diagnostics>  
    <sources>  
      <source name="System.Net" tracemode="includehex" maxdatasize="102400">  
        <listeners>  
          <add name="System.Net" />  
        </listeners>  
      </source>  
      <source name="System.Net.Cache">  
        <listeners>  
          <add name="System.Net" />  
        </listeners>  
      </source>  
      <source name="System.Net.Http">  
        <listeners>  
          <add name="System.Net" />  
        </listeners>  
      </source>  
      <source name="System.Net.Sockets">  
        <listeners>  
          <add name="System.Net" />  
        </listeners>  
      </source>  
      <source name="System.Net.WebSockets">  
        <listeners>  
          <add name="System.Net" />  
        </listeners>  
      </source>  
    </sources>  
    <switches>  
      <add name="System.Net" value="Verbose" />  
      <add name="System.Net.Cache" value="Verbose" />  
      <add name="System.Net.Http" value="Verbose" />  
      <add name="System.Net.Sockets" value="Verbose" />  
      <add name="System.Net.WebSockets" value="Verbose" />  
    </switches>  
    <sharedListeners>  
      <add name="System.Net" type="System.Diagnostics.TextWriterTraceListener" initializeData="network.log" />  
    </sharedListeners>  
    <trace autoflush="true" />  
  </system.diagnostics>  
...
</configuration>

With these configurations, the network.log file will be created. You can check the HTTP response of the News Story request.

Hi @cmendolsohn

I would recommend you download the latest example package which includes release notes for changes in this release. You can try isolated examples to confirm behavior. Regarding "news streaming", can you elaborate what specific API/Example you are referring to? The main News change was to react to the changes in the Desktop News Story extraction. I would try example 2.3.03-News-Story in the new package to confirm expected behavior.

After upgrading Refinitiv.Data Nuget package to 1.0.0-beta5, I am now able to get a response from the server that includes the story's Body. To answer @Jirapongse previous issue of why some news items will not retrieve a Body, if the news source is a Web News source "urn:link:webnews", the Body will not be available, which I guess is expected behavior because even in the News Monitor tool, selecting a Web News item opens an external browser link.

I'm currently trying to optimize performance, and instead of querying for the StoryID using Headlines.Definition().Query() (which introduces additional latency), I'm trying to directly create the StoryID as such, where PNAC is the "PNAC" field of an incoming news item from the Pricing Library's news streaming mechanism.

string storyID = "urn:newsml:newsroom:"+ DateTime.Now.ToString("yyyyMMdd") + ":"+PNAC+":0".

Can I get confirmation that this is the proper formatting of the StoryID used to find a News Story, and what is the ":0" for? In what scenarios is it not ":0"?

Moreover, using this workflow seems to run into significant performance issues, as the news item's Body will not be available for retrieval by the server (404 Story Not Found error) until at least 2-3 seconds after the headline is picked up by the news streaming mechanism. Is there anyway to overcome this performance issue? It doesn't seem right that the News Body takes 2-3 seconds to be available after the headline is available.

Hi @cmendolsohn

I'm glad you were able to get the news story.

Regarding the creation of the story ID based on the streaming field, I would suggest you reach out to a News content specialist as they can confirm your approach and to better understand the delay you are experiencing with the story. You should be able to access a content specialist via the Refinitiv Helpdesk.

@cmendolsohn

The number after PNAC could be the version number.

However, I could not find it in the document. Please contact the content support team directly via the Refinitiv Helpdesk to confirm this, as mentioned by my colleague.