You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that are obtained when reading data through a .csv file are not avaliable when reading through API communication. The information stored in these columns when using the API method seems to be now at the columns
I don't know if am I missing any functionality or there is any parameter in the rd_transform function that allows to indicate that the data was read from whether one data source or another. So far I have managed to get rid of the issue when fetching data from API by creating new columns with the same format. However, I would appreciate if you could change the function in order to avoid further errors.
Thanks,
Adrian
The text was updated successfully, but these errors were encountered:
Hello,
redcap_data
function seems to return a dictionary with a different format depending on the method chosen to retrieve the data from. The columnsthat are obtained when reading data through a .csv file are not avaliable when reading through API communication. The information stored in these columns when using the API method seems to be now at the columns
that do not have the same name neither the same format
These differences lead to bugs in the
rd_transform
function at the following points of the code:https://github.com/ubidi/REDCapDM/blob/48bcc90d6067da4262cb793f326bab0e280d388a/R/utils-transform.R#L22
https://github.com/ubidi/REDCapDM/blob/48bcc90d6067da4262cb793f326bab0e280d388a/R/utils-transform.R#L143-L146
I don't know if am I missing any functionality or there is any parameter in the
rd_transform
function that allows to indicate that the data was read from whether one data source or another. So far I have managed to get rid of the issue when fetching data from API by creating new columns with the same format. However, I would appreciate if you could change the function in order to avoid further errors.Thanks,
Adrian
The text was updated successfully, but these errors were encountered: