Best Of
Apply Color Rules to other Columns
Hello, I am looking for a way or workaround to be able to apply color rules to other columns. For example, I want a beast mode's calculation and it's color rules to apply to a separate column that isn't even the beast mode. Essentially, being able to apply color rules for one column to another.
Re: Connecting Google Ads
@HowDoIDomo - Domo's Google Ads connector works for me now and I've had success utilizing it.
Re: How do I make a Domo to Power BI Connection with Microsoft Authentication or Okta SSO and not ROPC?
I don't know about the path you are seeking. But, are you aware there is a Domo ODBC connector that can connect you to your Power BI? Our Finance team uses Power BI and we use the ODBC to source our Domo data via their Power BI dashboards.
Re: How do I make a Domo to Power BI Connection with Microsoft Authentication or Okta SSO and not ROPC?
ODBC stands for Open Database Connectivity, simply put, it's a connection or handshake between systems. You may have several, some for source and others for destinations or both.
I have data coming into Domo through Workbench, Python, and APIs. And I have data displayed in Domo and some other data routed out to Power BI, MS SQL, Azure, and Excel csv files.
Re: Shopify - Month over Month % Change Beastmode Help
@DMJerryVuori , you can adapt the design pattern in this video to get the desired result, https://www.youtube.com/watch?v=CDKNOmKClms
Re: Beast Mode Question
Perhaps I'm not fully understanding your question. But it sounds like you can take the Net Gain column and add that to the Month column to get your month ending balance. It looks like you already have this column in your example screenshot. What am I missing?
Re: Average time to response but how do I not include weekends?
I think there's a way to do this by figuring out the day of week of the created field, the day of week of date of response, and the datediff of the two. You should be able to calculate how many weeks turned over from those three points of data, and therefore how many 2-day weekends which you can subtract within your beastmode, but I don't have enough time to play with it at the moment.
Re: Average time to response but how do I not include weekends?
Hey Deona,
Break this calculation down into steps:
- Creation of ticket date
- First response date
- Days between creation and first response date
- Weekend days between creation and first response date
- Weekday days between creation and first response date.
- The column is given
- given
- datediff(`creation_date`,`first_response_date`)
- You can use the SQL queries provided or the magic ETL date operations column to calculate the working days difference between 2 dates.
- Column #3 - column #4
nmizzell
Re: Average time to response but how do I not include weekends?
You can use the DAYOFWEEK() function to identify and remove weekends - days 1 and 7 (saturday and sunday)
CASE WHEN DAYOFWEEK(`YourDateField`) NOT IN(1,7) THEN Your beastmode END
LinkedIn Ads Connector - Upcoming update to the 'Ads Creative (versioned)' report
On Monday, July 29th 2024, Domo will update the version the API endpoint that is used to generate the 'Ads Creative (versioned)' report in the LinkedIn Ads connector. Datasets that are powered by this report at the time of the update will be affected as follows:
(1) Columns that are populated by the older version of the endpoint will remain in the dataset, but they may no longer be populated. If the dataset is set to replace mode, then these columns will be blank on runs following the upgrade. If the dataset is set to append mode, existing data in these columns will remain, but no new data will be populated. A list of column names returned by the older version of the endpoint is attached to this post as olderEndpointColumnNames.txt.
(2) Columns that are returned by the newer version of the endpoint will be added to existing datasets powered by this report, and will be populated starting on the day of the upgrade. You may see these columns in addition to the ones populated by the older version of the endpoint in existing datasets. For a list of columns returned by the newer version of the endpoint, please refer to the attached file called newerVersionColumnNames.txt.
(3) New datasets powered by this report after the upgrade will only contain the columns returned by the newer endpoint.
If you have a dataset powered up by the 'Ad Creatives (versioned)' report, and you have assets such as cards, dashboards and alerts, that rely on the fields produced by the older version of the endpoint which you cannot or do not want to immediately update following the upgrade, Domo recommends you update your dataset to use the ‘Ad Creatives’ report instead of the ‘Ad Creatives (versioned)’ report. The ‘Ad Creatives’ report uses the older version of the endpoint. Updating your dataset to use this report will not affect the dataset schema, and should preserve any assets that use the existing dataset.
If you have any additional questions, please visit the Domo Community Forum or reach out to Domo Support.
Tasleema