GrantSmith Coach image

コメント

  • Hi @Khan_Naziya I'd recommend using a webform to maintain the list of clients and then utilize a Magic ETL or Dataset View to join your original dataset to this client list dataset to filter out any non-client data. If you're looking to do some special calculations based on which client is which you could attempt to pull…
  • Hi @user027022 Currently this isn't possible as the UI doesn't function this way as you'd have to do each ID one at a time to find in your filter list, select the checkbox and then search for another ID. This would be great product feedback for your CSM as I think it'd be a great enhancement to automatically split a search…
  • @Victor You need to use an HTML Table. It won't work within a Mega Table.
  • Hi @user02319 The date range field determines how much data you wish to have displayed on your card so in your example it would show just the last 30 days worth of data. Compare To says I want to take a given time period (in your example days) and compare each of those to 180 days ago. So on your graph it would compare the…
  • Hi @Shumilex You can utilize a Magic ETL 2.0 data flow with 3 different input data sources, then join the data sets together using a Join tile bsaed on the date and username fields. The resulting dataset would have all of the columns in the same dataset. Alternatively you could use a Dataset View (in beta, talk with your…
  • Hi @user062862 If you want the order date to be before status you need to call datagrid.addColumn('Order Date'...) before the Order Status. Because you're adding Status column before the date column is what you're getting your current result. Could you just add all 3 columns to start and then just add a null value (this is…
  • As a minor tweak I'd recommend not including the wildcard at the end as it might cause incorrect matching. For example if your domain was "google.co" it would also capture "google.com". CASE WHEN `emailaddress` LIKE '%@mydomain' THEN 'Yes'ELSE 'No' END
  • Hey @SLam What other columns do you have in your chart? Would it include the error message that isn't aggregated? It sounds like the grouping in your chart (non aggregated [count, min, max etc] fields) might be causing some issues as the summary number is looking across your entire dataset but depending on the fields…
  • Hi @user02319 Yes, this is possible however you'd need to structure your data in such a way that you'll need to calculate your YoY in a beast mode instead of using the period over period type graph as that'll support only a single metric. @jaeW_at_Onyx has a great video of this concept which I recommend…
  • Hi @SLam You could use a Min or Max function on the ErrorDecription field to display only one value on your drill path if you don't necessarily care about all of the different Error descriptions. That'd restrict it to a single value for each OrderNumber. If you're interested in combining all the the error messages then…
  • Hi @user073741 You can use a beast mode to calculate the number of distinct topic / card IDs if you're grouping based on the user ID with a simple COUNT(DISTINCT `user_id`) however you aren't able to filter on an aggregate on a card. There is an alpha feature which enables this however I don't recommend it as it's doesn't…
  • Again, I'd highly recommend you configure an offset dimension to setup a week prior and 2 weeks prior custom offsets and structure your data as such. @jaeW_at_Onyx did a great video explaining this whole process as well: https://www.youtube.com/watch?v=CDKNOmKClms 
  • @user028686 If you absolutely must use a beast mode you could utilize the DAYOFWEEK function to get the end of the prior week and then subtract the number of weeks you're interested in. DAYOFWEEK returns values between 1 (Sunday) and 7 (Saturday). Subtracting that value for the number of days will return the end of last…
  • Hi @user028686 Whenever I typically need to do some period over period comparisons I actually restructure my data so that I have a report date and a "comparison date" (the actual date the metric was recorded on) and calculate it as necessary. This allows you to have custom defined periods (like 2 weeks ago and a week ago).…
  • Hi @Aymeric Really it's going to require more training for your users. When selecting Delete there is a dialog box that pops up which warns users of the consequences and that it will delete cards from this and all other pages. This action cannot be undone. Similarly the Remove option has a dialog box outlining what exactly…
  • Hi @user016095 This is a common question regarding looking back in time. The best way to think about this is to restructure your data. With your beast mode you're asking essentially is 1 = 1 - 364 which will never be true because beast modes compare data within the same row. What you can do is join your data to itself but…
  • Hi @Chris_Wolman With WB5 they took away the more detailed scheduling in favor of the "sometime in this hour" schedule. If you really needed it to you could utilize Windows Scheduler to have a more fine tuned schedule which would then call the wb.exe executable telling it to run the job at the specific time you desire.
  • Hi @user075492 Domo has some governance datasets which would help with your analysis. Specifically the DomoStats connector contains an Activity Log dataset which will show you all the different actions a user has taken including card views, page views etc.
  • Hi @user069636 You can calculate the first day in a week using the DAYOFWEEK function in your beast mode. SUM(CASE WHEN (`Date`) > DATE_SUB(CURRENT_DATE(), INTERVAL DAYOFWEEK(CURRENT_DATE()) DAY)AND (`Date`) <= CURRENT_DATE()THEN `Units`END) DAYOFWEEK returns values between 1 (Sunday) and 7 (Saturday). Subtracting that…
  • Alternatively yes, you can just filter for last month in the date selector which is probably the cleanest ?
    Previous Month GrantSmithによるコメント January 2021
  • Hi @Ashleigh There's several ways to tackle this. One possible way is to utilize a date dimension to calculate last month data. This has been outlined before on the Dojo. Alternatively the quickest option would be to utilize the LAST_DAY function in your beast mode. CASE WHEN LAST_DAY(`dt`) = LAST_DAY(CURRENT_DATE()) THEN…
    Previous Month GrantSmithによるコメント January 2021
  • Hi @Shumilex You'll want to utilize a windowing function to calculate the sum for each partition / typename and then divide that by the sum of the entire dataset. SUM(SUM(1)) OVER (PARTITION BY `typename`) / SUM(SUM(1)) OVER () If you don't have windowing functions enabled you'll need to talk with your CSM to get that…
    % of Total GrantSmithによるコメント December 2020
  • Hi @user033540 You likely have a difference of 4 hours because Domo stores dates and timestamps as UTC under the hood and then converts the dates when displaying the data in a card. You need to make sure your data is in UTC time when ingesting it into Domo. You can utilize a Timestamp transform on a workbench job to…
  • Hi @user004289 If you're referring to the preview within Magic ETL it's limited to 100 rows. If you want to see more you'll need to output it to a dataset to review the entire dataset contents.
  • GROUP_CONCAT is the MySQL version of LISTAGG group_concat(MyString separator ', ')
  • Hi @user031930 Are you using public or private embed? Only with private embed can you apply and change filters. Here's the knowledge base article describing some limitations: https://knowledge.domo.com/Engage/Sharing_Content_Outside_of_Domo/Sharing_Cards_and_Dashboards_Outside_of_Domo_Using_Domo_Embed As for page fitlers…
  • Hi @kboudrie You could attempt to add a Beast Mode as a column which use the same logic as your color rules and returned a description of that specific coloring. If you didn't want it on the same card you could create a new table card and just list that new beastmode as a column and add the same color rules to it so that…
  • Hi @HashBrowns Domo doesn't like it when you try and take an aggregate (count) of another aggregate (row_number). There's some caveats to this with window functions but how you're utilizing this is why. What I'd recommend you do is create a new Magic ETL (or a Dataset View if you have the beta) to perform your windowing…
  • Hi @user046467 You could spin up a magic ETL and attempt to convert the data type to a date (using Alter Columns tile in Magic 2.0 or Data Type(?) in 1.0). When you run the preview it'll state which value it wasn't able to convert to a date. Alternatively you could utilize a replace text field with a regular expression to…
  • Hi @tstimple I've written up a similar solution utilizing UNIX_TIMESTAMP, some simple math and the CONCAT function. I'd recommend taking a look at https://dojo.domo.com/t5/Beast-Mode-ETL-Dataflow/Date-Calculations-minutes-and-seconds/m-p/49259/highlight/true#M8465. That will give you a way to customize your display of the…