Posts tagged CRM
Posts tagged CRM
Nonprofits needing workflow and project management software, be sure to give Podio a look as you explore the usual suspects (such as Basecamp).
A few highlights (from our perspective):
Some of the other features that we haven’t explored:
*As a condition of sponsorship, nonprofits must add this block:
Idealware and NTEN have a new report out about Donor Management Systems — we’re listed in the consultants directory in the back as a resource for nonprofits who want to install CiviCRM for Drupal or Joomla.
A Consumers Guide to Low Cost Donor Management Systems
Written in partnership with NTEN, this detailed, impartial report walks through the features that might be useful, summarizes and compares 29 different donor management systems that cost $4,000 or less in the first year, and provides detailed reviews of 10 of them…[more]
From social media to Social CRM: What customers want (The first in a two-part series)
A new study by IBM Institute for Business Value
This one is courtesy of a connection made at the #11ntc last week. We have a partner with an old CiviCRM database, upgraded many times over the years. At some point in the past, the upgrade failed to run completely (whether due to a bug or a server misconfiguration or something else) and now the database generates errors on every subsequent upgrade. The problem lies in a part of the database that isn’t used by our partners, so we haven’t invested a lot of time into figuring out how to fix it. Last week at #11ntc, I attended a CiviCRM session and posed the question to see what would be suggested. One of the other participants volunteered to share the solution with me and later emailed it to me (Thanks, Frank!). Behold:
Ensuring Schema Integrity on Upgrades
When a CiviCRM site is upgraded to a new version, there are frequently changes to the structure of the database. This may include adding or dropping tables, columns, indexes and foreign keys. Generally, the SQL upgrade script provided with each new version does a decent job of modifying the existing database to match the new schema.
However, there are occassionally issues during the upgrade which prevent a full implementation of the new schema. These issues generally show up as error messages or warnings during the upgrade. The procedures below are designed to reload the data into a new database which contains the exact schema needed to upgrade to the new release. We recommend you follow these steps if you’ve experienced any unexpected database errors or warning during an upgrade. We also recommend following these steps if your database as been through several version upgrades.
After running these steps, you can be confident that your database schema matches the current production version exactly, with all indexes, foreign keys, defaults and other constraints…