GrantSmith Coach

That's what I was curious about. It can be a bit confusing but glad you got it working properly.

Is this only when you do the test of the connector or have you actually run the connector and it's requesting the same data multiple times?

Is Domo interpreting your initial string as a date and the column is a timestamp data type? There a function called STR_TO_DATE which will allow you to convert a string to a date type object based on the format string you pass in. Alternatively you can do TIMESTAMP() to convert your string to a timestamp since it's in the…

Ah that makes sense now. You'll likely need to use a different beast mode to calculate the percent of total using something called a window function. A window function will return an aggregation across your entire dataset or subsection of data. Current Year SUM(CASE WHEN YEAR(`Date`) = YEAR(CURRENT_DATE) THEN `Value` END)…

The concept is the same if you're using beast modes to calculate the YTD_22 and YTD_23 values, just create a new beast mode by subtracting your 22 beast mode from 23 beast mode as @ColemenWilson mentioned.

Beast modes perform on a row by row basis for a singular value. You can’t create multiple rows with a beast mode. You’d need to do that in an ETL

Which fields are nested beast modes? What definitions go to which field? Have you tried using a table card and breaking each part of the beast mode into separate sections to determine which part is causing issues?

You can log in as an Admin and go to More > Admin > Dashboards, search for your dashboard in question then check the checkbox next to it. In the upper right select Add dashboard Owner.

You can use a window function for something like this: SUM(SUM(1)) OVER (ORDER BY `Score` DESC)

You can change the data label in the setting to use other fields or values so if you want two separate columns for tie tooltip you can put them into the tooltip values

Can you pass in filters based on the date such that start_date is between your date range and end_date is between your date range?

Because your website and domo are coming from different domains by default you'll get the CORS error which is a standard security check to make sure you're not attempting to access a website from a completely different website. This is to avoid click-jacking attacks. There isn't a way to avoid this except for turning off…

A Domo Brick is a simplified custom app. You can see in the upper left portion of the bottom data mapping tab the name of the dataset that's been mapped and which dataset it's mapped to. The manifest file is already created and deployed with a DDX brick. If you need additional control over the manifest file then you'll…

Have you tried utilizing color rules and making the condition where isn't blank to apply to the cell and not the entire row? You may need to use a beast mode to set a default as it may not show empty value as an option. COALESCE(`Date Column`, 'MISSING DATE') Then set color rules based on the beast mode where the value is…

The custom app version does indeed work, it's just a matter of swapping out all your datasets on the cards and dataflows. Documentation on Domo's Shopify Custom App connector: https://domo-support.domo.com/s/article/000005100?language=en_US Shopify's documentation on creating a custom app and getting an access token:…

You can follow Shopify's documentation to create a custom app and get the access token here: https://help.shopify.com/en/manual/apps/app-types/custom-apps#create-and-install-a-custom-app

If you go under the Total section of that drop-down menu that's where you can change how the total row is calculated.

If you embed a dashboard there is an option for maximization to have a popup window for card details: Allow maximization — Opens a pop-up window of the card Details view for a card. This allows you to see more detail and interact with the card such as quick Filters and allows for additional export options.…

What date field is the PoP comparison using in your date selector? Are you using any beast modes in your chart?

Yes if you click on the three dots in the dataset history on the version you want to revert to you can find the option.

I’ve also recently had issues with the Shopify connector where it’s saying it’s not authorized when I’ve authorized the connection already. I’m also waiting to hear back from support

If your data doesn't have data then it won't connect. You'll need to insert records in your dataset to have a contiguous line in your chart

+1 for LAST_DAY. An alternative is: CASE WHEN LAST_DAY(`Date`) < LAST_DAY(CURRENT_DATE()) THEN 'In' ELSE 'Out' END

You can refer to the KB article on setting up the SA360 connector: https://domo-support.domo.com/s/article/360042926714?language=en_US It walks through getting the ID and secret from Google's developer console.

By default the total is summed, if you select the Turnover % in your column list for your pivot table you can change how it's aggregated for the total record.

Are the values explicitly formatted as text in your Excel document? As a workaround, you can do as @DavidChurchman mentioned and just LPDD them in a MagicETL after it's been ingested.

You likely have some blank spaces in your 3rd party field. To handle these you can ignore empty fields: GROUP_CONCAT(DISTINCT CASE WHEN TRIM(COALESCE(`3rd Party`, '')) <> '' THEN ` 3rd Party` END)

the ds_get function doesn't allow for any encoding other than the default utf8. Two options here: Override the Domo class and write your own ds_get function to handle the latin1 encoding you have Bypass using the ds_get and just call the dataset.data_export function to return the data, then call pandas read_csv on your csv…

What type of file are you importing from? CSV? XLSX?

On the schema tab in your workbench job, set your ID field to be a string instead of a number. This should keep it as a string with the leading 0s.