Shevy Contributor

Here is the solution I think we are going to use to answer my question - after some more work and looking at what was available: I can see the changes on screen in the history of the data base. In the example below you can see there was a manual update at 3:15 PST on 4/9/2020 In the Activity log data set I can see there…

I have a couple of questions and thoughts - not knowing what card you are using. But, in the card design, you can pick what date field you want it to focus on - one solution could be to use the Revenue Period date field in that spot. Now the card, filtered on this quarter will show the revenue that came in the quarter.…

Unfortunately not today. It needs to exist in the data set to display on a card. So force it in with a date table merge or it will be blank.

I have created a date table that I link to to be sure all dates are included. May not be the most elegant - but works and gives you every month!

You will need to add it as a column to your data set - you can do this in Magic ETL or in your original data set update. First, if you can change the data set you are bringing in to add a "Current Date" or a "Max Date"in our SQL statement, that is probably the easiest way. IF you do not have access to change the code that…

so I assume your beastmode is something like: `column1`/`column2`? Next question is "average vacancy" if one building is 100% full and one is 50% full is the answer 75% (simple average) or is it a weighted (actual vacancy) based on size of building? I assume the second is preferable. Make the beastmode:…

There are ways to make it an aggregation depending on what you are trying to do. For example if Column 1 has three values: 1, 5 and 10 and Column two has three values of 1, 10 and 40 then I assume your besatmode is a calculation making percentages like: 100%, 50% and 25%? OR: are you making it something like 1:1, 5:10 and…

Looking forward to the brew being complete! I know it was started last year as it was the hit of the announcement at last years domopalooza! Any idea if it will come out before this years party!

You will want to combine the two data sets into one data set. If I interpret your tables correctly, your first table is already a summary table by company. The second is a detail table that you want to summarize. Using ETL, bring the detail table in as a source, and use the Group by function to create a summary table. When…

Sump cards and note cards do not print in publications. I know I submitted an enhance.ent request for that that is under review... hopefully they will be added. In the meantime i re built many as table cards...

This is needed! Didn't see it as an option to like somewhere else!

what kind of join are you doing? Left join, inner join...etc... Also, you may want to force a 0 (zero) into the volume clumn when you do the join for those where there are hours worked and no volume (null values sometimes gives odd results)

I would use a Radial Dial - you can set several ranges and colors to identify what you want.

Sorry! I tried to do what you wanted about a year ago and learned I could not but could use the Radial gauge to get to it as I shwoed above. The comparative is more limited and not as customizable.

Yes - In the guage properties you can set ranges and the color you want to use. In the picture above Range 1, Range 2...etc Color choices like pink, Teal, orange.... 

Well it did confirm what I was afraid of! Execs dont like to switch views.... I will look into other options. Will also mark as accepted answer

If you just want to count all days, then this will work: (DAYOFMONTH(LAST_DAY(CURRENT_DATE()))-(DAYOFMONTH(LAST_DAY(CURRENT_DATE()))-DAYOFMONTH(CURRENT_DATE())))/DAYOFMONTH(LAST_DAY(CURRENT_DATE()))

I have not seen that - I would open a DOMO support ticket - that sounds like an issue with your instance or connection. The whole DOMO philosophy is on auto refresh!

Here is where it is in our instance

Yes you can append with Magic ETL. What I am not sure of from your post is if you want to append or if you want to update? If you are appending, sounds like you are creating a stacked Data source with date stamped versions of the same datasource? If so, bring the data source in, add a date field to identify it. for the out…

If your card is set to that data source, then it will refresh everytime the data is loaded. What issues are you seeing? If you are combining data using that data source. then you need to be sure you set the data flow to refresh each time the new data is imported. The cards will always point to the most current data.

Unfortunately no - I had this solution - was looking for a way to get just the one to show like yo can in EXCEL - will post to ideas board at some point.

I have had two get stuck in the last couple of days but I had the cancel button - I would reach out to DOMOsupport - sounds like a bug. I have not seen the situation mentioned without having the ability to hit cancel.

Windy, What was your reply? I do not see one here? Under Datasets, you will see Dataflows and you should have a drop down box to choose MySQL or Magic ETL.

For me it was Magic ETL (if I remember) and I was making a lot of changes - I thought perhaps I made changes too quick and system did not keep up. Didnt worry too much about it. It has happened two or three times but I have not been doing new ETLs recently. Sorry I cnat give you more details!

Another option is to create a date table that tags days as business days or not. That way you can exclude holidays that your company is closed or whatever criteria you need. The table can be linked to any other table by date and you get a lot of date information that will be consistent. We built our own, but DOMO has one…

Solved this - we ended up getting rid of the Publication groups as SUMO cards had an issue as well. Thanks for the offer!

That is the original solution and great for the average user - I have some EXECS, that are asking we show it without hover.... Can't always please everyone!

The "cancel" link not working? I have this occur at times but if I hit cancel and re run it usually works fine.

I have seen this issue a few times - sometimes it worked and sometimes it didn't. When it didn't I found deleting the original data set and creating a new Dataset that used the same name often fixed the problem and allowed for minimal maintenance. Also I sometime just did a second data set and then changed where cards…