GrantSmith Coach

@PJG Magic ETL dataflows are a great way to enhance your data efficiently especially in such cases as yours where you can translate one value to another and have that value then accessible to all your cards. Domo's Knowledge Base has some good articles on Magic ETL. I'd recommend you start there to learn more about Magic…

To add some additional context the first one works because it will return a singular value from your window function so any aggregation on your card will work on that field but can cause some issues depending on your sorting and grouping and other aggregation that's being performed on the card when it's displayed. The…

Hi @pauljames , Typically for connectors that Domo doesn't provide out of the box, I'll either write my own custom connector or I'll utilize a scripting language like Python and the pydomo library to ingest the data myself. It's a bit more technical to get the data but there's a lot of documentation out there.

You can utilize a window function to calculate the estimated month depending on the number of days that have elapsed in the current month. LAST_DAY returns the number of days in the month Running Total: CASE WHEN `Date` < CURRENT_DATE() THEN SUM(SUM(`Sales`)) OVER (PARTITION BY LAST_DAY(`Date`) ORDER BY `Date`) END End of…

How is your data being grouped? Are you looking for the max date across all records or within a specific partition of your data?

You would create a beast mode for each of set which would be a conditional sum where the period type = Last Year then use that beast mode for the prior year graph and period type = current for this year. Both are keyed off of the report date field but the data would conditionally be last year or current

I'd recommend utilizing a custom date dimension which would allow you to have a singularly selected date but then allow you to show last year's data. I've done a write up on this in the past you can find here: Essentially your second graph would have there the period type = last year.

If you have a constant value from your calculation you can apply that value by doing a Cartesian join. To do this use a formula tile to add a new column called Join and set its value to 1. Feed this into a filter to only get your single value for the specific code. Then duplicate that filter and change it so it’s getting…

Does it accept a POST request instead of a GET request?

That would need to be an idea in the Idea Exchange for Domo to allow the ability to "zoom" to a specific time period in your data without filtering out your data as it's currently not supported.

Due to standard security practices a NOT IN option typically isn't provided as it opens up the data possibly to everyone on accident rather than just a single person on accident. NOT IN is a more risky security practice which is why Domo doesn't include it. Alternatively, you could configure specific groups to not include…

HTTP GET requests typically don't accept body parameters as part of the protocol specifications. GET requests typically pass parameters as part of the URL as URL parameters instead of body parameters. Are you able to pass those using addParameter before your request?

You need to add a comma to your date format: DATE_FORMAT(`MyDateColumn`, '%b %d, %y') For others who come across this there's a great Domo KB article on date format string you can find here:

I don't believe an official list exists however I'd recommend looking at the Beast Mode Function Reference page and avoiding using any of the functions. Alternatively, you could just prepend or append a character like an underscore to avoid name collisions dynamically.

In order to track the weekly stats you'd need to either use a dataflow to add in the timestamp and schedule it to run once a week and have it append on the output or alternatively use a dataset copy connector and set it to append to automatically copy the original dataset with the _BATCH_LAST_RUN_ timestamp field. As for…

You need to wrap your entire case statement in SUM instead of having your condition be the sum. It's evaluating each row at a time and then aggregating when you want to aggregate after evaluating all the rows. SUM(CASE WHEN … … THEN `INVOICE_AMT` END )

You’d need to explode your data so that you have a record for each month. You can do this with magicETL and filter where day = 1 to only get the first of each month. Then using a formula tile on your data you’d need to calculate the first of the month with something like `Subscriotion Start Date` - INTERVAL…

You'd need a ROUND function to reduce the amount of decimal places. Once you're adding in the HTML coding the data becomes a string and you're unable to utilize Domo's built-in formatting options so you need to format your number yourself. If you want to format it as a currency you can do something like this post:

Domo isn't really designed to be an ODS but more a reporting data store. Typically connectors will run at a minimum of 15-minute intervals but some have longer intervals between runs. At best you might be able to get a 15 minute latency.

You can't do this within Vanilla Domo itself however Domo Embed does allow for you to switch datasets with Dataset Switching. You can read more on it here:

Hi @NathanDorsch Typically when I'm doing PoP analysis I'll use a custom date dimension to add more flexibility for what I want to do. I'd recommend reading this article that I've written up in the past on how to get this configured and used.

You should be able to get the page URL to get a more exact match from GA4 / UA.

This is just a warning message when attempting to do something that won't be supported in later versions of the pandas package that Domo is utilizing. You can ignore this warning for now assuming your dataset is being written properly. Domo will need to update their domo package to properly fix this warning in their future…

What does your data structure look like? Do you have separate columns for bought and sold based on each day or do you have one row for each sold and purchased along with the date? Do you have a starting inventory number?

Congrats @trafalger !

You’re limited to 3 tooltips however you can create new beast modes and combine several fields together with a CONCAT and then use that beast mode as a tooltip.

Likely what's happening is that one of your B2, B3 or B4 calculations is returning a NULL which will make your entire calculation NULL when using +, -, * or / operations thus not returning any data to your chart. You can try and wrap each in a COALESCE(formula, 0) call to make sure you're not adding NULLs together.…

You can't do a dynamic pivot with Magic ETL however you can leverage prepared statements and SQL in a MySQL dataflow to do dynamic pivoting. You can follow the SQL with something like

Cards aren't considered "viewed" by the DomoStats unless the detail view is looked at. When looking at a card on a page it doesn't count that as a card view. As @MichelleH mentioned you can utilize the Domo Governance or Domo Stats connectors for pull the last viewed information for pages and join each card on that page…

The activity log doesn't capture if someone plays the video, only if they look at the doc card details as a view. I think this would be beneficial to know and I'd recommend logging a new Idea in the Idea Exchange.