question

Upvotes
Accepted
robin.ameloot avatar image
5 ●0 ●0 ●1

Different results from get_data request depending on session type

Hi all,


I was previously helped by being shown the difference of a desktop session vs platform session and wanted to convert my rd.get_data() requests to exploit the benefits of a platform session over a desktop session.

In doing so I've encountered two anomalies I wanted to see if I could get some clarity on.

1) Parameters

Using the same list of fields and associated parameters resulted in multiple errors. As I'm working off old code form a colleague I'm not sure what all the parameters do, but it seems weird that parameters passed using a desktop session cause errors when using a platform session.


I found that 'CH', 'RH', 'NULL' and 'Transpose' throws a 'Error code -1) error.

2)

Omitting these erroneous parameters allowed me to extract the data but I noticed another difference. I'll illustrate with the two sections of code shown below:


1707836654480.png

1707836671573.png

the sole difference (to my understanding) here being that the top snippet is using a default desktop session and the bottom a custom platform session.

The results of these snippets differ in that the top will return all years even if there is no data available (desired output), whereas the botton snippet only returns data for the years where data is available (undesired outcome).

My question is whether these problems are caused by a fault from my side? If not, what is causing this or in what way can I best remedy this?


Thanks in advance!

rdp-api#product#content
1707836654480.png (8.4 KiB)
1707836671573.png (11.1 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

raksina.samasiri avatar image   raksina.samasiri

<AHS>

This is related to an existing bug

I've follow up in the email thread RE: Issue with returned data using RDP DataGrid endpoint || Misaligned rows - another case found in 2024 will keep this question updated

1707883609959.png

1707883609959.png (276.3 KiB)

2 Answers

· Write an Answer
Upvotes
Accepted
Jirapongse avatar image
79.2k ●251 ●52 ●74

@robin.ameloot

Thank you for reaching out to us.

Yes, you are correct. The results are different. I used the following code.

rd.get_data('LVMH.PA',['TR.CashInterestPaid.fperiod','TR.CashInterestPaid'],
            {'SDate':'FY0','EDate':'FY-32','Period':'FY0','Frq':'FY','Scale':6})

This is the output form the desktop session.

1707883236842.png

This is the output from the RDP session.

1707883308576.png

However, this developer forum is for questions on and general discussions of Refinitiv APIs.

To verify the content, please contact the helpdesk team directly via MyRefinitiv.

I have tried to submit this issue on your behalf but the system didn't create a ticket number. Therefore, please try to submit this issue via MyRefinitiv.


1707883236842.png (29.6 KiB)
1707883308576.png (20.5 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Jirapongse avatar image Jirapongse

@robin.ameloot

Now, I can sumit this query on your behalf. The case number is 13307519.

The support team will contact you regarding this issue.

robin.ameloot avatar image robin.ameloot Jirapongse
Thank you very much!
Upvotes
robin.ameloot avatar image
5 ●0 ●0 ●1

For those curious as to what the results look like I've attached the results for a default desktop session below:

1707840640579.png

And the results for a custom platform session below:

1707840607220.png


the problem caused here is that when extracting multiple variables in a single get_data() call the data and years don't necessarily matchup meaning the data in the dataframe is in essence worthless.


1707840640579.png (30.5 KiB)
1707840607220.png (21.3 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.