jaeW_at_Onyx Coach

@GrantSmith would it make sense to stack the data Such that you have ACTUAL UNION FORECAST UNION LAST YEAR OFFSET with a column 'Activity Type' to differentiate the three sets of data. Then use a CASE statement to differentiate between SUM(CASE WHEN Date <= today() then Actual ..) and SUM(CASE WHEN Date > today() then…

@crispinvaldez I don't know what to tell you. Email this screenshot to Chuck and ask him to validate that Windowed functions are enabled on your instance of Domo.

aww geeze @crispinvaldez , now i feel like a jerk. I did test out LAG() in my instance of Domo before replying and I did get a result that with 5 seconds of examination looked correct. In general Domo tries to avoid sunsetting features that would impact users, so if someone told me "it worked yesterday but broke today…

@kacy no worrieis. Pare a test function down to just one LAG() function. Make sure that you're including `TimeStamp(use)` in the GROUP BY clause of the SQL function your table generates. The LAG() function must have the same granularity as the number of rows in your final visualization. (so Timestamp, must be on an axis or…

Is the dataset exceptionally wide? Do you have exceptionally wide plain text columns? BTW. This is the sort of error you should direct to support@domo.com They are equipped with tools to troubleshoot bugs / issues when the error message is not particularly helpful. In the immediate term, you can test if the issue is a…

@hamza_123 and @GrantSmith Domo have a premium app called "campagins" that functions similarly to MailChimp or ConstantContact insfoar as it allows you to create ... email campaigns. In your example, yes, it would allow you to generate a list of users to send a campaign to, the campaign would of course be, the notification.

This'll sound snarky but isn't meant to be. Did you try it? Yes. Lead and Lag still work. Domo is a phenomenally powerful platform that is not completely documented because groundbreaking changes come out every quarter. I strongly recommend that you get used to both trial and error and googling your question. A year and…

https://www.youtube.com/watch?v=cnc6gMKZ9R8 I did something like this in a tutorial video. I think you need LAG(sum(quantity) , n )

You could make a beast mode with a CASE statement of all the 'not ins'. and make the else clause "choose me" -- or similar.

@Nick_ submit the feature request using Product Feedback in Domo. It'll create a Jira ticket which PMs are contractually obligated to review and reply to. It'd be nice if Domo was a little bit more consistent in checking Dojo ... but Product Feedback is the best way to guarantee they see it.

there isn't an equivalent of COALESCE or CASE in Magic 1.0. You can use FILTER to create your CASE switches. Then use a second set of FILTERs on NULL and NOT NULL to define the COALESCE (which value you want to prefer to keep) then use APPEND to bring all the values together. Be careful in defining your FILTERs. There is…

instead of a treemap, could you use a table card and then use HTML tags to set the background of the cell? https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Transforming_Data_Using_Beast_Mode/Adding_Graphics%2C_Links%2C_and_Images_to_Table_Cards_Using_Beast_Mode

Yes, Domo can do it ? Usually it'll be a matter of finding the right configuration settings. can you confirm that you can do an SFTP pull using any other client and the configuration settings you've applied? Filezilla for example? if you have the option of scripting from the server side, do consider using the JavaCLI to…

Most connectors in Domo support two ingest methods, APPEND (add new data) or REPLACE. Check the last configuration tab under dataset settings. Look for 'update method' or similar.

works as anticipated. with just Min and Max(date) if this isn't the result you're getting, make sure you don't have anything in the ORDER / SORT clause that would be changing the cardinality expressed.

If at data ingestion, Domo is able to 'interpret' your data as type Date, it will store it as type date and then display it in the correct format (day first or month first) as appropriate. So your question of CurDate() and date columns being in different formats should not apply. If Domo is presenting your Date columns as…

This is definitely something Domo Support should help out with. If you haven't already, google the error message (with Domo) I'm sure someone would have posted about it in the Dojo already. If I were in your position, I'd probably CC my CSM and frame it as 'I can't get started with Domo ... '

@swagner was absolutely correct the equivalent of PIVOT in Domo will be the Collapse / Uncollapse columns magic ETL tile. It's a bit of a bear b/c unlike SPREAD / GATHER / MELT from Python and R, you have to manually assign each column and unless you know Dynamic SQL there is no way to dynamically implement PIVOT / UNPIVOT…

@eriena I haven't looked at the Activity Log closely, but it sounds like you're saying, if a card is shared to multiple pages, it can be difficult to know which page a user was on when they access a given card. If that's true, you could do some ETL magic, and basically implement a LAG() function which asks "for each card…

Upload a Sample dataset that spans these duplicates you're returning to. It's 1AM over here ? but I'll see if I can't get you something for tomorrow. you can email me directly at jae@onyxreporting.com or DM me in the Global Slack Channel

This is a doozy of a question, and i strongly recommend you find someone who really knows their stuff to help you plan out your implementation ...because you don't want to spin your wheels. (that said, refactorign in Domo is pretty easy so it's flexible enough if you have to rework your pipeline.) 1. Issue is we have…

@JeffDaySJP contact your CSM or Chuck if you're in the beta program and ask them to "enable window functions in Beast Modes." It's a feature switch.

I think you could just put Name on the axis and create a MAX(Date) in a Beast mode.

Same as my response to your previous post, I don't think you can accomplish the bucketing you desire without pre-aggregating your data and then creating buckets based on an aggregated dataset (because you'd have to include UserID in the GROUP BY clause in order to calculate the number of visits per user BEFORE bucketing…

It would not be possible to define your user states (Is Resurected , is Active etc. in Beast Modes with month over month comparisons in Analyzer. You would have to be presenting the data at the UserID granularity in order to calculate the desired metric (because you'd have to have User in the GROUP BY CLAUSE ...) INSTEAD…

@GrantSmith remember, you can't filter on a windowed function b/c that's functionally the same as filtering on the HAVING clause (unless you have the beta feature enabled, but even then ... could be janky. I don't think @chrishaleua have you seen anything like this baked into product without using embedded cards or…

@chrishaleua have you seen anything like this?

HAHAHA did you post the same question twice once in English? :( sorry, usually I try to be good about translating non English Dojo posts :( sorry so late.

Just in case you haven't figured it out yet, in query-data you have two methods you can use to query the database, you can send a SQL query or you can specify a schema. In this video I show you how to use get-schema to get the schema of a dataset. https://www.youtube.com/watch?v=kHSeSbSFS1Q But in this post we found the…

The name of the dataset implies the granularity. That said @DataMaven has seen that not all DomoGovernance datasets have the expected cardinality. If I were using a DG dataset, I would enforce a GROUP BY clause to the data BEFORE JOINing it to another table to guarantee granularity. For Cards and Pages, I would 1) GROUP BY…