need to connect to workspace via RStudio.

I need to connect to workspace via RStudio. Il installed Refinitivr package and i run this command with my API Key found in APPKEY :

RD <- RDConnect(application_id = "<app key>", PythonModule = "JSON")

I get this message :

Erreur dans RefinitivJsonConnect() : Please supply Eikonapplication_id.

Screenshots:

Find more posts tagged with

#technology

#product

Accepted answers

All comments

Jirapongse

@Vikram_2910

Thank you for reaching out to us.

First of all, we don't provide any libraries for R and that library was developed by the third party which we don't support it. The client needs to use our LSEG Data Libraries instead which support Python, TypeScript. and .NET.

For this issue, the client may try to call the EikonConnect before calling the RDConnect. For example:

Eikon ← EikonConnect(Eikonapplication_id = "<app key>", PythonModule = "JSON")
RD ← RDConnect(application_id = "<app key>", PythonModule = "JSON")

laurens

Hi everyone,

Laurens here, maintainer of the RefinitivR package on CRAN.

The root cause is still the same: RefinitivR today can only authenticate via a locally running Workspace/Eikon desktop application. It has no working code path for the cloud-based/online Workspace terminal, which is why users keep hitting the “Please supply Eikonapplication_id” error in pure-cloud setups.

I am genuinely happy to implement and maintain proper cloud support in RefinitivR (in fact I’ve wanted to do it for years), so that R users are no longer forced to install and run the desktop client just to get data.

The only thing stopping me is very simple: I do not have access to the web-based Workspace/CodeBook environment. My licence is desktop-only, and LSEG has never provided maintainers of the open-source R package with a cloud licence for testing and development purposes.

So, to LSEG/Refinitiv representatives reading this:please just grant me (for the RefinitivR project) a regular cloud-based Workspace licence so I can actually test and ship a proper cloud-compatible connector. Once I can log in and validate the session handling myself, I can have a working implementation out in weeks rather than years.

Until that happens, the limitation will remain, through no fault of the package or the R community.

Happy to take this offline with the product/developer-relations team if needed – just let me know whom to contact.

Thanks,LaurensMaintainer – RefinitivR package

EXPLORE OUR SITES