CRMs are must-have for any organization, large or small. There is some debate over what the “C” in CRM stands for - client, constituent, customer, etc., but at a very base level it manages information about your contacts. Organizations now understand that communication is not always linear, flowing to one central point. To further complicate things, organizations have a splintering of data from a multitude of tools. For example, maybe you are using Evite for event registrations, Salesforce to manage your customer communication, PayPal to collect donations, and Constant Contact for your email blasts. How can your organization get visibility into all of this data with it spread out amongst various systems and databases? The solution is CiviCRM.
Editor’s Note: I was initially going to make this one blog article, but since there are so many great features to talk about in CiviCRM, I’ve decided to break this up into...Read more
Over the past 18 months, the CiviCRM Core Team has focused heavily on project sustainability and on balancing our own internal capacity. During that time, our infrastructure has been consistently (and thankfully) managed by Mathieu Lutfy, a member of the Canada-based partner Coop SymbioTIC. While we’ve always considered Mathieu quasi-core-team, we’ve recently made it official and are very happy to announce that, in addition to managing the project’s infrastructure, he’ll now take on a greater role in its overall leadership.
Though the Core Team’s finances are always in flux, and often tenuous, we hope to expand the Core Team throughout 2017 to include a diverse set of individuals whose collective wisdom and guidance can take CiviCRM to a new level. Mathieu’s addition to overall project leadership is a first step toward deepening both our skills sets...Read more
CiviCRM Entity Reference Field is a submodule of the CiviCRM Entity project. One of the many advantages of installing the CiviCRM Entity module is the ability to use Drupal’s Entity Reference module to reference CiviCRM data from nodes, terms, or other entity types. Many people are using the Inline Entity Form module, which provides field widgets that allow you to create, edit, or delete a referenced entity from the parent form.
If you reference CiviCRM contacts via an Entity Reference field and use Inline Entity Form, you’ll often want to include the ability for the user to create or edit subsidiary CiviCRM entity types, such as the email, phone, and address entities. This can get tricky with CiviCRM integration. A regular entity reference field stores a target entity id in a Drupal field table of the Drupal database. CiviCRM Addresses are stored in the CiviCRM database, and can be created by different types of users and in many different ways. In addition, Drupal and...Read more
As of CiviCRM Entity 2.0-beta4 the sub module called CiviCRM Entity Price Set Field provides a Drupal field type for the Event entity type. In this article we’ll review the features of this submodule and discuss how to configure and customize it to fit your needs.
Event Registration on the Event view page
When configured to display on the Event view pages, this field generates a registration form that supports:
- Registering multiple Participants
- Uses the event’s price set and all price fields of any type
- Pay later or credit card transactions utilizing CiviCRM’s payment processing
- Default values for the profile fields corresponding to the logged in user’s contact information ...
Authorize.Net Sandbox: April 30, 2017
What does this mean?
CiviCRM Entity is a contributed module for tightly integrating and extending CiviCRM with Drupal. This module exposes CiviCRM API entities as proper Drupal entity types. This is HUGE as it allows you to make CiviCRM data available within your favorite Drupal tools such as Rules, Views, and EntityReference. I’d like to present another advantage of Drupal entity types, and that is Drupal fields.
By enabling CiviCRM Entity, you can add Drupal fields and associate with CiviCRM entity types such as Contacts and Events. In fact, any of the hundreds of Drupal field types can be used with CiviCRM Entity. You may be asking yourself, “Shouldn’t I use a CiviCRM custom field? Why would you want to use Drupal fields?” The correct answer is, you should choose the right tool for the job.
CiviCRM is great at having the business logic and infrastructure to support event registrations. CiviCRM has price sets, price fields,...Read more
WHAT'S NEW IN CIVICRM 4.7.18
- Core CiviCRM updates:
Before I started working as a CiviCRM consultant, I was a CiviCRM user at a small nonprofit. We got a large chunk of our revenue through grassroots donations, but we never had an opportunity to see how we compared to other organizations like ours.
(TL;DR – you should install the Individual Donor Benchmark Survey extension, run the report, and submit your survey response.)
Nowadays, some proprietary donor databases collect users’ data and publish reports, but besides being creepy, they can’t get good data without involving organizations directly. They also only cover users of a single software system.
Besides, how do you know the data covers organizations like yours?
The Individual Donor Benchmark Survey was developed by Third Space Studio to address these...Read more
Thursday 23th and Friday 24th of March we are having a mini-sprint in the Ede (NL) in which we will fix CiviCRM bugs. We are with four of us already (Erik Hommel, Alain Benbassat, Klaas Eikelboom and me) so it is going to be fun! That is the main reason and the other reason is that we want to contribute to CiviCRM Core.
Our plan is to have two days for fixing CiviCRM bugs once in the month or once in the two months. But at least regularly and fitting to our busy schedule.
So if you are in the neighborhood we want to invite you for joining us so it going to be more fun.
The dates we have planned so far are:
- Thursday and Friday 23th and 24th of March (in Ede, NL)
- Thursday and Friday 18th and 19th of May (location to be decided, possibly Antwerp)
If you want to join us drop me a message on the chat or send me an e-mail on firstname.lastname@example.org
Nearly 78% of sites using CiviCRM are on either version 4.6 or 4.7 (check out CiviCRM stats online). Why is that significant? Because those are the only two community supported releases currently. If you’re not on one of these versions, most importantly, don’t be alarmed. There might be a reason you’re not… perhaps you’re using a partner that continues to support an previous version, or have customizations that prohibit an upgrade. If that’s the case, feel free to skip the rest of this post. But, if there’s no good reason not to upgrade, then read on.
What do we mean when we say that 4.6 and 4.7 are the only versions being supported? Well, just that. CiviCRM 4.7 is the latest stable version of the software and is the primary focus of the Core Team. Version 4.6 is the current LTS, meaning that security updates (but not new features) will be back ported to it for a not-yet-determined amount of time. If you’re on any other version, then...Read more