kingaaronj Member

This same thing is happening to me now as I'm attempting to create some new datasets. Were you ever able to resolve it?

@jonathanlooker In addition to what @jstan said about adding a WHEN clause to prevent divide by zero errors, you have to make sure that the date range on your card is big enough to contain all data being compared. For example, if today (9/13/18) I am looking at data for last week Mon-Sun (9/3/18-9/9/18) vs the previous…

I agree, this could be better, but as a workaround, you could use a beastmode formula to compare your actual vs. your target, and then use that result as a summary number. Then you'd need to create two separate alerts (one for greater than, and another for less than). for example... let's say that your target is a number…

Thank you @ilikenno. I'll give this a shot.

No problem. Thank you... I'm going to consider using the radial gauge to see if it goes over well with my audience.

Hi @Shevy The comparative gauge card I'm referring to is pictured below. I believe you are showing a radial gauge.

Thank you for this @ilikenno. Very helpful! I actually noticed through trial & error that WEEK(`Date Column`) appears to give the same result as WEEK(`Date Column`,22) where the weeks start on Monday. Good to know.

Have you had any success or heard back from support on this topic? I saw your previous comment about utilizing DMAs, and am facing a similar challenge. I have a few advertisers I work with who operate on a DMA basis. I may use Lat/Long as a temporary workaround, but would love for support to add this, as I've done it…

Nice. Definitely let me know if that ends up working for you