Allow manual entry of ID# on Add Constituent screen
We use RE as our secondary database and use the same ID# as the records in our Primary database, requiring the user to manually enter the ID# when adding the Constituent. This is possible in DBView. In WebView, one would have to add the record then go back in to edit the ID#, taking double the time, and our users are unlikely to remember to do so, which would leave records without any ID#
-
Mara Wolverton
- Sep 25 2024
- Reviewed: Voting Open
Related ideas
Agreed. We use multiple systems at our organization and it is helpful to have one common identifier across all platforms. The number we have to use comes from a different system that the RE users have no control over so we add that number to RE as the Constituent ID. We considered using the Attributes but did not see a reason in DBV since we could easily add the needed number to a standard field in RE.
I know we can go edit the Const ID in Webview but that seems counter-productive in adding a separate step AND burning a automated number in RE.
We do the same thing. Our Finance, student records, and HR use a different platform so employees, students, and grads come in with an existing ID number. I have to enter the person on the DB side so I can have the correct ID # to start with, then go to WV to add everything else.