Welcome to the BrightGauge Enhancement Forums

When you add multiple filters to a board, it would be great if you could exclude certain filters from gauges instead of excluding them all 

If you have a number gauge that has several tabs that are hidden and used to create calculations, the names of the tabs are just displayed as generic names, like "query1_amount_sum" or "calc_metric_1". It's frustrating trying to remember what the tabs are actually for, so you have to "unhide" them to seeing what they actually do.

Can you work on the ability to name the layers as they are displayed along the left side panel (see #2)?

I was just informed that when using the Products dataset "Only products updated in the last 24 months will be represented." and "we focus on products that are actively being used. This means that we only include products that are associated with a ticket, agreement, or sales order"

This makes no sense to me. I'm looking to create a snapshot gauge so I can see at a glance how many products I have, and see the same data by category and subcategory, so we can keep the product catalog clean. Since this dataset does not include all the products in the product catalog (not even all the active ones) it would be incomplete.

We have over 30 pages of gauges and 10 people across the organization that are creating gauges (Leadership, Directors, Managers). I can guarantee that there are duplicated gauges and gauges that were created years ago that haven't been used. 

I know I can filter by unused as well as last updated but that doesn't give the full picture. It could have been last modified and last used a week ago. 

I want to be able to filter based off last maintained AND last used (on a Dashboard/Report/Goal) was 6+ months ago. Having a last used field that would be updated daily would be beneficial. 

I was under the impression that I had virtually unlimited access to tables and fields in on-premise applications such as QuickBooks with Brightgauge??  The first attempt at a gauge I attempted was for my retail division... to show daily sales by payment method (Cash, Credit Card, Check, etc.)... no such fields are available.

These limitations are very crippling and disappointing with this otherwise potentially impressive product.

Back to the drawing board with the horrible QB Advanced Reporting Tool, which is similar to PSA Report Writer, which I assume I will also have to use for a lot of what I still need out of PSA as well.... we will see.

Hey team, would like to be notified anytime a dataset sync interval is missed 

The Invoice Data dataset contains fields like updated_by and adjusted_by, but not created_by, which seems like a big oversight. We need to be able to report on who created invoices, and the workaround we've been given is to create a custom field, which would rely on someone manually setting that every time they create an invoice.

Filter for dates should have an "Earlier than (n) Months ago" for monthly snapshot data scenarios. 

On past-looking data, we can use 2 filters to achieve a specific, custom range: Last (n) Days // Earlier Than (n) Days Ago

This solution works for looking at date ranges in the past.

BG has Last (N) Days, Earlier than (N) Days, within Next (N) Days, but does not seem to have After (N) Days. I would expect that to be there since it is very similar to the Earlier than (N) Days filter.

I will start with the past-looking metric to explain better:

1. Past-Looking Data
1. Need: Opportunities where date_became_lead is between 90 – 180 days ago
2. Solution:

1. Filters:
2. Filters:

1. Date_became_lead = Last (n) Days {180}
2. Date_became_lead = Earlier Than (n) Days Ago {90}
3. The combination of these filters yields a list of opportunities created between 90 – 180 days ago, which achieves the purpose.
1. Forward-Looking Data
1. Need: Opportunities where expected_close_date is between 90 – 180 days in the future
2. Solution:

1. Expected_Close_Date = Next (n) Days {180}
2. Later Than = FIXED DATE
3. The combination of these filters yields a list of opportunities closing within the next 180 days and which are also after a fixed date;
1. We need this to be dynamic, like it is with the past-looking/”earlier than” data.