MarkSnodgrass Coach

Comments

  • If you are not able to use the append method that is available in the Settings section as previously mentioned, you can build a recursive dataflow that would let you append new records to a dataset without duplicating your data. This KB article does a good job explaining it.…
  • Yes. The Dashboard and Story Dashboard are the same. I believe Domo initially called the new layout Dashboard, and then moved to calling them Stories, and now they have somewhat settled on Story Dashboard. Whenever you see any of those three names, they are talking about the same thing. Hope this helps.
  • I'm not sure if this will solve your issue, but here is an idea to consider: Instead of using Sumo cards, use the Pivot Table card. It is currently in Beta, but you can request it from your account manager. It is more powerful than a Sumo card and may allow you to put the numbers in a format that you are wanting. Here is…
  • You can do this by adding an additional column in the ETL that you can use to Exclude the open accounts and still keep your main dataset intact to do other analysis. You would build an ETL like this: (I'll break down the steps after the screenshot) SampleStatus - this is your initial dataset Days to Close - This is a…
  • @Ritwik It should be in the top right portion of the page. However, I believe that if your story is too long, the Export to PDF option becomes unavailable. The PowerPoint option looks quite similar to the PDF, but I at least have the option in PowerPoint to remove the filter language that I don't want to show up. I would…
  • Have you looked into the Domo Governance Datasets in the App Store? This might give you what you need. Search for "Governance" or "Domostats" in the app store and you should see it under connectors. One of the datasets you can pull is the Dataset Schemas dataset. This should give you what you need. Below is a list of what…
  • Domo has a connector called Domo Dimensions that is a data table of all calendar dates that is useful for this type of work. If you search for calendar in the connectors section of the App Store, it should show up. If it doesn't ask your CSM to enable it. This can save you some work when needing to build a table full of…
  • I'm assuming you are wanting to do this for a summary number since you can use the formatting options on a field when you drag into use if it is a numeric field. There a number of methods you can use to do this. If you search for custom summary number in the Dojo, you will see some other examples. Here is what I created…
  • Are you looking for information like this? https://knowledge.domo.com/Prepare/DataFlow_Tips_and_Tricks/Aggregate_vs._Non-Aggregate
  • Ok. This should work for you. I've added some additional columns just for learning purposes so you can see how it is put together. The column that I named NewDate is really the only column that you would need in your output. I've added some comments to explain what each part is doing. SELECT "datelen", --Gets the year…
  • I would say that means it is falling into the first part of the case statement and it thinks the values are less than 19000101. Can you add another screenshot that shows the datelen column without any logic applied to it?
  • Redshift and MySQL have different preferences on their use of single quotes and double quotes. Try this: SELECT "campaign", "date", "revenue", CASE WHEN "datelen" < 19000101 THEN NULL ELSE date(to_char(TRIM("datelen"), '99999999')) END AS DateEXTRACTDTE FROM "df_ga_int_emarsys_campaign_attribution_sql_prep"
  • It looks like I was using the Redshift SQL for this conversion. Do you have the option to use that? If not, we should be able to track down the equivalent functions in MySQL.
  • I seem to recall running into a similar issue and I could never get the ETL to cooperate. I ending up doing a SQL dataflow to get the dates in an actual date format and then used that output dataset as my new input dataset in the ETL. Here is an example of what I did in my SQL dataflow CASE WHEN "EXTRACTDTE" < 19000101…
  • You should be able to build an ETL that has the NOAA dataset as one input dataset and your sales data as another input dataset. You would then use the Group By tile on your sales data and group by city and use the Average function on your rain total. Next, use the Join tile to join that data with your NOAA data to bring…
  • If you don't want to create a new column, you would need to do this in the ETL. You can use the Replace Text function to replace a site name with a different site name and not add it as a new column
  • You did that correctly as it looks like you are wanting to get contacts that only visited in 2018 and exclude contacts that visited in 2018 and then again in 2019.
  • Assuming you are using MySQL, you would do this to add 7 days SELECT DATE_ADD(mydatecolumn, INTERVAL 10 DAY) FROM MyTable
  • Thanks! I see the Add Tags option now and just added my 1st tag! Appreciate it!
  • @DaniBoy Do you have any insight on this?
  • Have you tried the line + stacked bar cards or line + grouped bar cards? Here's a link to the KB article about how to use them. https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Building_Each_Chart_Type/Stacked_Bar_with_Line_Graph Here is a screenshot of how I have used it. Hope this helps.
  • You should be able to do this with the Collapse Columns feature in the ETL. Here is a link to the KB article that walks you through how to do it. https://knowledge.domo.com/Prepare/Magic_Transforms/ETL_DataFlows/02ETL_Actions%3A_Edit_Columns#Collapse_Columns
  • When you add a page filter, if your column name is in multiple datasets, there will be a right arrow > that you want to click on. This allows you to select all datasets. Choose that and then when you use the filter, it will affect all the cards on that page that use those datasets. Here are some screenshots of adding the…
  • When you are viewing an individual card, have you clicked on the icon with the box and up arrow? It will give you the option to Send/Export and then you can choose to export the card to PowerPoint or PDF, which would export the card itself and not the data. When it is in PowerPoint, you could then copy and paste the card…
  • If you are using Domo Workbench to send the data to Domo, you can go to the Schema tab and change the data type to Text or String. This would eliminate the need to do anything in the ETL. 
  • Yes, you could certainly do that. If you are using Microsoft SQL Server, it would look like this: SELECT ROW_NUMBER() OVER(ORDER BY Product ASC) AS ID, Product, Class, 'TableA' AS Source FROM TableA UNION SELECT ROW_NUMBER() OVER(ORDER BY Product ASC) AS ID, Product, Class, 'TableB' AS Source FROM TableB The newly-created…
  • Yes, that is correct.
  • In my screenshot, the two dataset that are at the beginning are two different datasets. The names are cut off in my screenshot, so I could see how you were confused. For you, you should have Table A -> Add Constants and then Table B -> Add Constants 1 and then bring them together after that like the rest of the screenshot.
  • I just tried exporting a table card to Excel and it worked fine for me. Do you have more rows in your data than Excel might be able to handle? Have your tried going to the data center and then to the data set that powers your card and exporting that to see if you run into the same issue? That might narrow down the problem.…
  • I think I had the same problem as you a while ago. When you click on Add Filter, click on the arrow to the right of the column you are wanting to filter on. Then click on Select All. Here are some screenshots to help you. This should make your filter apply to all the datasets on the card. Hope this helps.