ckatzman Contributor

Comments

  • Here's a link to an older thread on this topic. https://dojo.domo.com/t5/Card-Building/Stacked-Bar-Chart-Sorting-Incorrectly/m-p/12433#U12433
  • I presume a - f are individual field values? I presume you've created a distinct Beast Mode for Series 3 to sum all of the a - f values? Are you creating a distinct beast mode calcs for your Series 1 & 2 results, or doing that as a CASE since the results a - c and d - f are mutually exclusive? Then in SORTING, are you…
  • That's an interesting idea, Aaron! Saying it back to make sure I understood your methodology. Please correct me if I misspeak here... Workbench job with a dummy dataset, leveraging the workbench scheduler to only run once/month. Then attach that dummy dataset in some innocuous way to the primary dataset within a workflow,…
  • @DaniBoy, is there a dojo protocol for being able to reach out for help from someone at DOMO when the Dojo has been unable (either no one has seen the question, or no one knows the answer) to provide a solution? Is that just a matter of redirecting the inquiry to DomoSupport, and if so, is there a way (an @name) to be able…
  • Try this... https://dojo.domo.com/t5/Beast-Mode-ETL-Dataflow/Conditional-formatting-of-Columns-in-a-table-view-card/m-p/12495#M881
  • Thanks, @AS. I think I had actually found it, as it was already checked when I went to take a look. But the real mystery may be why it's NOT rotating the labels. It would seem to me that an overlap problem does exist. I could solve it by shortening the displayed timeline or rolling up to quarters instead of months, but…
  • @klicks, be sure to understand the difference between Move/Copy, and Duplicate. Move/Copy allows you to either pick up and re-locate a card, or to spawn linked-copies to other locations. Change it one place, it changes all the linked copies. Duplicate will create a clone of the original card, but it is self-contained. Good…
  • @DaniBoy, it's already there... https://dojo.domo.com/t5/Ideas-Exchange/Control-which-columns-show-up-in-list-for-filtering/idi-p/1490 and https://dojo.domo.com/t5/Ideas-Exchange/Allow-Card-Builders-to-hide-fields-in-Analyzer/idi-p/13478
  • @product_John, any insight you or one of the PMs can share? 
  • Combining a conditional test, and an aggregation, could be a simple matter of wrapping a CASE statement in the appropriate aggregation function. Ex: SUM(CASE WHEN `TEST` = 'TRUE' THEN 1 ELSE 0 END) That case could be much more involved with multiple tests, or even nest a CASE within a CASE if you have a two-layer (or more)…
  • I am not familiar with HTML myself, but there are numerous examples of HTML related inquiries and responses within the Dojo, which can be located by searching "html formatting". In addition to the one previously provided, here is another that appears to provides some examples of code and results images.…
  • @crocija, there was a previous post in the Dojo that showed an example similar to what you are trying to do. Take a look at the post at this link and see if this helps you in the right direction. https://dojo.domo.com/t5/Beast-Mode-ETL-Dataflow/Number-formatting-when-using-HTML-conditional-colors/m-p/14272#M1083
  • If you submit it, I'll vote for it. I've had the same thought about just letting a table card roll to multiple pages if necessary due to length. May just be card builder responsibility to make sure the columns fit, but the rows should just flow to extra pages if needed. Good luck!
  • Got it. What kind of conditional formatting are you applying? Still thinking in terms of an Excel output, and while not as aesthetically pleasing, perhaps you can accomplish the same net effect by creating some sort of flagged values in a Beast Mode column to draw attention (as opposed to color highlights, or something…
  • @theCliffs, how are you "publishing" your table card? If you are exporting an extensive table card in a PowerPoint format, then I have experienced the same issue, and opted to switch to a different medium, Excel being the obvious choice. If you are using "Publications" and a link for the users to access, then that may be…
  • We import all of our date data in the 'YYYY-MM-DD' format, though i will admit that we do not use Google Spreadsheets. The one thing i note from your date example, is it looks like maybe you are doing YYYY-DD-MM... (ie, there is no month 13) The other thing you could try is pulling the pieces apart and using the…
  • I had a similar issue a couple of months ago. I put in a ticket with DomoSupport, turned out there was something corrupt behind the scenes that they were able to resolve and my Output dataset was fine thereafter.
  • For every inquiry you can see on this topic, there are probably 100 more that haven't spoken up. Hiding in the walls, like roaches...
  • Can you post an example of the format that your date field values are showing? Do they look like properly formatted dates, but they didn't pickup a date data type during import, or are they representative of dates but not in a date format (ex: 20160720).
  • Add the date field that represents your X-axis value to the Sort criteria in edit mode, select Ascending, and depending on your card you'll need to determine whether it's No Aggregation or which Aggregation to use. Most likely, No Aggregation. If the date value you are uising is not a Date data type, then you may want to…
  • I don't think it's a move so much as a re-enter in the correct area (link here: https://dojo.domo.com/t5/Ideas-Please-suggest-ideas-to/idb-p/Ideas). That said, I did have another idea, similar theme as the first, but a different approach. This may or may not work depending on the level of functionality your users…
  • Depending on the nature of your data, dataset, and the overall analyzer capabilities you wanted a user to have, if you had a preconstructed, pre-aggregated dataset with a numeric rank based on some ordering (Sales, descending for example), you could apply Analyzer against that rank ordering number. That's probably not…
  • How about setting a parallel date value field to whatever date you really want your view to be based on, but only populate values through the end of the prior week. Leave current week date values empty, and set your lookback to 5 weeks. "Last..." naturally wants the current period to be inclusive - you are forcing the…
  • @jeffcavallo, see this previous post which may help. The naming convention is very specific, but it looks like you've got that part ok. It is also my understanding that it may not work if there are any records with incomplete or invalid values. In that case, it may be necessary to create a pre-filtered Dataflow to…
  • Thank you, that view helps. I was locking myself into thinking about "Series" with No Aggregation. But instead, having two separate measures to represent the Series components, and no Dimensional Series value, totally makes sense. Thank you (again!)
  • Oooohhhh... so there will be a horizontal offset between the two columns. Not Stacked which is how I was thinking about it, but rather done as a Grouped Column, one will go up, the other down, and they'll share an X-Axis value. Got it! Not exactly the visual I was going for, but I can see how to do it now, and an…
  • Hi @DaniBoy, thanks for the follow-up. Yes, there are several active map-related posts in the Ideas Exchange, at least one that I wrote, and another that I've piled-onto. The ability for map cards to have a persons name listed by state, county, or zipcode Improve United States Map Card functionality Product Manager has…
  • @kingaaronj, nothing yet. @Gavatar, I think you are the Product Mgr for this area, aren't you? Can you enlighten on any maps-related enhancement that may be in the works? There are several different Ideas and discussion threads on topic floating around the Dojo. Thanks!
  • Been a while on this topic, had to move on to other things, but have had occasion to circle back and work on this. I now have a dataflow created with Magic ETL... Essentially, each segment is looking at the entire population, but based on a different attribute, so that I can create a stratified view of the overall…