GrantSmith Coach

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:

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

I don't think there's an option but it'd be a great idea for the Idea Exchange.

Twitter has recently rolled out its new v2 API which essentially paywalls API access to read the data. I don't believe the Domo connector has been updated to use this new one yet. https://twittercommunity.com/t/announcing-new-access-tiers-for-the-twitter-api/188728

I missed that in your screenshot but you did have the backticks. The forums interpreted it as a code block when it was pasted in. 2,4,8 and 10 are comments where you can add additional information for context but won't be evaluated, that's what the two dashes represent as part of the beast mode. What I'll do when…

That's a great first attempt. What you're missing is surrounding your field names with backticks (`) to show that they are fields in your dataset and not actual beast mode code syntax. CASE WHEN `Actual Business Go-Live 1 Date_p` IS NULL THEN —- If Initial Business Go-Live 1 Date_p IS NULL = 'On-Time' CASE WHEN `Initial…

My understanding is that Workbench is built off of the .NET platform and not the Java platform so you should be ok.

Correct, this is because the page is locked to prevent editing from anyone except for admins and the page owner (the lock symbol next to your Keyword Performance title).

Not directly. There is a Domo Stats dataset for Workbench which has higher-level information. You can export all of the workbench jobs and their definitions in JSON format on the server itself. You can use the wb.exe executable in your Workbench installation with a command prompt to export all of the jobs and then take…

Partitions are used to replace a group of records typically. If you have some records being replaced for a date then pull in all records for that date and use the date as your partition key. This will replace all records with that date. Alternatively if records aren’t being deleted you can utilize UPSERT in workbench to…

Separate variables would be a good use case here. Two for the stats and two for the ends and then just compare within a beast mode if the date is between what was supplied

Yes, you'd need to utilize a group by function. You can either use a function in the group by or use a formula tile to put your CASE statement in and then do a distinct count with a group by tile.

Are you keying your admitted based off of STATUS or and ADMITDATE field? What issues are you running into with your beast mode? It looks like you're missing the trailing ) in your beast mode after the END.

This isn't a possibility with a beast mode as they'll have access to the dataset that's powering the card. You'll need to do the masking within an ETL and utilize PDP to filter to filter only the rows that are allowed. You'll then need to add an additional field to your dataset to identify masked rows to allow users to see…

Currently the table is the only one that will work. If you want you can get more control of the visualiation utilizing a Domo Brick which would support circular images.