GrantSmith Coach

You can't hide the link but you can restrict their access to viewing the data by removing the grant in the admin section. You'll need to use a custom role to do this and then assign the users that custom role. If you want the link to completely go away I'd recommend logging an idea in the idea exchange.

You'll need a window function to aggregate an aggregate and a count distinct to count the users only once. COUNT(DISTINCT CASE WHEN COUNT(`userid`) OVER () > 100 THEN `userid` END)

Does the audit fail across all records with the same submission ID or are you looking to have just the Critical/Major portion of the submission marked as a failure?

For your first condidition, Critical/Major can't be both Common and Major at the same time so it won't ever get set as fail. It looks like you have two separate conditions so I'd split out the Common and Major clauses into two separate clauses: CASE WHEN `Critical/Major` = 'Common' AND No>= 2 THEN 'Fail' WHEN…

Assuming you're wanting a bucket for your applications and not an actual user group here you can utilize a magic ETL to enhance your data. With a formula tile and a CASE statement you can then create your groupings: CASE WHEN `Application` like 'STARTSWITHFORGROUP1%' THEN 'Group 1' WHEN `Application` like…

Page views and Card views are separate from each other in the activity log. You'd need to utilize an ETL to join the governance dataset for cards and pages to the page ID in the activity log and then count each of those page views as a card view in the resulting dataset.

Domo Publish is a premium option which can allow you to publish datasets and dashboards to child instances. Another possible option is utilizing some of the commands in the CLI tool to export and import Domo objects.

This happened to me today as

You'll likely need to coalesce your dataset1 zip code and dataset2 zip code into a new field using a formula tile and then use that to join your dataset 3 zip code. This way it will pull in zip codes that don't exist in dataset1 COALESCE(`dataset1.zip`, `dataset2.zip`)

You can use two join tiles with a full outer join to do this. Join tables 1 and 2 together then join the output of that to table 3 via an outer join.

Another version would be LAST_DAY(CURDATE() - INTERVAL MOD(MONTH(CURDATE()), 3) MONTH) To break it down: MONTH(CURDATE()) - returns the month number of the current date (1-12) MOD(..,3) returns the remainder when dividing by the month number by 3 so the last month of the quarter will be 0 INTERVAL .. MONTH - subtracts the…

It depends on how you want your data to be structured. You could duplicate the rows so that each email is on its own row or you'd have one record with three separate columns to store the three separate email addresses. In either case you'd need to use a for loop and loop through the emails property of your data.

Have you tried using a beast mode to calculate the difference between now and 5 days ago and counting them? COUNT(CASE WHEN `date_field` < CURRENT_DATE() - INTERVAL 5 DAY THEN `date_field` END)

Currently, this isn't supported out of the box with the standard visualizations. You could attempt to implement this with a Domo Brick instead to give yourself more control over the visualization.

Are Contact ID and Opportunity ID a list of CSV values or do you have one record per each contact & opportunity? How are you defining based on your data that the contact is attached to the Opp ID?

Are you enclosing your values in double quotes?

It works well if effort and training are put towards it. Make sure to train your users that only certified things are to be trusted and used for reporting purposes. The other thing is to determine the different departments and levels of certification you want to apply for and who is in charge of giving the approval. Should…

Are you requiring it to be in a tabular format? You could get something similar with a Sankey chart where you'd just need your data to have two columns: Boss Title | Report Title

Add your other metric as a Series. Since it's a metric and not a dimension it will treat your y-axis and series as two separate series.

This is an issue with the connector itself as it's expecting that property in the JSON to be returned by the API call but it doesn't exist. You'll need to reach out to Domo Support to have them look into the connector.

The way a case statement would work is that it will evaluate the first condition it finds to be true and then ignores all other condition. So in the case of how the logic is written, it would return 'On-Time' as that's what comes first.

One way to simplify your beast mode case statement is to instead utilize the FORMAT_DATE function: DATE_FORMAT(dt, '%m - %M') This will instead format your numbers as 2-character strings so they sort properly in your list and makes it a bit easier to read. 04 - April Here's al ink to some documentation about the format…

@MarkSnodgrass 's solution will work but here's a regex version for you: You can use a formula tile and a REGEX_REPLACE Client Name REGEXP_REPLACE(`clientfield`, '^(.*) ?(\d+)$', '$1') Client ID REGEXP_REPLACE(`clientfield`, '^(.*) ?(\d+)$', '$2') A breakdown: ^ - Start of the string (…) - Defines a match group to store…

You'd need to generate a dataset with numbers between the min and max of your graph and then you could utilize variables within the page for the E_Rate and N_Rate Values to automatically update your graph. You can use the value from the dataset for both your x and y value.

Your bar chart is being aggregated so when you attempted to add in user information it included all records as it now had to deal with the additional user information to group on. When you click on the 2022-Dec in your First-time purchasers Domo only knows about the value you selected which is the date. It doesn't know…

Custom Attributes currently aren't supported with Dynamic PDP. You could configure the PDP based on a dynamic group with the new custom attributes.

Great name @GrantStowell. Glad to have you on the forums.

You can change the Position of the text and Rotate settings under "Data Label Settings" properties on your chart in Analyzer.

The documentation is a bit buried but this may be of help to you to explain how the lastvalue parameters work in Workbench: https://domo-support.domo.com/s/article/360042932734?language=en_US

Can you provide a sample CSV or excel file (with just the dates with their field names, and no other identifying information)?