-
Notifications
You must be signed in to change notification settings - Fork 48
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
Potential Breaking Change in REDCap 13.4.3 #474
Comments
yikes, thanks for the heads up. I'll update and check it out. |
@nutterb, is this a pre-release version? I don't see 13.4.3 on the standard download page. |
Interesting. This happened when Vanderbilt went to 13.4.3. but they may be on some kind of inside track. Maybe this wont be a problem by the time it's available to you? What I do know is that some methods haven't ever worked with that formatting. I have had problems with exportArms and deleteArms. I think exportFieldChoice mapping required the different formatting, too, I think. |
To confirm to anyone listening, today's upgrade on OU's server (to 13.4.10) had some of these problems. I'm working on it now. (@nutterb, thanks for the heads up. It was nice having knowing I had to schedule time to upgrade REDCapR after upgrading the server.) |
For those with access to the Community site, read about this issue here: https://redcap.vanderbilt.edu/community/post.php?id=202055 |
I've heard some reports that in REDCap 13.4.3, there have been a lot of new errors in various packages trying to access the API. It seems to have affected R, python, ruby, etc.
The crux of the issue is how vectors are being passed to the API. paste0(..., Collapse=",") will not work anymore.
See https://github.com/nutterb/redcapAPI/blob/main/R/vectorToApiBodyList.R for a solution that deals with this. This will affect anything that the API designates should be passed as an array
The text was updated successfully, but these errors were encountered: