GrantSmith Coach

Change the way you store your data such that each action has its own row date action 1/1. A 1/1. B 1/2 a 1/3 b etc. You can utilize the calendar dataset from the Domo Dimensions connector to left join your data set t twice based on the ever a date and based on the event b date and append those two together. You may need to…

Domo currently doesn’t support the ability to conditionally set the size of the columns and just assumes the best fit sadly.

Hi @JonavilCello You can't change the owner of an app, I believe due to security concerns, but you can make yourself an administrator. Alternatively you could re-deploy your app with your account and use that moving forward and delete the old app.

Hi @Raj This is something the Labs team would need to investigate as it appears to be a bug in the CLI. Since they'll have access to the source code I'd recommend opening up a ticket with support to help your issue get resolved.

@dylang91 Can you just join your budget values to your pivoted dataset based on the date so you have the column for budget?

You can use multiple workbench servers on the same domain. It’s possible. You’d just want to watch out so you don’t have different workbench jobs updating the same dataset as it’ll get some odd behavior when attempting to update the dataset. the documentation is talking about multiple instances of workbench running on the…

@jstan Are you utilizing SSO for your Domo instance with your Azure AD?

it appears you only need the client id and secret. Just put those into your connector and it should handle the part about generating an access token

It needs to be a metric (number) and not a dimension (string). Once you have that you can then add multiple other metrics to your chart. With it being a dimension Domo is assuming all of your different series are within that dimension. If you had one row per product instead of all the products on the same row you could use…

You'll need a client ID and client secret which you generate from https://developer.domo.com/manage-clients. You'll define the specific scopes needed when creating your client. Once you have those you can then pass those to OneCloud to finish your connection

Hi @lvtrujillot You can utilize window functions in beast modes to accomplish this. You'll need to talk with your CSM to get it turned on. I've done a previous write up of window functions and running totals before. You can read up on it here:…

I'd recommend doing the splitting out in your custom connector and having a single row for each tag in your dataset, then you can use an ETL to group by and combine them together with a comma afterwards. It's easier to loop through all of your tags and generate one row for each tag.

Hi @Pedro_Valverde Have you tried sorting those axis labels in descending order on your card?

You'd need separate cards for each graph but you can put multiple charts side by side within a page. Essentially you'd have a page with 20 separate charts / cards on your page. You can resize the different charts to meet your needs on the page.

I’d recommend waiting as DDX bricks looks to streamline a lot of the development work and makes it simpler to deploy. It’s uncertain as to how long it’ll be until it’s generally available so if you need the custom app now you’d need to go the traditional route.

@MarkSnodgrass - I win 😋

What is your beast mode and are you sorting by any values? You may need to create a new beast mode for HOUR(`Timestamp`) and sort on that so it's sorting based on a 0-23 value instead of doing string sorting.

@Hiraayub Sadly this isn't possible as you're wanting to aggregate (average) an aggregate (count) which isn't possible. The only way to get close would be to pre-aggreagate your data in an ETL and then take the average in your card but that's not what you're wanting since you want filters to be applied.

Credit to @MarkSnodgrass for offering that answer.

Magic ETL doesn't support conditional joins so you'd need to set a constant for each of your datasets called 'Join Column' and set to a value of 1, then do a join on both datasets together. After that you can use this expression to filter your results. `URL` LIKE CONCAT('%', `Product ID`, '%') Not the most efficient method…

@User2021 How are you able to relate the child to a grandparent or great grand parent? You data appears to show that the parent (numbers) never being in the child column (letters). What you're asking to do, If I'm understanding you correctly, is to have Domo recursively go down the "family tree". Domo can't exactly do this…

Hi @user000253 Are your values blank meaning an empty string '' or are they actually NULL meaning no data? To handle both cases you could add an additional clause to your case statement with a COALESCE function: CASE WHEN TRIM(COALESCE(`Flow Velocity (ft/s)`, '')) = '' THEN 'BLANK' WHEN CEILING(`Flow Velocity (ft/s)`)<= 10…

Hi @User_32265 Regular expressions are a great tool for this use case when you're trying to parse our text from another with variable length or positioning. You can utilize this regular expression in a formula tile: REGEXP_REPLACE(`url`, '^.*/([^/]*)$', '$1') ^ Says start at the beginning of the string .* Match any number…

"There's an API for that" ™  😂 api/identity/v1/users/search You can submit a POST request to that endpoint and it'll return user information. It defaults to 200 users. Sample body:…

For those of your coming to this looking for an answer you can find more information on a newer topic here: https://dojo.domo.com/discussion/54163/export-card-data-using-python-pydomo#latest

Those are some nice links you have there @MarkSnodgrass :) You can leverage the logic outlined in the links he's provided to calculate the difference in the number of full days in between your two days, then multiply those days by the number of hours in your day (8) then add in the number of partial days (hours) from your…

SUM(1) / SUM(SUM(1)) OVER () SUM(1) will get you the total number of within the grouping defined on your card. SUM(SUM(1)) OVER () This returns the total for your entire dataset after filtering has been applied. This version is simply counting the number of rows for each group and the total number of rows across the entire…

@JR_Iron The data is returned when you call the render endpoint. You can pass in your filters / query overrides as part of the PUT request. Inspect the network traffic for the render endpoint when you go to a card and that'll show you the request it's making and the data points from the card in the returning JSON.

Thanks @Anna Yardley and @Richard - It was a great session. Looking forward to more.

Hi @Trumpetbob You can look into window functions to calculate rolling averages or percentages. I've done a writeup on this previously here: https://dojo.domo.com/discussion/52679/domo-ideas-conference-beast-modes-rolling-averages#latest This will take into account filtering as well as a beast mode.