Metric specific filters in chart builder #2120
nahiyan-yasaar-selise
started this conversation in
Ideas
Replies: 1 comment
-
|
Sounds like a good idea to me, will probably be implemented when some time is available. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently we are only able to set a chart-wide filter
However, we would also like to have metric specific filters.
This is so that we have one bar show "Count items with Status = Status1" and the next bar show "Count items with Status = Status2" for the same Dimension value
Example:
Our chart looks at the Account module. Dimension is set to UserSelector, so each Dimension item would be each users.
Metric1 is set to a simple Count, so the first bar for each person is total accounts under that person.
Metric2 is set to Status='Status1', so the second bar for each person is accounts with Status1
This can carry on for arbitrary number of statuses/metrics as per requirements.
Current workaround
We keep making more fields in the Accounts module named IsStatus1, IsStatus2 etc. with Field value expressions (e.g. Status == "Status1" ? 1 : 0) and have the relevant chart Metric SUM up those specific fields.
Issues with workaround
It can create an unnecessarily large number of fields for a simple chart depending on how many value types we need to see. Hampers scalability, which we are already facing.
The above module is a one-to-one connection to the actual Lead module just so we can separate out these chart-specific fields from the Lead module. And this is only for the Industry field. If our company creates a new Business Unit, then we would have to create one more field across all modules that deal with something similar. Even worse, if we need to see a chart that deals with a different field from Industry (example LeadStatus) then we would need to create as many fields as there are business units.
Additionally, for this specific example (where we are creating a different module), we are also forced to create workflows that creates, updates and delete a record according to changes in the Lead module.
Beta Was this translation helpful? Give feedback.
All reactions