GrantSmith Coach

You can replace the FLOOR(SUM(`random_number`)) on line 11 in the example with the beast mode that will format the value with commas. You can refer to the Number Formatting link I sent earlier.

@tlammie1806 Google restricts the amount of data it will pull in the APIs due to performance reasons. If you limit your request to a small enough dataset it will return everything, otherwise GA will return a sample of your data. You may need to pull data for a specific day to reduce the size and have GA return the entirety…

It's not possible to include an average when using a category series. You could create a separate graph to display the overall average next to your original graph.

Are you grouping by anything? Have you selected to graph by day or month in your date selector (upper right of the graph)? What type of graph are you using?

Here are a few posts on beast modes that may help you: https://community-forums.domo.com/main/discussion/52677/domo-ideas-conference-beast-modes-number-formatting https://community-forums.domo.com/main/discussion/52685/domo-idea-exchange-beast-modes-abbreviated-summary-number…

Agree with @MarkSnodgrass. To clarify you'd need to do this within a Magic ETL dataflow as a beast mode on a card won't support the multiple aggregations that would be needed.

Glad it's working again for you.

I tested this in another instance and it seemed to be working. What specifically is the issue / how is it not working? Have you made any changes to your configurations recently?

@nshively - Is this the first record for the effective date for the job title? If so, lag can't get anything before it so it will return a null. Also - just to confirm is your beast mode using back ticks (`) instead of single quotes as displayed in your formula above? I'm assuming so and it's just a formatting issue with…

How did you do the appending? Did you do a left join from your all records to your duplicate remove records dataset based on the primary identifiers between the two tables? If the identifier isn't found in the removed records dataset then you can use a formula tile to calculate it's a duplicate CASE WHEN `id field from…

You can select the type of aggregation for a pivot table or table with subtotals under the Subtotal options for each column you include and toggle whether to show the subtotal or not.

Sorry, I had the wrong format, try %m-%Y.

Are you currently logged into your instance? If not try and log into your instance again in another tab and then try and save it again.

You can use a formula tile and the STR_TO_DATE function STR_TO_DATE(`Month`, '%Y-%m') Alternatively you could just use LAST_DAY to get the last day of a month to get the month of your date / timestamp field. LAST_DAY(`RRDAT`)

Currently this isn't an option with how Domo works. You'd need to either use a contains filter and have the user type in the filter value instead of a selection filter or have one record per person and subject.

More auto-formatting issues. Try this version for your procedure definition. /*Dynamic Reverse Pivot*/ CREATE PROCEDURE Pivot() BEGIN SET @cols = (SELECT GROUP_CONCAT(DISTINCT CONCAT('MAX(IF(p.`Target` = ''', `Target`, ''', p.`Target Value`, NULL)) AS ', `Target`) ) AS Base FROM `preformat`); SET @sql = (SELECT…

Looks like my copy and paste was bitten by the forum formatting. Remove the first line and it should work. /Dynamic Reverse Pivot/ Alternatively you can change it to what it should be /*Dynamic Reverse Pivot*/ the /*…*/ just represents a commend to add some contextual information but doesn't do anything to the actual code.

Have you looked at the domo.filterContainer() method? https://developer.domo.com/portal/e947d87e17547-domo-js#domofiltercontainer

Microsoft does have a Planner API (https://learn.microsoft.com/en-us/graph/planner-concept-overview You might be able to write a custom connector to pull in the planner data instead of having to write it to a SQL database and then import into Domo.

There isn't anything out of the box that would potentially allow you to replicate this specific visualization. You might be able to do it with a Domo Brick but that's a more technical route.

@Ashleigh I'd recommend logging a ticket with Domo Support. Certification should work with groups and I've successfully used them in the past. This sounds like a potential bug.

Hi @NathanDorsch, I was able to get some time this weekend to dig in a bit deeper to your issue. You'll want to use the following code to do a dynamic pivot using a MySQL dataflow. Replace the nathandortch_pivot_table_example in your code to the name of your input dataset name. The first transform you'll have is a table…

@user045907 - Have you thought about using a Magic ETL dataflow to have your dataset as an input and then filter the data so you don't have historical then output it to another dataset making it update on a daily schedule? Once that's in place you may be able to extract the dataflow definition with the Java CLI, change the…

Beat me to it as I was going to suggest pydomo to do this. Here’s more documentation for future users https://github.com/domoinc/domo-python-sdk/blob/master/examples/stream.py

Create a new beast mode to return an integer based on the order and then use that in the sort of the card: CASE WHEN `Year of Tour` = '5 Years Ago' THEN 3 WHEN `Year of Tour` = '3 Years Ago' THEN 2 WHEN `Year of Tour` = 'Current' THEN 1 END

The company settings - language setting may allow you to change the display type of numbers for the entire instance by selecting your variation of English. I wouldn't use a formula in the ETL to do the conversion as it will convert it to a string instead of a number and you'd lose all of the numerical aggregations. You may…

This is likely a Domo infrastructure backend issue that you'll need to reach out to Domo Support to get resolved.

Do you have any trailing whitespace in your email names? You could wrap your column name in a TRIM function in the formula.

Try this in a formula tile: CASE WHEN REGEXP_LIKE(`EmailName`, '^.*(\d+)k$') THEN REGEXP_REPLACE(`EmailName`, '^.*(\d+)k$', '$1') * 1000 END It's surrounding it in a case statement to make sure the field will match your regular expression if it does then format it otherwise it'll return null.

Thanks for the clarification - how is the formula not working? Is it because the original values aren't null or are the fields you're expecting to be converted not being converted to numbers properly?