Quote:
Originally posted by M. Alpert:
Hi Brian and Chelsea:
Having a preferred address selector wouldn't be much different than creating a custom field "preferred address". The core issue here is the fact that YM uses a flat file database, and any export requires manual sorting with or without a preferred address. The solution lies with YM moving to a relational membership database, whereby the preferred address could be selected by the admin when they're running the mailing report. Then the export would only contain the preferred address selected by the member. Using a Custom Query here is only a workaround because of a number of variables in play.
There are a myriad of other reporting deficiencies that would be solved with a relational database. If you were to look at a product such as CiviCRM or ISIS, you would see the difference in how these function compared to YM. Currently everything in YM has to be performed manually because fields can't trigger logic (yes/no) resulting in the display a specific queries (preferred address).
Thanks
Hi Mark,
You are correct in that just giving the member a way to select their "preferred" address is only half of the issue. We are also planning to add an easy way to the Custom Report feature to select the "Preferred" address fields.
Our database is a relational DB. In building the reporting module the intent was to remove any steps needed by a site administrator to link tables together and to know how that has to work so we built Views that contained all of the information needed. Some of these Views are dated and some restrict access to data and this was not intentional.
I am working on a top 5 list of improvements that we can do to the reporting feature and would be glad to have a discovery call with you so I can get your ideas.
Thanks Mark.