ArborRose Coach

Each dataset has an id shown in the URL when you look at the data. Can you use an anchor reference link pointing at the id for each of your drilldowns? <a href=""></a>

Do a search on community forums for "pfilter". You should find some examples of passing parameters.

There is a way. In a past post I gave an example of creating a link that passes specific parameters to the page. I'll try to find it for reference.

The message "Insufficient developer role: insufficient developer role" means the assigned team member might not have the permissions within the Instagram developer account to set up the Instagram connector. You need to ensure that the person has the developer role assigned to them in the Instagram Developer account. This…

Based on the error, it sounds like the body of the email you sent didn't match the expected pattern defined by the regex filter. But you aren't showing us either so its difficult to tell you what pattern isn't matching.

One possible solution is to ensure that each chunk you upload is consecutive in terms of the data. It seems like you're attempting to split the data into chunks of 800,000 rows each, but it's possible that the rows aren't consecutive across these chunks. Perhaps something like this: Import necessary libraries import pandas…

Sorry, I meant to add some text to that response. I don't think you can directly map Calculation IDs to Beast Mod IDs. But I think you can use the API to retrieve the information. I have provided links that should point to the appropriate documentation.

Domo Developer Portal: https://developer.domo.com/ Dataset API Documentation: https://developer.domo.com/docs/dataset-api-reference/dataset Beast Mode API Documentation: https://developer.domo.com/docs/beast-mode-api-reference

As mentioned, it's just (col1+col2)/2. Use coalesce(col1,0) if you have nulls. They will become zero.

To add the updatemethod=Append argument to your Domo object instantiation in Python, you can include it as a keyword argument like this domo = Domo(client_id, client_secret, api_host=api_host, updatemethod="Append")

//This code uses the example dataset… var domo = window.domo; var datasets = window.datasets; // get the data domo.get(`data/v1/${datasets[0]}`).then(function(result){ var tableHTML = "<table><tr>"; // Extract headers and make them bold var headers = Object.keys(result[0]); headers.forEach(function(header) { tableHTML +=…

Here's a couple screenshots showing two different ways I'm calling the dataset. Note the difference in function(result) vs handleResult.

Are you saving after you select the dataset at dataset0? It looks like you are calling the dataset properly. And you've selected it. What is the warning in the triangle?

Congratulations @david_cunningham.

Sign in to your Google account and find security settings. It should be under manage your google account, security. Check third-party apps with account access or something like that. You should see a list of apps that have access.

Note for anyone reading this thread. I believe Grant's solution will also work. But I did not test it. As Mark mentioned, TRY_CAST does appear to be working in the ETL. And that's where I want it happening so my issue is solved. Thank you both @MarkSnodgrass , @GrantSmith .

Testing it on a calculated field in a card, it's rejecting TRY_CAST as a valid command.

If the source is from Google, you wouldn't be editing the google data, you would be editing the dataset in Domo that came from google. Any edits would be overwritten when the dataset is refreshed from Google Sheets. You could create a dataflow to isolate the inline edits. That way it would not be updated by Google's…

Typically, you would do it on a date field. But I believe it will convert a string value using YEAR(`fsa_spending_year`) You can use aggregate functions like COUNT and SUM inside beast mode calculations. Just wrap the whole case statement in SUM(…). It's okay to be new. I haven't been on here as long as the ancient ones.…

You don't need SQL. In beast mode, make a calculation such as… CY: CASE WHEN year(`fsa_spending_year`)=year(curdate()) THEN `rfs_amount` ELSE 0 END For previous year, subtract 365 days. Two years previous, 730 days. Etc. PY: CASE WHEN year(`fsa_spending_year`) = year(date_sub(curdate(), interval 365 day)) THEN rfs_amount…

Did you run them concurrently or one after the other finished? Based on the error it sounds like its saying you can't authenticate a second time while something is already running. Meaning, wait until its finished to then do the second…using the same account. And make sure that account isn't attempting to log in somewhere…

Domo also has JSON oAuth connectors for making generic connections to APIs. You can find them by entering JSON into the AppStore.

It sounds like you already have your token information configured. Next step would be to find the connector in Domo. Xero connectors for Domo are listed in the AppStore. You will see AppStore on the ribbon bar at the top of your Domo screen. Enter Xero into the search and hit enter. Several Xero connectors show up. Pick…

The syntax appears to be correct; all commas and parentheses seem to be used properly. There may be an issue with the usage of $fourteenDaysAgo in the $match stage. In MongoDB, you typically use variables defined within an aggregation pipeline stage using the $$ notation, but here it's used as a string value.

Welcome @david_cunningham

As David notes - you will need to aggregate ("group" and sum/count), with necessary fields. If you add fields to an output, the data will "break" or split on that data. Example, if your objective is to sum the amounts by store then you might include Store, Quarter, Month, and Sales. Since Month is in the set, it will split…

If you have a column such as a date in your table for goals, you can identify the quarter the same way you can pull month - QUARTER(mydate). Quarter being 1,2,3, or 4. When I configure my primary transaction flow, I have a column pre-calculated for each of year, quarter, month, and week. That way those values are readily…

You will need to make sure there's a connection between the data sources. Something in common you can use to join the sets. Your raw data would be showing something like a date and sales amount. Date, Sales 2024-01-01, 1200.00 2024-01-23, 900.00 2024-02-14, 2400.00 And your month goals might be something like Date, Goal…

You don't need to explicitely create indexes as you would in traditional databases. Domo's automatically optimizes for performance. Slow performance may be due to complexity of the dashboard or an issue in how you have things structured.

One way you could do it would be to append to a dataset using an ETL. Create a dataset and make sure it has a column to store the date. In the ETL dataflow, set a formula value with the current date and that in the date column within the dataset. Use the "append" tile to append data each day, the column value will act as a…