-
writing to datasets
We are running into issues writing to a domo dataset from a custom app. Is that expected and if so, is our only option to create a shadow json doc to write the dataset and the new field to? Thank you
-
gauge with custom tick marks with values showing
Its possible I am missing it, but I went through all the gauges and settings and did not see how to do this: 1) a gauge with visible numbers for the tick marks 2) Tick marks that are custom values (ideally supplied in the data set, but even manually entered in the settings would be fine) The idea would be to see the tick…
-
Weird warning "This DataFlow is incomplete" on QBO connector
So we run the Domo Cloud Connector quickbooks online (and advanced) and often get this warning, even though the dataflow shows as having run 100% successfully. "This DataFlow is incomplete". It is odd though, after waiting about 10 minutes, the output dataset does show up. Also, why the huge lag for datasources (even small…
-
Quickbooks Online - received $ transactions
Hello, we are trying to get our received $ transactions at the lowest level of detail /and at day level from quickbooks online with domo cloud connector(s). To be clear we are not talking about invoices, but rather paid invoices (e.g. deposited in the bank, so QBO registers it as a paid invoice in QBO). Can anyone give me…
-
expected beast mode behavior?
In trying to debug a beast mode issue, I created a simple beast mode: sum(1) Now, when I put that on a single value card, it displays "179". This is the same behavior whether or not I use an aggregate function. Can anyone explain that behavior? Screengrabs attached:
-
odd beast mode behavior
Hi- as I was creating a beast mode, I saw that it works great in a single value card, but uses the wrong values in the summary number- same exact beast mode. Any idea on why this would be? See syntax below. The single value renders the (`Opp Value`)*.05 correctly, whereas the summary number disregards the beast mode calcs…
