Comments
-
To my knowledge, each tab will need to be it's own data set. However, you could then use an ETL or MySQL data flow to join each "tab" into one larger data set.
-
Would you be willing to post a sample of your data set? It would be helpful to understand how your data is set up. This may require you to add a field to the data set instead of just a beast mode calculation.
-
For your Date ranges, I would suggest usind DATEDIFF() (CASE WHEN (`OW_TO_STORE` = 'X') THEN '01. Store OW' WHEN (`DC_OH` > 0) THEN '02. RDC OH' WHEN (`RDC_OO` > 0) and DATEDIFF(`RDC_ETA_STATUS`,CURRENT_DATE())=0 THEN '06a. RDC OO Due Today' WHEN (`RDC_OO` > 0) and DATEDIFF(`RDC_ETA_STATUS`,CURRENT_DATE())=1 THEN '06b. RDC…
-
What is the Data type for `RDC_ETA_STATUS`? Would you mind providing some sample data so we can understand your data set a little better? Is the current beastmode giving you an error message? Or just the wrong result?
-
That being said. I think that a cross table is a fairly common analytical tool that seems to be missing from Domo currently. I think I'll add this as a feature request. Cross Table Card You can vote for the idea here: https://dojo.domo.com/t5/Ideas-Exchange/Cross-Table-Card/idi-p/35262#M6648
-
The easiest way that I have found to do this is by using the Domo Workbench. As part of the set up, you can set the schema for each field:
-
How do you receive the surveys? Is it from an email? What is the format?
-
I did get a Product Update email from Domo this week talking about changes to the Facebook connector. I was not able to find the article in the knowledge base, but it did say to contact Domo Support with any questions about these changes. https://support.domo.com I think the changes took effect on Monday. When did you…
-
If you create the drill path on the first card, and then use the "save as" feature as you are replicating the card, the drill path is copied as well. I am unfamiliar with a way to replicate a drill path once the cards have already been made without a lot of manual work.
-
Is there a reason that you don't just want to use color rules?
-
case WHEN SUM(`OrderDollars`) - ('929846') > 0 then CONCAT('<div style="background-color:#9CD58D; width: 100%; height:100%; margin:-20px; padding:20px"><a href="#">', SUM(`OrderDollars`) - ('929846'),'</div>') WHEN SUM(`OrderDollars`) - ('929846') < 0 then CONCAT('<div style="background-color:#fcbcb7; width: 100%;…
-
Rather than using the "Current Month" filter on the date field, you could use a beastmode to filter the dates on the card: case when year(DATE_SUB(curdate(), interval 1 day)!= year(curdate()) and year(`date_field`)=year(curdate())-1 and month(`date_field`)=12 then 'Y' when (case when day(curdate())=1 then…
-
If you are not confident that the users will be able to operate the page filter efficiently, you could try creating "Linked Cards" to each of the cards you are using. Basically, each card would be set to display the Current FY data and would have a "linked card" that could display Previous FY data.
-
Try this: CASE WHEN DATEDIFF(IFNULL(`Termination Date`,`As Of`),`Adjusted Start Date`)<180 THEN '0-6 Months' WHEN DATEDIFF(IFNULL(`Termination Date`,`As Of`),`Adjusted Start Date`)<=365 THEN '6-12 Months' WHEN DATEDIFF(IFNULL(`Termination Date`,`As Of`),`Adjusted Start Date`)<=730 THEN '1-2 Years' WHEN…
-
Your suggestion sounds good to me. If you want this to be a page filter than I believe the field would need to be added within the data flow. I do not believe that beastmodes can be used for page filters. I would suggest adding a field called `Fiscal Year` to your data set. Depending on when your fiscal year turns over:…
-
You can create a group that has all of your Domo users in it, and then share the page to that group. For some added visibility to the page, you can go "Company Settings"→"Company page settings" and set the order of the pages, including the default landing page.
-
If that doesn't work, you could try this: case when sum(`Total Users`)=0 then 0 else CONCAT ( (sum(`Tool 1 Views`)+Sum(`Tool 2 Views`)) / (SUM(`Total Users`)) ,' Views') END
-
CONCAT ( (sum(`Tool 1 Views`)+Sum(`Tool 2 Views`)) / (SUM(`Total Users`)) ,' Views') Try this
-
I was not able to find a way to hide the variance series from the legend. You could always just hide the legend altogether. In theory, if you titled the card and added a good description, the legend may not be needed.
-
Can you provide some more clarity to your sales cycle here? It looks like stage 5 is "Won", stage 4 is "Lost", what are the names of your stages? Does every deal that is won go through each stage (except lost)? i.e. can a deal go from stage 2 straight to won? Do you have a historical data set? You would need to be able to…
-
This is a great tip. Thanks for sharing. It did spark some thought around possible improvements to summary numbers. I posted an idea, please upvote here
-
Correct, if you leave it as a string, then the quick filter is sorted alphabetically. If you change it to a date, you need to include the day as well. Do these months refer to a specific time frame for your fiscal year? You could use a beastmode to label it something like '2017 Q4', etc. Just be thoughtful about what you…
-
You could set up a beastmode to filter the dates that you want. Although you would not be able to alter the dates via the quickfilter any more. case when `Date Column` IN('Nov-17','Dec-17','Jan-18','Feb-18','Mar-18') then 'True' else 'False' end Or, if you change your string column to a date first: case when `Date field`…
-
Could you share a screenshot of your analyzer?
-
Is your Date field formatted as a Date? I'm sorry, I couldn't view the image that you attached.
-
You should be able to move multiple fields into the "Sorting" section of the analyzer. If you put your data field first and then add your series under it, does that accomplish what you want to do? Can you show me a screenshot of your analyzer if you are still having trouble?
-
Case when `month`=‘Jan’ then 100 when `month`=‘Feb’ then 200 when `month`=‘Mar’ then 300 end however, you should replace ‘Jan’ with whatever your dataset has
-
I think you want to use the Stacked Bar chart type. The x axis should be opp owner. the y axis should be revenue measure 1, with revenue measure 2 and 3 both added as "series"
-
That would be a nice addition. We currently put that information in our card descriptions (the user has to click on the card title to read the description.)
-
If there is any calculation to it, you could potentially create the target line with a beast mode. Otherwise you would need to add the target values to your data set and then you could use a bullet, line and grouped, symbol and grouped, etc. chart type to display it.