Comments
-
Hi Roxanne, When you make your changes, like moving a labe or a widget, do you make sure to grab all layers for that object? The presentation layer with the visible object has a corresponding invisible layer on most widgets that is exported when uploading the artboard to domo. Jake G
-
Please do, let's get this working for you. You can send me a private message by clicking on my profile name and then on the right side click on send this user a private message.
-
Yes my mistake, this should hopefully do the trick. You just state the aggregation prior to the groupby. stringQuery= '/data/v1/dataSetAlias?fields=alias1,alias2,alias3' + '&sum=alias3&groupby=alias1,alias2,alias3' + '&orderby=alias3 descending';
-
Have you tried : stringQuery= '/data/v1/dataSetAlias?fields=alias1,alias2,alias3' + '&groupby=alias1,alias2,"sum=alias3" + '&orderby="alias3" descending'; When a groupby is present, you only want to specify the aggregation operator inside the group by clause. Let me know how this goes.
-
domo.get is doing just that, referencing by alias to production datasets you specify in your manifest.json file. Have you logged into the instance your manifest.json is referencing with domo login in the cli?
-
Hi there, The issue is that you cannot load 'plugins' inside of a sandboxed iframe. When reading this document, the DOM needs to load a plugin to be able to read PDF files. This will work fine in `domo dev` since that iframe is not sandboxed. In production however, we sandbox the iframe to keep things secure. There are…
-
Could you send me the TOE associated with the broken card? From there I can better diagnose.
-
https://github.com/DomoApps/starter-kit Here is an implementation using webpack with an angular framework. You can reuse the webpack loader and just swap out the angular framework with your react implementation. Let me know if there are any bumps you run into along the way.
-
Oops, it is actually named something different than domo.js in the public domain. Change domo.js in the npm file to "ryuu.js": "^2.5.8" under dependencies. Then just change your imports or requires to look at ryuu rather than domo. As for your second question. domo login will need to be called anytime your session expires…
-
This usually happens when you have an old widget that is no longer in use on your artboard, usually an invisible layer. Do a quick sweep in the Design Studio "Edit Widgets" tab of all of your widgets and make sure they are all up to date and in use. If there are some that aren't, target them and remove ALL of the layers…
-
Could you attach the AI file of the app? I could take a look.
-
It should be as simple as requiring it or importing it in the top of the file you want to use it in. commonjs: const domo = require('domo.js'); es6: import * as domo from 'domo'; If you are using npm and have a package.json, include domo.js as a dependency.
