Data & Integrations

08:00 am should appear as 8:00 am; 10:30 pm should appear as 10:30 pm; etc. This would conform to the usual appearance of these times in the US.

Phone numbers with a country code (example: +1) and without a country code should not create "new information" to review in the Data Studio. Maybe have a setting where you can ignore the "default" country code for your organization

When importing funds into Almabase from Raiser's Edge (RE), it would be beneficial to have the option to search for funds using the 'Fund ID' field instead of solely relying on the fund description or name. Currently, the search function in Almabase allows only fund description/name searches, which may not always be convenient or feasible if you have several thousand funds in RE. Furthermore, when manually adding a fund in Almabase and connecting it to a specific fund in Raiser's Edge (RE), the only identifier currently supported is the fund System Record ID (External Database ID). Extending this capability to include the RE fund ID would be beneficial. Our team is accustomed to referencing funds solely using the Fund ID on RE. This will align with the practices of other Higher Eds, including EMU, where funds are commonly referenced using the Fund ID field.

Eastern Michigan University avoids using multiple employment relationship types in RE to minimize the number of fields they need to maintain, such as relationship type and reciprocal relationship. Instead, we rely solely on employment start and end dates to distinguish between current and former employment. For pulling accurate employment information from RE NXT, Almabase requires: Current employment to have the relationship type 'Employer' Previous employments to have the relationship type 'Former Employer' If this format is not followed, all former employment records appear with an end date as 'current' in AB, leading to data discrepancies. We'd like to request an enhancement to the current data pull process that allows Almabase to accurately classify employment records based on start and end dates rather than relying on specific relationship types.

In the United States, the standard date format used is "mm-dd-yyyy.". The site should have the option to use this format throughout for easy understanding.

We’d like to request a feature that enables the syncing of event participant attributes to Raiser's Edge NXT. Currently, we have to manually export participant data like dietary restrictions, meal preferences, and T-shirt sizes from Almabase and share it with the event planning team, which primarily works in Raiser's Edge NXT. This process is time-consuming and prone to errors, and it limits our ability to fully leverage the integration between Almabase and Raiser's Edge NXT. If we could sync our Raiser's Edge event category directly from Almabase, it would eliminate the need to manually select the event category after syncing an event from Almabase to Raiser's Edge NXT. I am posting this on behalf of Mickey McIntosh, Special Projects at Idaho State University.

Having the same email should add more weightage to how the system identifies as opposed to name because it's very likely for people to have similar first/last names but it's less likely that people share the same email. The system is not flagging profiles with the same emails as duplicates thus making it impossible to know if duplicates exist.

Pretty much what the title says. Prefix as in Dr., Mr., Fr., etc. and Suffix as in Jr. It seems to be an issue for at least two years as this post has not been resolved: https://feedback.almabase.com/data-integrations/p/allow-suffixes-to-be-downloaded Since we cannot view these fields in the Data Studio, they also cannot be exported. Also, there should be more options for Suffix other than Jr., including roman numerals (I, II, III, etc.).