jaeW_at_Onyx Coach

Is `temperature` numeric or string? '33' and 33 ARE NOT the same thing. '33' is a string whereas 33 is numeric. I suspect you want CASE when (`temperature` >= 33 and `temperature` <= 39) then '30s'

I hear you on the clutter issue. -- Implement content management practices that makes UX / UI the responsibility of the business -- If it's not a data security problem, then maybe you can direct users toward practices that let them get to the stuff they want to see faster. For example, when I do content management…

@kacy in order to analyze usage, particularly in the context of 'no usage', you have to have two pieces of data 1) a list of all the product contracts (it sounds like you have a start date and end date) -- one row per contract 2) a list of daily usage (it sounds like you get that already) -- one row per day the contract is…

oh. this was reported by another Dojo user as well, send an email to support@dojo.com

@grimmers that's wicked! glad to hear. If your dashboard does slow down, consider dropping columns in your Fusion. If any of the responses from @GrantSmith or me helped, please feel free to mark them as a solution! Thanks!

Sorry @GrantSmith ? i know you're gunning for that belt ? SUM(CASE WHEN `Country` LIKE '%In' THEN `Value` ELSE 0 END)/SUM(CASE WHEN `Country` LIKE '%In' THEN `Value` ELSE 0 END) OVER () to get to work in Domo, the denominator would have to be: sum(sum( case ... end )) over () @nat040711 , if you haven't seen windowed…

Have a good think about what you want the data to mean and display. I recommend that instead of JOINing the data as recommended by @rado98 that you UNION the two sets of data after adding a column Aggregation Level with constant values 'Daily' and 'Monthly'. This way you can avoid crazy math in your beast modes when you're…

Did you try creating a new (whatever the current version is) Instagram connector or is this an older connector that stopped working? Also, it's worth submitting to support@domo.com Domo maintains a broad library of connectors, so sometimes the devs don't know that an API changed until a customer reports an issue.

Rohil, can you confirm you can run all the jobs with manual execution?

there is a Domo Governance Dataset calld PDP, but that's probably not what you had in mind. AFIK there is no way to report with 100% certainty what you're asking for, other than to look at which cards have been shared with users (b/c cards are power by datasets). You can get a hint by looking at the Domo Stats Activity Log…

You can't do it in Domo with beast modes with the data model that you have without listing out each user in your card. What you can do is create an ETL (or data view if you have the beta) and add a window function column that calculates the min(login_date) over (userID). This would be your 'first login event ever'.

that would be the method. one thing you could consider, is create a DatasetView that sits between your dataset and the cards, and treat the view as a 'semantic layer' (friendly spellings etc.) that way if you ever change the underlying dataset then you just have to update the view instead of the dataset. also, it is a pita…

at the moment Admins have full control over everything, there is a product enhancement in the works called 'departmental admins' but at the moment, the functionality you're looking for doesn't exist. you can schedule backups of your data using the JavaCLI to external sources, and you can ask support@domo.com to restore the…

=IF(I8121="Total SS",M8121*12,IF(I8121="Total PODZ",M8121*12,IF(I8121="Total 5+1 ",M8121*2,IF(I8121="Total 3 Pack",M8121*4,IF(I8121="Club Pack",M8121*360))))) Take a look at CASE statements. (just google CASE SQL statement)

hmm... update your version of the CLI? Beast Mode Manager does have a bulk update feature.

This is not a Domo problem, this looks like a SQL optimization problem. Do you have any indexes? Have you tried paring down your query until it runs? If you're not good at optimizing SQL, have you considered using MagicETL? There's nothing you're doing in your SQL that you can't do in Magic, and Magic will ultimately…

try reducing the stuff in the schema file. try changing the type from dataflow to API or CSV try changing the dataset name to not include a hypen. if you're trying to alter Beast Modes, beast mode manager will probably be the better tool for this job.

could you just set the default PDP behavior to not have access to rows of data, and then only give access to datasets that are certified? also... knowing how difficult/laggy governance is... would you really want to prevent people from engaging with data until the stewardship team could play catchup? it seems there could…

do you actually need to calculate at the row level? could you just do SUM(colum1) + sum(column2) and get the desired result? In beast modes this will be faster performance than calculating at the row level b/c of how adrenaline works. but if you're concerned that SUM(column1) may end up being NULL, you could wrap it.…

Do you mean, use a checkbox instead of a radio button filter card? If yes, it's a chart type. @user084060 wrote:Hi, I am using a filter card that affects another card. Now the filter card is set up in a way that I am allowed only to pick one item on it. How do I adjust the filter card, such that I can select several items…

you have to be careful if you're adding new data every 15 minutes. When you add new data, Domo has to reindex the data in Adrenaline. If Adrenaline re-indexes the Fusions, I'm pretty confident it clears your cache. If you clear your cache, all your pages and cards will never benefit from a warm cache. It should be fine as…

https://stackoverflow.com/questions/28486891/uncaught-error-module-did-not-self-register ?

there's built in filtering that would allow you to filter by weeks. alternatively you can construct a date dimension table based on TODAY() that includes a calculation for WeekNo and a WeekLag_fromToday

What error message did you get? This works fine. select date_part(dayofyear, cast('2020-02-14' as date)) Is your Date column a date or text? Domo processes Redshift ETL in a Redshift cluster. So if you're throwing an error during transform steps it's usually a code issue.

piece of cake. You need two chunks of data. "Sales Actual by day" and "Financial allocated by day." Yes, you need to break your financial data into one row per day. Decide if you have 20 or 30 days per month. APPEND the two together and differentiate by 'Activity Type' or some similar column. Then decide how you're going…

https://knowledge.domo.com/Connect/Connecting_to_Data_with_Connectors/Configuring_Each_Connector/Connectors_for_Social_Media/Facebook_Advanced_Connector#Which_endpoint(s)_does_each_report_call_in_this_connector.3F The documentation is pretty clear about which APIs it's hitting. https://developers.facebook.com/docs/ I don't…

@user046467 let's be clear, when you're creating a connector you're saying you're unable to get 'the right data' OR in your cards you're not showing the 'right data'? If you're having difficulty configuring a facebook connector, support might be a good avenue for you to pursue. if you can't get the right data in Analyzer,…

I assume in your raw data you have one row per building and then the metrics going across in columns. If that's the case then you need o collapse the metrics such that your end result is one row per building per metric. (use the collapse columns MagicETL tile). Then you can pivot as @MarkSnodgrass where Metric is in Rows…

@user10198 wrote:Hi All, Well im trying to have a date-time card so that it is like a clock visible on domo dashboard. So there are few issues that i am facing 1. the date and time are required for different time zone . i want to show central European summer time zone (utc+2) 2. i am using the NOW() function , and i want…

Beast modes don't support BETWEEN syntax. But also... this is the sort of thing that might benefit from a lookup table / date dimension + a fusion. It'll be more easy to manage.