ST_Superman Domo Employee

@Ben_Dunlap - I'll defer to @MarkSnodgrass and @jaeW_at_Onyx for understanding the technical workings under the hood of magic 2.0 over MySQL. It sounds to me like your hands may be tied when it comes to which type of transform you are using and the decision has already been made to use MySQL. In that case, I would highly…

Hi @MichelleH Unfortunately, I don't have an answer for you. However, I really like this idea and I'm upvoting it. This would be a nice feature. Hopefully this post brings some more attention to it.

From my experience, there are several things that can have an impact with load speeds. Number of datasets being used on the page. Number of PDP policies applied to those datasets. Number of beastmode calculations being used in the visuals. I would agree with @GrantSmith though. What is the use case for having so many cards…

I think the other concern, even if they didn't view the specific card that you had the alert on, the admin could still just view the raw data set. I think there is a beta feature in the works to allow "departmental admins". I don't know if the beta is actually available now or not, but you could potentially create two…

This needs to get implemented. MySQL 5.6 is over 8 years old. Even the latest version MySQL 8 is 3 years old.

You could also apply PDP to the dataset powering the card. You could set the PDP dynamically based on the user email (if that is a trusted attribute).

@MattGo - I'm not aware of any way to do this. Most scheduled reports just link back to Domo if you click on the report (which would then have the hyperlink). However, I wanted to follow this conversation in case there was a feature that I'm not aware of :)

I would try something like this SELECT A.`Posting Title`, A.`Weekly Reporting Date`, A.`Weekly Report Stage`, A.`Funnel Stage`, A.`Candidate Link`, A.`Origin`, A.`Department`, A.`Days in Stage`, A.`Days to Hire`, A.`Days to Archive`, A.`Offer Acceptance Date`, A.`Candidate Journey Start Date`, A.`Event Date`, A.`Previous…

Hi @Ashleigh - I'm just posting because I would like to hear what response you get. Unfortunately, I do not have a fix for you.

The Dojo was a lifeline for me as I learned to use the product. Now, I enjoy coming to the Dojo for new ideas and to help out others.

@melyeo - make sure that you run all of the step in the SQL dataflow prior to calling the procedure. i.e. make sure that you run the procedure_transform_1 step first and then run the step that calls the procedure. (you can also select the down arrow next to the "RUN SQL" box in your screenshot and select run to this point.…

@Shumilex - the Calculated Field syntax does not like the BETWEEN clause. The formula that you provided should work for you. However, I would recommend being more descriptive with your filter expressions. I know that for the current use case, you are only interested in including future dates in the current month. But what…

@Jbrorby - My recommendation would be to stack your data. If you could get your data to look something like this: You could then use something like this for outcome - appointments per hour: sum(case when `METRIC`='Outcome - Appointment' then `VALUE` else 0 end) / sum(case when `METRIC`='Logged Hours per day' then `VALUE`…

I'm not sure I understand your dataset schema. Since this could impact any potential solution, would you mind providing some more details? I think it would help to have a sample of your dataset.

Are you sorting the table by any fields? Sorting can cause Domo pivot tables to "drop" data. Would you mind showing the sort properties as well?

@jaeW_at_Onyx - that's a nice approach. I'm curious, what were the rest of the handful of solutions?

You could add another beastmode to check for null values and filter on that. Something like CASE WHEN `PW Sales` is NULL then 'no value' else 'value' end You could then add this field to your filters and filter for 'value'

@Sam1 - Agreed! (link to original post https://dojo.domo.com/discussion/35632/dojo-forum-for-beta-testing )

I believe that the page filters save per user. So you wouldn't be racing against your other users to export the cards. The Powerpoint plugin simply exports the view of the cards that you had last filtered for.

Would be great if we could build some visuals directly from this "live" data as well. The domostats user activity only updates once per day... unless I'm missing something

@RobynLinden Would you want the quick filters to function like page filters? or interactive filters when viewing through the story? Or should they only impact the one card they are assigned to?

We have a landing page that directs our users to different KPI's by clicking on links. When we need to make changes, we simply create a new page and modify the content there. When it is ready to get "pushed to production", we simply redirect the link on our landing page to the new content and post a message about what was…

Can you change the x-axis to be MIN of the date field?

You can view my solution tables and dataflows here: https://domo-dojo.domo.com/page/1777803864

@user046467 Your table confused me a bit. If you want to show going from 100 to 50 as -50%, then I would be looking at the percent change from prior month. However, if you want to show going from 50 to 200 as +400%, then I would need to show the percent of the prior value, not the percent change (which would be 300%).…

You can do something similar to this by getting creative with a heatmap. In the heatmap option, I am actually using the % variance as the value that I am graphing and then pulling in the values I want to display as tooltips: Unfortunately, short of some html tagging, I am not aware of a way to do this within a table.

I would recommend adding a first_sale_date field to your dataset. You could do this by using a group by tile and grouping by your cust_id and then calculating the min(`sale_date`) for each cust_id. You would then join that table back to your main table by joining on cust_id. This would give you the first_sale_date as a…

You need to remove service from the partition by clause. That is why you are getting an extra row of data for each type of service that was present in that week

Sorry, I just checked the syntax that I used and I told you incorrectly. I don't use stored procedures very often. I actually stored a transpose procedure as well: -- 10) CREATE PROCEDURE transpose() BEGIN SELECT goal_info into @sql2 FROM for_transpose; SET @str=concat('create table normalized_goals as ',@sql2); PREPARE q…

@danidiaz I believe that there is a feature currently available in Beta that addresses this issue. Try reaching out to your Domo CSM to see if your instance can join the beta.