SageCRM Switch and Save Promo
Between now and March 31, 2010, Sage is offering a switch and save promotion for companies that want to switch from their current contact manager or CRM solution to Sage CRM. Sage CRM is the world’s leading, on-premises, browser-based CRM solution. Read more
SageCRM 7.0 Features
Here is some of what’s coming in SageCRM 7.0, which is currently in Development Partner beta. Read more
Comparing SageCRM Editions
Confused by the different SageCRM editions (SageCRM 200, SageCRM 100 and SageCRM.com)? Wondering which one may be for you? Here’s a breakdown of the differences:
SageCRM.com
This is the cloud version of SageCRM. As a multi-tenant, hosted solution, SageCRM.com is instant-on and is paid for on a per user, per month basis (no long term contract required). For companies that want to get started quickly with a basic implementation of SageCRM, this is an option to consider. Read more
SageCRM 6.2 Beta Announced
With SageCRM 6.2 going into beta, the new features have been announced. Here’s an overview:
Branding Toolkit
SageCRM will now include alternative themes. Custom themes can also be created by customizing style sheets. Read more
SageCRM 100/200 Deployment Options
SageCRM.com is hosted, multi-tenant version of SageCRM. SageCRM 100/200 is the version of SageCRM that can be purchased. SageCRM 100/200 can be deployed in one of three ways: Read more
SageCRM Web Form to Case
Companies that are using or planning to use SageCRM for Case (Ticket) management are often looking for an anonymous Web Form to Case functionality, so that a customer can be prompted for a serial number or a specific software version — and this information will be sent to custom fields within the SageCRM Case record.
There are several ways that this can be set up, but the following is the best way to set it up when SageCRM is hosted within a company’s firewall: Read more
You May Need to Recreate Views Manually
The most enigmatic error in SageCRM is probably “You may need to recreate views manually.” There are several reasons why this can appear. Before making any changes to SQL Server, make sure to back up the database. Before making any changes to the Registry, back it up.
The “sa” User Password Has Been Changed
If the sa password has been changed in SQL Server and not in SageCRM, it will need to be changed in SageCRM. If the sa password is not known, it will need to be changed in SQL. Read more
Subscribe to Blog
with RSS Reader