DataSquirrel Contributor

Didn't know quite what the spoiler object would do. I was trying to insert a break-clearl-all sort of thing to make the text and images easier to follow. I'm not great at the formatting system used on this forum, clearly.

Thanks for the answer. Confirmed, I followed those steps several times yesterday, using copy-and-paste for both the subdomain/trunk name and the key. No joy. I'll check with support.

No, I can't see any good reason, past what you mentioned. Pulling data out of Domo, repackaging it, and then pulling it back into Domo is downright perverse. So even though I posted a sample of how to do just that, I'd not promote the idea. We may have other uses for the data but, right now, we don't. And if Domo adds…

P.S The summary count is the sum of is_late_number, one of the calculated columns. That really was a great idea! Very simple to use. I'm going to keep that trick in mind for other situations.

I need to get my head back into a lot of Postgres+Domo work, so I figured I'd dive in here...it's a no-risk problem to solve. I'm excited about checking out the Governance connector, as that's likely what we'll want. But I figured I'd give this a shot and I came up with a visualization that I don't love. I figured I'd just…

I was not aware of of the Governance or DomoStats connectors, they look very interesting. I'll check these out next. I see that the Governance module was only released in December of 2018, so it's probably new for most people here. If anyone else checks it out and has comments, please post back!

Now that is a great idea! I wasn't thinking about the presentation, and would not have come up with something some simple and complete. Now I want to go and write the code to make it happen! Thanks again!

Thanks for the detailed answer! I like your idea of a status card, simple and workable. We don't have so many DataSets now that it couldn't work, but I see your point about scale. You feature requests sound good, I'd vote for them if I found them! I may end up writing something with the API as I've already got the code to…

I've now resolved this issue with Tech Support and want to update this thread for the sake of the archives. Here's the short version: * The Postgres Connector (and probably others) doesn't support pulling data into DECIMAL. Can't be done. * When you migrate a card, you get a DataSet mismatch error. * The difference between…

Thanks for the link! I should have made it clear that I've already been through the documentation and tried searching through past Dojo theads. As I've probably said somewhere, I've written a tool to pull the DataSet definitions via the API so that I can then have a script compare the new and old DataSets. This lets me…

Aaron, thanks for the comments! I'll see if Tech Support has a fix but, agreed, a DataFlow to fix one thing feels really over the top and best to avoid. Thanks

And here's a remedial question from me: How do I specify an output DataSet when trying a column conversion? I managed to find a combination that doesn't immediately fail, but the DataFlow Editor doesn't see any valid input source to build an output from (?) Thanks!

Just as a sample of one of the errors I was seeing trying to convert a string column with values like "82.03" into a DECIMAL. Note that the source string column is populated from a numeric source and that there are no blank rows - so I don't think the problem is an obvious flaw in the source data.

I don't use the Magic ETL features in Domo as I prefer to prepare the data in advance, but I did check DataFlows out a few months back. Super cool UI, very nice. I do not want to use a DataFlow in this case because it makes our setup more complicated...but I figured it's worth a try. I can't get it to work. I get…

@AS wrote:What data transfer method are you using to pull from postgreSQL? Are you using the API connector in the Domo web interface? I'm not aware of a way to override datatype coming out of those APIs. Could you possibly use Workbench and an ODBC connection and DSN on that server to connect to your database? That would…

Thanks for answering! It sounds like I wasn't clear. We were using Workbench, we are moving to a Postgres pull. With our running setup on Workbench, the data comes into Domo as DECIMAL. I haven't been able to find any way to match that with the Postgres pull. I've tried every base numeric type in Postgres (smallint, int,…

Thanks for the quick answer! Here's what I think that I've seen from some simple experiments: * You can a warning if field names differ, even case-sensitively. I don't think that Domo normally treates names case-senstiively, but that brings up the warning dialog when you migrate. * Beast Modes seem to magically be…

I'm researching what's involved in migrating many cards to a series of new DataSets and ran across this thead. It's marked as solved, but not soultion is mentioned. Is this still an open issue? Thank you

I've been checking the docs and they note that CSV is currently the only supported upload format for the DataSet API. I'm still curious about real-world experience with this API, if anyone cares to share.

ODBC even makes me spell wrong. Like I said, I'm allergic to it. 

Okay, I took the suggestion to post in the Ideas forum and updated an existing request for spark line support: https://dojo.domo.com/t5/Ideas-Exchange/Sparkline-support/idc-p/34200#M6539 If you also want real spark lines/bars/etc., please comment and vote over there.

@rado98 wrote:I think you are right (specially about side by side graphs), however you should probably post this in ideas exchange or something like to hopefully get things changed/improved Thanks for the answer! I feel bad about sounding harsh since the folks at Domo seem universally quite nice. The links I posted…

Thanks! I havn't tried SQL Transforms, so here's a good excuse to try them out. That will put me in a better place to decide if we should prep an extra DataSet on the outside or do it in Domo. Thanks again for all of the help!

As it turns out, this is what I actually need to do today. Just find the most recent row. Our data set is mostly used to find _trends_, but sometimes we want to find _status_. The current/latest day gives us a snapshot of the current status. I don't see anything like a TOP or LAST function in the Beast Mode reference, or…

Great answer, thanks for the reply! Given that, I'd probably be better off biulding a one-row data set to push into Domo. The code will be similar to what you propose, but we're currently aiming to keep most of our data prep logic outside of Domo. I know, that's not the Domo way...but it's working well for us so far.…