ArborRose Coach image

Comments

  • Mark thought he wasn't fast….gee. Better late than never right?
  • Dynamic parameters already happen. It's up to the API on the other side. I can call my APIs and pass them a list of specific customers with comma separators in a single parameter. Or multiple offices with comma separators. As long as the other side can understand it…it works. What I am not sure, is how I would expect to…
  • https://community-forums.domo.com/main/discussion/comment/86954#Comment_86954 Using the filter tile. When you review Domo's recursion example, they set up a dataset. Then use a calculated field to filter what is kept or filtered out. You can flush previous data the same way.
  • Sure. You can aggregate in an ETL (group by) and send the result to a tile that appends a dataset.
  • Interesting idea. If I need four different date ranges, I pull four different JSON connectors and combine them into a dataset. If we had the ability to do multiple date ranges, it would significantly reduce the size of the datasets being held…and reduce the strain for Domo's storage.
  • As a fixed field (test)….and filter.
  • Using a calculation instead of the aggregate…
  • What is your last field doing? Seems like you should be removing that last field from the table. Then put the filter in for >=3. You would then get the list of sites with 3 or more tickets.
  • https://community-forums.domo.com/main/discussion/comment/86919#Comment_86919 Your TicketNbr field seems to contain things other than ticket numbers. What are the COUNT 1 / xxxxx values? When doing a condition search for a value, I often write it as {fieldname} IS NOT NULL AND {fieldname} <>'' I use this because sometimes…
  • A beast mode calculation might be something like the SUM(CASE WHEN TicketNbr IS NOT NULL THEN 1 ELSE 0 END) Then put that calculation into the filter where fieldname is greater than or equal to 3.
  • Your filter appears to be on the site name, not on the # of tickets.
  • You can use the rank and window tile to identify the top 5. Then set color rules.
  • Two solutions that don't really solve your issue but might help. Using column widths, you can set the amount of width for a column. This includes making some fake filler columns. The other way is to use html table with a setting for padding. When I was looking for border styles, I came across a post talking about removing…
  • Btw…those identifiers in the URL are important. They can be used in Python code to identify a dataset to export the data to a local Excel file.
  • https://community-forums.domo.com/main/discussion/comment/86842#Comment_86842 They may not be able to share them via Domo, but each URL has an identifier associated to the dashboard. And those are unique. If I copy the URL from my browser and shoot it to a coworker in Teams or email, they can attempt to pull the card. They…
  • You can bring in portions of your data as a dataset and then create a ETL flow to append each to compile a larger dataset. Say you want 2 years of data. The previous years data you might want to pull on the week, each Saturday. The current year, you might want to pull the current quarter daily and the past quarters weekly.…
  • According to the Domo documentation on Locking or Unlocking a Page, "Locked Pages also cannot be shared by users if they are not the owner or do not have an "Admin" default security role or a custom role with the "Manage All Cards and Pages" privilege enabled."…
  • It sounds like you defined formulas on the ETL that are replicated in beast mode on the card of the dashboard. The beast mode on the dashboard would see the calculation already exists in the dataset with the duplicate on the card not being part of the ETL / dataset.
  • I tried background colors and hate the result. In this case I am trying to mimic an excel sheet. Without subheadings and borders, my Domo version isn't very readable. To differentiate columns, the descriptions get out of hand. This is such a basic html ability. I fail to see the usefulness of an html table that doesn't do…
  • None of these solutions work. A pivot table is inappropriate to my need. A mega table only lets me set the global style for verticals (as far as I can see). I need to set specific columns left and/or right borders so I can "section" the dashboard.
  • Ashleigh - can I control the borders between specific columns? I need to create visual sections of three or four groups of columns. I'm not seeing that control with a Mega table.
  • Mega Table should work just fine. Thanks. Any idea how to I could make subheadings?
  • If your dataset has something you can use to identify the incremental changes, yes. A recursive data set can pull records and append the records to an existing dataset. I would look at doing something similar. You just need to make sure your ETL accounts for changes in records. The following link should give an idea……
  • https://community-forums.domo.com/main/discussion/comment/86437#Comment_86437 Michelle is correct. In fact, I am staring at one of my own cards where the grand total shown is completely wrong because of this reason.
  • I too think your DISTINCT is probably the reason. If you are trying to count, I would create the CASE statement to be COUNT(CASE WHEN {conditions met} THEN 1 ELSE 0 END)….without DISTINCT.
  • I do this for year to year trend comparisons using chart type "bar line". I set the data range to the increment (month, quarter, etc). It gives me the current year as a bar and the prior 3 years as line overlays. As the year progresses, we see the performance comparison.
  • I inquired about a similar functionality. I wanted to give users a note taking ability - related to the Domo card. When a specific filter was applied, the user would see the notes written about that selected person or criteria. We had a work session for Domo to show me an example like Colemen's description but they weren't…
  • Thanks. I found a formula Grant used in a different thread and using my fields it comes out with the correct days. https://community-forums.domo.com/main/discussion/52686/domo-idea-exchange-beast-modes-business-days-prior-to-today