cr1ckt 🟠

About

Username
cr1ckt
Joined
Visits
0
Last Active
Roles
Member
Points
159
Badges
3

Comments

  • @JustAGirlyGeek: It's possible that an update has broken my workaround since I tried it, but I was referring to the fact that an input DataSet must exist to be selected as the source of the input in the Magic ETL. Therefore, when I am creating the new ETL (and new output DataSet), I have to run it once to get an empty…
  • I think it would make sense to be able to provide an unaggregated series value to split by, with the same per-series color configuration you get with the bar charts (I think a "grouping name" is what you called this). Additionally it might be nice to be able to check a box in the card configuration to group words of a…
  • I think I was specifically talking about a date field filter being added via the Analyzer. End users have the ability to choose relative date windows on the configured date range field via the date range selector, but the filter options an arbitrary date field in the analyzer are much more limited and do not support ranges…
  • No, I think that's a great idea. Assuming that the bulk select and "Run now" is supported by DataSets that are maintained via a Workbench upload, the feature you described is exactly what I'm asking for.
  • I'm using the newest version of workbench 4. Specifically I'm asking for the ability to flag a Domo DataSet in the web interface to request another job run. I would expect that the workbench would poll for target DataSets with this flag periodically and execute the jobs supplying those targets. I don't know how feasible…
  • Assuming January 2nd 2016 at 1:34:34 PM: 01-02-2016 01/02/2016 01-02-2016 1:34 PM 01-01-2016 13:34:34 Jan 01, 2016 1PM (for queries by hour bucket) I imagine separators and ordering varies by locale. Not sure if the (Javascript?) formatting library would support symbolic separators for date/time fields.
  • @ckwright I've sent you some examples ?
  • This request was a little generic, but the "field filter" functionality I'm talking about is pretty much the filter input field you get on the left-hand side when looking for fields in the card builder. Some other places (e.g. many column selections in Magic ETL transforms and the field selector for the summary number on a…
  • Ticket number with Domo support is 01774551
  • I would second this option.
  • I would like to second this feature, although it seems that it is possible today to create an arbitrary beast mode calculation using count distinct rather than a simple count. Specifically, I would like to see count distinct as an aggregation option when adding values/series to a card configuration, so that it is not…
  • Sure, you just add your column names with the dynamic values into the concat list like so: CONCAT('<a href="', 'https://www.myinternaldomain.com/linkforitem', '"><img width=40 src="https://www.myimagehost.com', `column_name_with_relative_url_to_image`, '" title="', `column_name_with_title`, '" /></a>') I believe you need…
  • Yesterday I learned that it is possible to provide an HTML column for the table card itself. (The instagram pre-made app has an example of a beast mode column that does this.) I believe that sumo tables and final drill down tables still lack this ability though. There might also be some overlap between this and more robust…
  • After some time, it seemed that a page refresh would no longer bring back the original group name/membership count but it would bring back the new name with a count of 0 (the actual count is 5). This strengthens my belief that some form of caching/eventual consistency issue is at play
  • "A column in this calculation did not exist." It would be really cool if the name of the missing column was included in this message. It also is a little cumbersome to track down the beast mode field breaking a card. It would be even cooler if a specific error message bubbled up to at least some card level view, even if it…
  • Yes I do have access to the MySQL DataFlow. Thanks for taking a look at this.
  • Sure Matt, The problem is that I need to fuse one BlogPost record with three different records from the user table (the author, the editor, and the manager). In most SQL engines, you achieve this by joining the user table three times with different foreign keys and aliases for each join. select * from BlogPost b join users…
  • Oh I did not know about CC'ing through mentioning. Thanks for the tip ?
  • I believe you can achieve this via either the edit data -> remove duplicates or edit columns -> group by transformations. Your preference might be driven by what you want to do with the data that gets thrown out. Selecting just the date column and removing duplicates should give you a set of distinct dates in the original…
  • It looks like sumo tables and the drill down tabular view also suffer from this issue (I only see the DataSet name and an ellipsis for every column name in my table view). It would be nice if there was a way to see the column names at the end here.
  • A lot of the field selectors in the Domo application have a fixed width, which can make it difficult to see the actual column name when there is a DataSet name prefix. This becomes a frequent issue when using DataFusions as the source for a card, since they automatically prefix column names with the original DataSet…
  • I would second the importance of being able to promote/demote. Right now, I'm holding off on refactoring my page organization in the hopes that a streamlined process for this gets released.
  • For any interested people out there, I was able to provide a tampermonkey/greasemonkey userscript solution to my end users by injecting jquery and running this once it's loaded: function checkForImageLink(e) { if (e.target.innerHTML.indexOf('/item_images') === 0) { $(e.target).html('<img src="https://www.artfulhome.com' +…
  • A great place to start with this would be to allow a sumo cell to be formatted as an image tag. I have merchandisers that would really benefit from being able to take image urls provided in an uploaded DataSet and use them to generate an img tag loaded from our website.
  • It sounds like this use case could also benefit from some kind of anomaly detection tracking the data set size over time. If I join data source A with data source B every day to get Data fusion C and suddenly the size of C drops by 60 percent while A and B sizes are stable, that would be a red flag that something odd has…
  • I would second that being able to have more specific control over how drill paths are triggered and what filters they generate on drilled views would be a great way to add a lot of power to what Domo can do with its presentation layer. For instance, I recently created a stacked bar graph showing how different segments…
  • Not sure if this is being implemented by the project for this, but have an upvote.