domoinc-r / domor Goto Github PK

When I upload a data.frame using this class my R session aborts every time and the replace does not complete. Eventually the Domo dataset refresh times out after 8-9 hours.

Hello!

I am running some old code, specifically fetching data from my instance, and I'm repeatedly seeing:

Error in DomoR::fetch("XXXXXXXXXXXXXXXXXXXXXXXXX") :
Not Acceptable (HTTP 406).

Anyone else having this problem?

Hello,
Are there any future plans to add a nrows parameter to the fetch() method?

some of our tables are over 27MM rows, and it crashes R over and over again.

This is NOT a usable solution for export.

Attempting to update a data set in Domo using the replace_ds function which throws a HTTP 400 error. This function works fine within the same Rmd file for other datasets, so authentication and setup is not the issue. The dataset is not overly large so it should not be throwing any errors.

Hi, I run into the following installation issue. Can you please help resolve?

install_github(repo="domoinc-r/DomoR", auth_token = "")
Downloading GitHub repo domoinc-r/DomoR@master
2 [main] tar 9852 fstab_read_flags: invalid fstab option - '0'
Error: Failed to install 'DomoR' from GitHub:
Does not appear to be an R package (no DESCRIPTION)

Anyone else run into issues with Domo fetch coercing character or numerical characters to logical when importing to R Studio? How do you keep this from happening?? I've submitted a ticket with Domo Support but also checking with the network here.

Hi,

This is what I get after installing devtools and trying to verify if it has been installed correctly.

has_devel()

"C:/PROGRA1/R/R-331.3/bin/x64/R" --no-site-file --no-environ --no-save --no-restore --quiet CMD
SHLIB foo.c

Warning message:
running command 'make -f "C:/PROGRA1/R/R-331.3/etc/x64/Makeconf" -f "C:/PROGRA1/R/R-331.3/share/make/winshlib.mk" SHLIB="foo.dll" WIN=64 TCLBIN=64 OBJECTS="foo.o"' had status 127
Error: Command failed (1)

Can you help resolve this?

Thanks!

Getting an issue fetching a dataset. Never had an issue with this dataset before. Just using:

DomoR::fetch('--dataset id here--')

returns

Error: col_names must be TRUE, FALSE or a character vector

I tried adding a vector of column names but I get the same result.

I am using the DomoR package with R to edit and upload data sets to DOMO. When I try and use the "create" function to create a new data set in DOMO or the "replace_ds" function to replace a DOMO data set, I get a "Bad Request (HTTP 400)" error. Any advice?

typeConversionText appears to only work with dataframes. If a dataset is not in the expected format (e.g., is a tibble), then the table created on Domo will have a schema of all text.

Would be very useful if the fetch command did not have to pull the full data set into memory but allowed a preview of the data to be fetched.

DomoR fetch() function does not return the identified dataset. The same error message seems to appear for all datasets regardless of displayType (dataflow, datafusion, etc.)

df <- DomoR::fetch(1)
# Error in readr::read_csv(x, locale = readr::locale(encoding = encoding),  : 
# unused arguments (check.names = FALSE, na.strings = "\\N", colClasses = c(NA, NA))

Get I error when try to run on 3.6.3 as Domo is not available

For some reason, I'm unable to create a data set with data in it or replace that dataset today.

I can fetch data fine. I can even locate my new datasets with list_ds. But every new dataset I create with this script shows up in Domo with no data (R has it and will write it to an excel for me, so at least I have a workaround) and every time I try to update the dataset with replace_ds I'm told there's an error. R is unable to find the stream for this particular dataset.

It seems to be an issue within this particular script too, though I can't imagine why. Other scripts I ran this morning did not have an issue with replace_ds, and copy/pasting to a new script nor a computer restart helped. I can't find anything that makes this particular dataset, or any dataset created in this script, different than others.

Has anyone else experienced this?

DomoR::fetch does not treat trailing whitespaces the same as domomagic::read.dataframe() or read_csv

When I load a CSV file into a domo data set trailing whitespaces in the data in a column are retained, i.e., "string " remains "string " not "string".

When I then read this data set in a Magic R scripting tile the trailing whitespace is retained, i.e., I use
library('domomagic') read.dataframe()`

However if I read this in DomoR the trailing white spaces are stripped off, ie use
library('DomoR')
fetch()

If I read the CSV directly using read.csv() this retains the white space unless I add "strip.white = TRUE."

This creates a problem when moving from developing in an IDE to production in Magic R tiles.

R version 3.5.2 (2018-12-20)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Debian GNU/Linux 10 (buster)

Installing DomoR's latest commit c2bc1d6 is failing.

install_github(repo="domoinc-r/DomoR")

throws error

Error in parse(outFile) : 
  /tmp/RtmppmX8GO/R.INSTALL856881d54e/DomoR/R/replace_ds.R:172:18: unexpected symbol
171: lookup_stream <- function (dataset_id) {
172:   search_stream('dataSource.id

Installing the previous commit works fine.

install_github(repo="domoinc-r/DomoR@d3b659602565bf0f676f57481a6445d3fea41f41")

Hi there,

I think this ```, auth_token="<auth_token>"`` part is unnecessary from here:

Installation method from GitHub
You can install directly from our private Github repository:

install_github(repo="domoinc-r/DomoR", auth_token="<auth_token>")

When most people are used to this and it works fine without specifying the auth token. Perhaps this simpler method could be provided as an alternative to not confuse people who don't specify auth_token as you specify

install_github(repo="domoinc-r/DomoR")

Hello, is there a way of writing the data to disk and avoid memory issues relating to the RAM?

When I use the fetch_to_disk() function the data gets written to disk, but it still runs into memory allocation limits relating to the RAM instead of the disk:

Does anyone have a solution to this that enables to write a .csv file to disk directly and not the RAM? Or batch the writing of the file so it avoids running into this issue?

Would really appreciate any help figuring out how to export a really large dataset to disk!

This is a comment for test issue

HI..I am following the exact code but it's not forecasting the six months data. With this code, I am getting data till available date only.. any help?