-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time series list request #40
Comments
Hi Abigail The request works for me:
I suggest that you restart your R session and change that you have the latest version of the package from CRAN:
You also might want to check that you are permissioned for this data by downloading it in Excel. |
Hi there I have access to this through excel so I don't think it is a permissions issue. Tried updating the package and the command still fails with the same error. I can pull through each datatype in separate requests but cannot pull in one single command? Thanks |
do you have the chunkLimit set to 50L? |
Changing chunkLimit to 50L for me replicates the original error for me. Here is a workaround where only one datatype is requested at a time and then these are combined into the final list.
|
Hi This work around doesn't seem to work for me either - I get the same server error. I will try reinstalling and see if there is anything in my setup that could be causing these issues. Thank you for the help and suggestions thus far though. Abigail |
My bug is fixed in v1.7.10, now on Github. It can be installed with:
|
Just following up. This seems to be an intermittent issue. I just detatched the package then required it again and the time series requests are working now? Thanks |
Hi there
I am trying to pull through a time series of a number of datatypes for a list and I keep getting the following error.
Command in R: testfords <- mydsws$timeSeriesListRequest(instrument="WSUS1",datatype = c("WC18198","WC01084"),startDate = "-2Y",endDate="0Y",frequency = "Y")
I have been assured by Refinitiv that this should be possible, am I doing something wrong?
Thanks,
Abigail
The text was updated successfully, but these errors were encountered: