ARosser Member

We are seeing the same thing. I would really like a post-mortem. This is the 2nd major release that has taken down reporting related to AppDB stuff for us.

No update on my ticket. I haven't even gotten a message beyond the initial "we got your ticket" email. It is extremely frustrating.

Yes. I have done all of the troubleshooting steps in this article. Additionally, this is an app that has been in use for almost 2 years and nothing has changes in at least 6 months.

I have already made the optimization as I stated in the reply to my original post. Nothing in documentation around MySQL data flows says anything about "Explain SQL" being limited to Redshift. If that's the case, can someone point me to that documentation?

Well I managed to get it optimized and running in 2 minutes by adding a filter transform at the very beginning. I would still like to understand why the "Explain SQL" option is greyed out.

I know this post is old, but it is exactly what I'm looking for. The link you posted above appears to be dead. Can you provide a new link?

I'm seeing the cut-off issue on all dashboards where I have cards at their minimum height. Specifically filter cards in my case. This is all dashboards with or without PDP. The PDP icon issue is only on PDP enable dashboards.

Thank you. That did it. Not sure how I missed that in the documentation.

I don't see it in the documentation for Group Management so I'll ask here. Can you create/manage Dynamic Groups? Essentially I would like to create a group where the user is in both the Office Manager AD group as well as the Division AD group.

It's not ideal as the data is getting aggregated and pivoting the data will make things more complicated. Using your example above the revenue for a single record is $100. With the pivot it becomes $300 using a simple sum. If I use AVG or MAX I lose the ability to aggregate in the report using beast modes because totals…

Same

After a call with Domo support I was able to get an answer. Since there are 3 different datasets I have to select the PDP policy for each even though they are all named the same thing. I was able to impersonate an end user and it works as expected from their end. It's just an issue/extra step for an Admin that is testing.…

I submitted a ticket late Friday. Hopefully there will be movement soon.

I am seeing the PDP icon at the bottom of all the cards. They all have the icon. They just aren't responding to changes in the selected policy.

I am using the ability to select specific policies to QA the dashboard. I do not believe this is a filter issue as I have verified at least 3 times that all of the policies are identical on each dataset. There are no dashboard filters. If I remove the card on the AR Data Mart (the only PDP working when all 6 cards are…

If I add a filter for Division to the dashboard all 6 cards filter as expected so I know the values are correct. I have created the PDP policies for each using PDP Automation. I copy/pasted the policies from Accounts Receivable Data Mart (first of the 3 to be created) and updated the dataset id in the webform that triggers…

Yes. And all cards have the PDP icon. Additionally, if I view the cards individually PDP works without issue. It is only not working when I am on the dashboard with all 6 cards.

I've gone through the knowledge base article several times myself. Yes, all of these datasets have been running successfully for months.

I didn't think that would work because text and number fields usually don't work well together. But it did! Thanks everyone for the ideas!

I have come up with a potential solution. It feels very bulky at the moment and there is one annoying element. I created 2 textbox variables, 'From' and 'To'. I set the defaults to 1 and 365 respectively. The intent is to dynamically select the desired range. I then modified my beast mode. CASE WHEN MAX(CASE WHEN Days…

In the case that the range selected was 0-180 (1-30,31-60,61-90,91-180) then yes, Customer B would also be included. I do have the raw Aging days. The frustrating thing is that by using the Aging Range or Aging Days the reports seems to filter on those before filtering on the Include/Exclude flag. Either that, or the…

Thanks. I am able to get it to work using a variable, but I was really hoping I wouldn't have to. One of the most highly requested feature when I first convert this report from Excel was the ability to filter on multiple ranges. As variable only allow single select that kills that. Ugh.

No worries. I was wrong anyways. It's not working. I swear it was, but I'm back to just filtering by the ranges selected. Ugh

I was able to figure it out in the end. Thanks for the jumping off point. CASE WHEN MAX(CASE WHEN Aging Range IN ('1-30','31-60','61-90','91-120','121-150','151-180','181-365','>365') THEN 1 ELSE 0 END) OVER (PARTITION BY Customer) > 0 THEN 'Include' ELSE 'Exclude' END

Thanks for your response. I'm following the logic, but I'm guessing I wasn't clear enough. The user has the ability to select from multiple ranges. Maybe my brain has just decided to take a vacation, but I can't put 2 and 2 together.

That's the one I've been looking at primarily and It's really not getting into the detail I need. I guess what I'm needing is something that combines the set up process as well has the functionality. I have a column currently that I can use as a flag. If [Flag] = 'Done' THEN do nothing If [Flag] = 'Create' THEN Append If…

Thanks. I ended up making a few modifications to the base dataset so I could attach the alert to it. Good to know that only views seem to be impacted.

That's what I did to get an alert running again, but the column values I had setup previously are not working. This is the email I got this morning.

@ColemenWilson That seems like the best option. Now to go down that rabbit hole.

But it appears I am getting dinged on my credits for the rows themselves in those datasets. As an example, this dataset hasn't run in 9 months.