GrantSmith Coach

Definitely log a ticket with support and outline the impact of it being slow. They tend to be sensitive about slowness.

Have you tried converting your series directly to a category after you import it? raw['column'] = raw['column'].astype('category')

In the Domo Governance Dataset Connector there's a Card Fields and Beast Modes report which should list all the fields used on a card for you. You can then take that data, group by the dataset and field and count the distinct number of card IDs to see how many cards are using the field.

Try converting the series itself as a category: raw['VEEVA Entity ID'] = raw['VEEVA Entity ID'].astype('category', errors='raise')

According to that documentation you should be able to supply it as a GET parameter with the value of a cvs list of fields you wish you average: var dataAggregateBy = 'day'; var dategrain = [dataDateColumnName + ' by ' + dataAggregateBy]; var query =…

You should be able to apply a page filter on the page to see if a date field is in between two other dates however you won’t be able to use two filter card to do this as they filter rows off data based on the exact match.

ETL Formula tile doesn't seem to want to handle single quotes correctly. I've been able to get it to remove single quotes using the Replace Text tile but you may have to put in the single quote a couple times as I've had it remove the single quote and replace my single quote with empty string. You can copy the JSON code…

Hi @ozarkram Views aren’t supported as an input dataset into MySQL data flows. You can only use them as inputs in the new MagicETL.

Have you tried using the same account for both connection methods and confirming the data you're getting back is the same or different?

Is the API you're connecting to able to return only the changed records? If that's the case then you'll have to use a recursive dataflow as there isn't an upsert option for the connector. If your API returns all your data then there it's much you can do.

@Garrett_Kohler It appears to be a bug. I'm seeing the same thing in my case as well. I'd log a ticket with Domo Support.

Yes it came out with the Domopalooza 22 release. Here’s more information on the latest release https://domohelp.domo.com/hc/en-us/articles/360042936114-Current-Release-Notes#1.10.

There doesn’t appear to be any documentation on the values. It’s be nice if it came with column definitions in the schema but it doesn’t and those are the programmatic values that are being returned. You could try and reach out to your CSM to see if they can get an answer from development for you.

You need to go to the dataset itself not the ETL

I’d submit feedback to Domo with this. You can find instructions how to do that here https://domohelp.domo.com/hc/en-us/articles/360042922794-Submitting-Domo-Product-Feedback

I'd recommend logging a support ticket and seeing if Domo can investigate the error for you.

You're not able to do this in a beast mode. You can use a GROUP BY tile in Magic ETL and tell it to separate the values by commas as your aggregation method.

There should be a _BATCH_FILENAME_ field in your dataset after the connector runs which will contain the name of the file which was imported into Domo. You could then use an ETL to extract information from your filename that way.

You need to go through the dataset under the history tab you'll see all the prior updates to the dataset. When you hover over a specific version you can select from the wrench menu on the right hand side to revert to a specific version of your dataset. This should allow you to get the data back you lost.

How is your total not summing properly? Is it too high? Too low?

Each row can't be from last month and 2 months ago at the same time. You could possible aggregate on each product code and sum the 2 months ago and last month ago to get the totals.

@ozarkram you have an extra closing parentheses at the ends of sum(`LY SALES`). There should only be one

NULL represents a missing value. You could try something like this to handle an entire string and null values NULLIF return NULL if the column has the value specified - empty string in this case - and COALESCE returns the first Non NULL value in the parameters supplied. In other words return the company name if it’s…

Hi @ozarkram you can use an HTML table and some conditional coding in a beast mode to accomplish this. I have a talk at DP22 about this topic and did a write up here: https://dojo.domo.com/discussion/54554/dp22-using-beast-mode-to-build-data-storytelling-formatting-text

@mberkeley If you could accept my answer to your question so others can find it easier in the future I'd appreciate it. Thanks.

@Joe_M How was your scheduled report created? Was it being viewed in a monthly aggregation when it was created or a daily aggregation?

@ozarkram If you could accept those answers to your question so it's easier for others in the future to find I'd appreciate it. Thanks!

Hi @ozarkram It sounds like you're wanting to restrict which data is visible depending on specific user criteria. This is what PDP was designed to do. You can enable PDP and define the criteria for the records users or groups are allowed to see. You can read up on PDPs here:…

@svetlana You're welcome. If you could accept the answer so it's easier for others to find who may have this same question in the future I'd appreciate it.

You can’t dynamically disable drill paths but you could utilize a different dataset on your drill path card which had PDP enabled to only the groups you wish to have access.