Comments
-
I was able to make this work by choosing a pie chart and making a card for each coverage type so that it will only have one value in it. I used the color rule for the color which looks to see if they have coverage. Since I am using a story page, I can make multiple small circles/pies and put them next to each other and get…
-
@Jarvis That's a good idea about the color rules. Any idea on how to create a card that is a circle or a group of circles? Or something similar? I feel like my only option is to create a custom chart, but I was hoping to avoid that.
-
Yes, generally it would look something like this. Just depends what else you want to do in your ETL. You can build some pretty elaborate ETLs if you want to. It just depends on your needs. You may want to watch a couple videos on building ETLs if you aren't familiar with it. There is a lot you can do.
-
Assuiming you are using the ETL, you should be able to use the row number function in the rank and window tile to create a unique ID for each row in your data. For #2, you should use the Add Constants tile and it after each dataset and before you union them together with the Append Rows tile. Here's a link about the Add…
-
It sounds like you need to pivot your data, in which case creating an ETL and using the collapse columns tile should get you what you want. Here is the KB article that discusses it. https://knowledge.domo.com/Prepare/Magic_Transforms/ETL_DataFlows/02ETL_Actions%3A_Edit_Columns#Collapse_Columns
-
I don't think Workbench is set up to select all tables from an entire database, but here is an option to make it a little less cumbersome. In Workbench, create a job of one your tables and save it. Go to the More tab and export the job. This will save your job as a JSON file. Now, you can open that file up in any text…
-
I think I created what you are looking for. Here is what I did. I created some sample data that looks like this (I've also attached the file): StudentCredits Toward ProgramCredits RequiredJim57John67Joe77Sue87Bill97 I then created a beast mode field called CreditPctRange that contains this: (CASE WHEN (`Credits Toward…
-
I would suggest you use the collapse columns tile to "pivot" your date columns into a single column and then use the group by tile to get the min of those dates. You can even split your dataset to do these functions and then join it back to your original dataset if you need to use it with the rest of your data. Not sure…
-
If you scroll down to the ETL example in this article, you can see how to do it. In the example, they are doing average, but you would just replace that with sum. https://knowledge.domo.com/Prepare/DataFlow_Tips_and_Tricks/Creating_a_Rolling_Average_Using_DataFlows Hope this helps.
-
Unfortunately, it doesn't look like you can use the Last Value Projection properties when you have more than 1 series. See KB article: https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Building_Each_Chart_Type/Multi-Line_Graph Note: Though Last Value Projection properties appear in the Chart…
-
You could do this with using the row number function of rank and window and then use the filter to function. Here is the KB article for rank and window and row number. https://knowledge.domo.com/Prepare/Magic_Transforms/ETL_DataFlows/03ETL_Actions%3A_Rank_and_Window#Row_Number Basically, you would use the row number…
-
I have used many beast modes to filters. Here is a screenshot of adding one to the filter section and it worked for me. Perhaps something is going on with your beast mode?
-
If you are just doing SELECT statements, it is not too daunting. I would encourage you to review this KB article that should give you enough basic knowledge to do what you want to do. https://knowledge.domo.com/Prepare/Magic_Transforms/SQL_DataFlows/01Creating_an_SQL_DataFlow You would select your source dataset as the…
-
In the select columns, you can use type-ahead to slightly ease the pain of selecting your columns, but you are still limited to do it one at a time. This has sped it up for me as I have a dataset with nearly 600 columns. Perhaps a better option would be to use a SQL dataflow whose only purpose is to select the columns that…
-
You can move this through the admin section. Go to Admin - Pages and then click on the checkmark next to the page you want to move. Then, over on the right, click on Edit and choose Move Pages. You'll be able to make it a top level page or make it a sublevel page underneath another page (which it sounds like what you want…
-
Do you have any PDP policies in place that would affect what other would see? Typically, page filters affect all users, so it is surprising they aren't seeing your changes.
-
Do you have a unique identifier in your dataset, such as ID? If so, you can choose that column in your summary number and choose count and it should display the number of rows that you have in your dataset.
-
My first thought would be to use the Date Operations and use the Week of Year function to derive the week number from the invoice date and build your dense rank off of that. However, it sounds like you want to count 7 days from the first invoice date regardless of the day of the week. To get what you want is going to…
-
Is the external source that you are connecting to throttle how many records it will return at once? It has been a while since I have used the developer studio, but I seem to remember having to build some looping functionality for it to return all of the records.
-
It appears to be going off of the format that is chosen for the Y-axis. If you format your y-axis to show zero decimal places, your min/max/average should use that format.
-
I would agree that the ETL would be the way to go. I would suggest that you look into the Rank and Window options in the ETL. Here's a knowledgebase article that breaks it down. https://knowledge.domo.com/Prepare/Magic_Transforms/ETL_DataFlows/03ETL_Actions%3A_Rank_and_Window Also, it is worth noting that you can have one…
-
If you just have the line column and the quantity column and choose SUM as your aggregation, you should get what you are looking for. If you click on a line it will drill into that line and show you the details of the line number. Now, if you add other columns into your table card, it will start taking the uniqueness into…
-
For append, you have a few options, but the most common method is to combine the datasets where the column name and types are the same. You'll see the various options when you configure the append rows tile. You can make them the same by using the Set Column Type tile and the Select Columns tile. This allows you to change…
-
@Sgoedecke Have you tried just evaulating based on the month of the period instead of the entire date and just look for January? It would look like this: SUM(SUM((CASE WHEN MONTH(`PERIOD`) = 1 THEN (`Beg Balance`+`AMOUNT`) ELSE `AMOUNT` END) ) ) OVER(ORDER BY `PERIOD`) It seems like using the MONTH function would make it…
-
@imelendez Typically when you are merging a historical dataset with a current dataset, you would want to use the append method in the ETL, especially if your columns are the same, which it sounds like they are since you made sure to use the same stored proc. Try using the append method instead of the join method in the ETL…
-
In the ETL and the SQL dataflow, you can't pull in all rows because it is just for previewing. You can adjust how many rows you see, but you can't choose all rows when your dataset is very large. You will want to complete your ETL with an output dataset and then build a basic card that is powered by that dataset to…
-
An important thing to note is that in ETL and in SQL, it will not load your entire dataset if you have a large dataset. Therefore, it can be tricky validate your data while building if you are looking for specific values. Depending on the setting, it may just be loading 10k rows of your dataset. Keep that in mind. As far…
-
I would suggest you make your where clause to be: WHERE 'date' BETWEEN '10/1/19' AND '10/31/19' This is the more standard date format for SQL to evaluate the dates, assuming your date format is m/d/yy
-
You can use the color rules feature to change the color for the single value. Here's a link to the KB article if you haven't used it before. https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/KPI_Card_Building_Part_2%3A_The_Analyzer/Setting_Color_Rules_for_a_Chart
-
Have you tried changing your date selector grouping? If it is set to None, that could be your issue if your date field has a time stamp in it. Try setting it to group by Month and see if your calculation works properly.