You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great contribution to the much needed improvement of presentation and analysis of memberships for CiviCRM. I'm using it on a couple of sites, and plan to roll it out across more sites that I support where membership is used. So thank you for that.
One thing that would be really useful for me would be the ability to focus solely on primary memberships, filtering out memberships that are created by dint of a relationship. One of the main sites I look after works with organisational members, and while it is valuable to be able to chart the change in memberships by relationship, it would be super useful to be able to see just the changes in primary memberships.
Thanks again for your work on this.
The text was updated successfully, but these errors were encountered:
Hi @Upperholme yeah, makes perfect sense. We'll need to work out how best to do it i.e. it could be a configuration option or it could be a filter on the display. My feeling is the latter will be more difficult and therefore we'll lean toward the config option unless theres some budget available.
This is a great contribution to the much needed improvement of presentation and analysis of memberships for CiviCRM. I'm using it on a couple of sites, and plan to roll it out across more sites that I support where membership is used. So thank you for that.
One thing that would be really useful for me would be the ability to focus solely on primary memberships, filtering out memberships that are created by dint of a relationship. One of the main sites I look after works with organisational members, and while it is valuable to be able to chart the change in memberships by relationship, it would be super useful to be able to see just the changes in primary memberships.
Thanks again for your work on this.
The text was updated successfully, but these errors were encountered: