Hi,
Currently reviewing with Development Staff here at the Met Opera how we will use/convert over from Solicitations to Plans. In our discussions, the following questions have come up and we were wondering if anybody else had come across these issues and how you have resolved them.
1) Is the current view on the Plans radio button a fixed view? Our solicitors are missing seeing the Status, Type and secondary workers at a quick glance. Can any customization at all be done to this screen?
2) Can titles on the Plan itself be changed? For instance, can you re-title "Primary Worker" to something else?
3) It appears that all current workers in v.11 get their own records in v.12. We have been debating whether we merge these records with any existing records for the workers (with their own personal organizational history) or do we need to keep them separate? Does this matter? We would like to know how other organizations have handled.
If anyone has feedback on any/all of these questions, we'd love to hear from you!
Thanks,Anthony
Good questions!
I can only speak to number 3; at City Center we have merged all of our Worker records with their existing personal records and haven't encountered any conflicts. Our Board members have portfolios of their contacts as well as Plans of their own for us approaching them.
-- Mike
Hi Anthony
Just another note on your point 3:
(Assuming you haven't actually migrated yet) - There is a mechanism in the v12.x migration process to associate users who have been used as Solicitors on some transactions with an existing constituent, so it won't create new constituenti for them, and you won't have to bother with the merge.
There is a migration report which will identify the users which do have solicitation entries, and you just need to find and enter the matching constituent ID into the User record in the Security module. (We asked consortium members to identify matching constituenti for their own users in a spreadsheet, then imported the matches with a script, which is a bit easier than updating them manually - after 10 years of use across six orgs there were quite a few)
Ken