Last Active


  • Hello @Matz1 It looks like a different issue. My problem is not that I cannot create datasets, it's that the API is not behaving as per the API documentation. I haven't tested yet to see if this is still an issue, since I am currently not using the API for anything.
  • Hey @ilikenno That's a no-go unfortunately. My sample code is from the Domo SDK, which runs client-side, and does not use oauth at all. In fact, I've tried authenticating via api.domo.com using clientside JS running in an SDK app, but that fails because of the cross-domain policies.
  • Not quite @LizWR :( I'm not able to route anything through an external service like @tannerb suggested - this all has to be self-contained in an SDK app. I got ahold of some sample code for making updates to datasets directly from an app, and when I ran it, it failed out with this message: {"status":400,"statusReason":"Bad…
  • It doesn't look like Domo is respecting that header field. I used your code to hit a debug endpoint of mine, and this is what came through: Array ( [_SERVER] => Array ( [CONTENT_TYPE] => application/json; charset=utf-8 [CONTENT_LENGTH] => 261 [HTTP_USER_AGENT] => okhttp/3.2.0 [REQUEST_SCHEME] => https [GATEWAY_INTERFACE]…
  • Thanks for the response! All my questions have been answered, thanks ?
  • Hey @product_John - I'd love to help test that out! Just let me know when it's ready to go ?
  • I already have answers for the first 3: 1. Connectors are published to all Domo customers, but are only accessible with a GUID url unless the connector is deliberately made visible in the customer's instance. 2. There is a delay, anywhere from 1-30 days depending on the current workload 3. There is no way to define…
  • Hi @alexpeay yes I am, and I'm having some trouble with updating and deleting datasets incidentally: https://dojo.domo.com/t5/Domo-Developer/API-Inconsistencies/m-p/14096#U14096
  • @manuwell There's two steps to uploading 1. Is to create the schema, which you have already 2. Is to use the Import route: https://github.com/woganmay/domo-php/blob/master/src/DataSet.php#L74 You'll want to PUT to /v1/datasets/{GUID}/data, specifically with the Authorization and Content-Type headers, and send your CSV data…
  • Hey @manuwell What sort of scripting environment do you have on your side? I'm working on an unofficial PHP client for the Domo Data API, which currently supports creation and uploading of datasets.
  • I'll give that a go in my cloud dev environment, thanks!
  • I just tried setting it up on a brand new Linux Mint installation. I used the jessie/sid repository versions of Node, and ran into the same problem with the domo app - taking out "env" fixed it. I'm going to rebuild the machine and try installing Node directly from their repositories.
  • Hi @product_John - I don't think it's as much about supporting cloud9 specifically, but more nvm generally, which is used pretty widely in the node community: https://github.com/creationix/nvm . I'll be trying to set up Dev Studio on a pure Linux machine later today, and will test if nvm is really the cause. And yes! Reach…
  • I'm definitely an admin on the appdev-acceleration.beta.domo.com instance.
  • I still get this error when installing the latest version of ryuu: npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to [email protected]^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.