Sage CRM 7.2 Patch Release Notes (Patch E June 2014)

Sage CRM
Sage CRM 7.2
Patch Release Notes

© Copyright 2014 Sage Technologies Limited, publisher of this work. All rights reserved.
No part of this documentation may be copied, photocopied, reproduced, translated, microfilmed, or otherwise duplicated on
any medium without prior written consent of Sage Technologies Limited.
Use of the software programs described herein and this documentation is subject to the End User Licence Agreement
enclosed in the software package, or accepted during system sign-up.
Sage, and the Sage logo are registered trademarks or trademarks of The Sage Group PLC. All other marks are trademarks or
registered trademarks of their respective owners.

Contents
Overview...............................................................................................................................2
Prerequisites .....................................................................................................................2
Latest Version ...................................................................................................................2
How to Install Sage CRM Patches.....................................................................................2
Patch E.................................................................................................................................3
Blog: Find out how to set up Sage CRM to work with Exchange Server integration 2013. . 3
Patch E Issues List............................................................................................................3
Patch D...............................................................................................................................18
Patch D Issues List.......................................................................................................... 18
March iPhone app updates.............................................................................................. 25
Additional notes on this patch (D).................................................................................... 26
More information around 0-156120-QA........................................................................ 26
Working with the Exchange Outlook plug-in with IE 11 installed on your machine........ 26
Patch C...............................................................................................................................27
Patch C Issues List.......................................................................................................... 27
Patch B...............................................................................................................................33
Before installing...............................................................................................................33
Edit and save your existing Notifications...................................................................... 33
Check your customizations .......................................................................................... 33
Patch B Support ..............................................................................................................35
Patch B Issues List.......................................................................................................... 35
Rolled-up Fixes ...............................................................................................................59
Patch B Known Issue ...................................................................................................... 59
Patch A...............................................................................................................................60
Patch A Issues List.......................................................................................................... 60
Patch A...............................................................................................................................62
Patch A Issues List.......................................................................................................... 62

Sage CRM 7.2 Patch Release Notes 2
Overview
This document provides details of all Sage CRM patch releases for version 7.2. Installing the
most recent 7.2 patch (E) ensures that you get all of the fixes included in earlier patches (if
applicable).
Prerequisites
You need to have Sage CRM 7.2 installed before you install the latest patch. You can find
out the version of Sage CRM you are running from the Logon page, which would read ‘CRM
version 7.2’, for example.
Latest Version
Latest Release: Version 7.2
DLL: 7.2.0.3
How to Install Sage CRM Patches
Use the following procedure to install the latest Sage CRM patch:
1. Back up the existing CRM eWare.dll and database. The DLL is stored in the CRM
installation directory, which is commonly in
…Program FilesSageCRM<Installation Name>WWWRoot
2. Run the Setup.exe file .
3. When using the InstallShield wizard, you can choose to use either Windows
authentication (using the credentials of the user logged in to the system at that time)
or SQL Server authentication (by entering the appropriate SQL Login ID and
Password).

Patch E
Released June 2014
Files included DLL version
Outlook plugin
Document plugin
CTI plugin
7.2.0.3
7.2.0.3
7.2.0.2
7.2.0.2
Blog: Find out how to set up Sage CRM to work with Exchange
Server integration 2013.
For those of you who’d like to work with Exchange 2013, please find out about the
configuration steps in the blog below:
https://community.sagecrm.com/partner_community/b/hints_tips_and_tricks/archive/2014/06
/18/configuring-exchange-server-integration-to-work-with-exchange-2013.aspx
Patch E Issues List
Note: The message “This issue could not be reproduced” in the Status column means the
issue could not be reproduced on the latest version and patch. An upgrade to the latest
version and patch should resolve the issue.
Ref ID Area Description Status
0-149773-QA Cases When a user saved a Case
record, if a required field
wasn't filled in and if the
Case SLA was set to None,
the case id was
incremented by 1 and all
entered data was lost.
This issue is fixed.
0-151511-QA Cases On the Case screen, a user
added StartTime, Endtime
and Minute fields. The
Minutes field (called
Duration) didn't calculate
the difference between
StartTime and EndTime.
This issue is fixed. Please
note that if you create a
Minutes field for Cases, you
should not call it
case_duration because a
case_duration field already
exists in the case_progress
table and this would create
conflicts between the two
fields.
0-155513-QA Cases On an integrated version of
Sage CRM, if a user
created a new Task from
the context of a Case, the
Account field wasn't
automatically filled in.

0-156142-QA Component
Management
It wasn't possible to record
the creation of a Dashboard
template using Component
Manager, and then export it
to another install.
Management
It wasn't possible to record
the creation of a Gadget
template using Component
Manager, and then export it
to another install.
Management
When a user created a
component to record the
creation of a new
Dashboard, the custom
captions for the Dashboard
weren't recorded into the
component.
This issue is fixed. If the
component is blank then set
it to be the active
component. Otherwise, the
generated component script
will not include the
translations associated with
new gadgets and this will
cause an error with the
landing page gadget list
load.
0-154178-QA Companies /
People
When working with email in
pop-up mode, it wasn’t
possible to select multiple
recipients by clicking
different email addresses in
the system.
This issue could not be
reproduced.
People
After merging two
companies, the Marketing
tab for the merged company
still contained two records,
instead of just one.
reproduced.
People
On 7.1h, a user created a
new Person in the context
of a company, and set their
address to Person Only.
Updating the address of the
new person also updated
the address of the
company.
reproduced.
People
When a user added more
than 12 people to a
company, the People grid
contained duplicate people
records, while others were
missing from the grid.
People
It wasn't possible to select
all contacts from the
Contacts list, and delete
them in Sage CRM.

0-155267-QA Configuration Time zone settings for
Central Time (US and
Canada) were out by one
hour.
The documentation has
been updated with the
following note: “If the
Automatic Daylight Saving
Time option is checked in on
the server machine, then it
will affect all users, even if
they have not selected this
option themselves in their
time zone settings”.
0-157257-QA Core Product On a user install with a
multi-server environment,
the user kept getting a 'You
may need to recreate views
manually error' at the same
time every few days.
0-157373-QA Core Product In Sage CRM, there was an
issue with appointments
ending at midnight.
0-148695-QA Customization Adding a new field linking to
a secondary entity on the
Case Progress screen
broke the link to Person on
the screen.
0-148764-QA Customization A user added a Date only
field to the Person entity
screen. The field couldn't be
populated.
0-148884-QA Customization In Administration |
Advanced Customization |
System Menus | Find,
clicking Save created a
duplicate Solution row on a
user install.
0-151819-QA Customization After a user added a
custom Opportunity list and
filter box, the value of Filter
Box name was populated
with the custom content list,
and displayed on the
Opportunity Find screen.
This can't be fixed. The
workaround is to run the
following script.
<script>
$(document).ready(function(
){
if
(crm.getArg("OBN").toLower
Case() ===
"salescommunications" &&
$(".CONTENTGRID tr
td:first").hasClass("VIEWBO
XCAPTION")) {
$(".CONTENTGRID tr
td:first").remove();
}
})
</script>

0-152661-QA Customization It wasn't possible to change
the type of a numeric field
mirrored with a progress
field.
0-152955-QA Customization A user was unable to
customize the Line Item
screen using inline
customization.
0-154748-QA Customization It wasn't possible to create
a field on Opportunity
Progress and Opportunity, if
the fields used the same
name.
0-154994-QA Customization When an email containing a
RecordAnchor was sent
from a workflow rule, the
record anchor didn't link
back to the specified
record's Summary tab.
0-155777-QA Customization It wasn't possible to clear a
case field which had been
added to the case filter box.
0-156417-QA Customization A user was unable to create
an Opportunity gadget on
the Dashboard after adding
a custom search select
advanced field on the
Opportunity entity screen.
0-156549-QA Customization It wasn't possible to create
dashboard gadgets based
on custom primary entities
with an underscore symbol
in the entity name.
reproduced.

0-156646-QA Customization A user wanted to use the
Company restrictor field on
Opportunity and use it as
part of the Opportunity
workflow. This didn't work
as expected when workflow
was turned on.
This is by design. The
Restrictor option only works
if the field that you're
restricting by is on the same
screen. You can't put an
advanced search select field
on its own onto the workflow
screen.
However, if you also add the
comp_primarycompanyid to
the workflow then the
restriction will work. That is
to say, you should add in a
new action for Display Field
for Amendment and select
the
comp_primarycompanyid
column on the same
workflow rule where you’ve
added in the
oppo_erpaccountid action.
You can set it to be read
only if you like. Now, when
you activate the Qualify rule,
the erpaccountid will be
restricted to the company
selected.
0-156665-QA Customization It wasn’t possible to create
a workflow based on a
custom Opportunity search
select advanced field. The
dropdown field was blank.
0-156865-QA Customization A user wanted to create
new buttons based on
Quotes and Orders, and
use SQL queries for these
buttons
This issue is fixed. Quotes
and orders were added to
the list of possible entities in
DoesSQLMatch fn.
Quotes will use vQuotes to
query. Orders will use
vOrders.
0-157712-QA Customization When a user clicked a
custom button on the Main
Menu area, the URL
opened in a new page
instead of being displayed
in the L frame.
0-157810-QA Customization In Administration |
Customization | <entity>,
when a user clicked 'Show
Logs' for Table Level
scripts, the popup window
would prompt the user to
log in again, and the logs
weren't displayed.

0-157874-QA Customization Customization screens for
‘CommunicationFilterBox’
were inconsistent
depending on whether they
were accessed from the
Administration |
Customization area or from
the inline customization
mode.
0-158241-QA Customization When a user created a
DateOnly field, for example
on Opportunity, and
displayed it for amendment
as part of a workflow rule,
the field value was one day
off (previous day).
255-146541 Customization An issue with metadata
prevented custom primary
entities from appearing in
the User Security Profiles
area.
0-154518-QA Customization
Wizard
After creating a custom
entity, a user was unable to
change the user on a
custom record.
0-156834-QA Database It wasn't possible to create
email notifications.
0-149257-QA Data Upload It wasn't possible to import
an Excel file containing line
feed characters.
0-152722-QA Comms/Diary The Date picker popup
window on the Recurring
Appointment screen was
too small.
0-152860-QA Comms/Diary After sending an email to a
group, the communication
under the Person tab didn't
display the person's contact
details.
0-153181-QA Comms/Diary There was an issue with the
default values for Date/Time
fields.
0-154957-QA Comms/Diary The Task Reminder and
Time fields didn't default to
a set time when selecting
them.

0-156461-QA Comms/Diary When accessing a
Company from the Recent
list, when the user tried to
create a new Task from the
company's Communications
tab, the Regarding field was
filled with an unrelated
Opportunity.
0-156463-QA Comms/Diary When moving an
appointment back in time,
the End Time wasn't
calculated properly.
0-156863-QA Comms/Diary When creating an
appointment for several
attendees, including
external ones, the Team
CRM Calendar displays an
appointment icon for the
CRM user and for each
attendee as well.
This is by design. These
"duplicate" icons cannot be
removed as it could affect
some customer installs.
0-157464-QA Comms/Diary After sending an email to a
group of people, if a user
deleted the communication
in the context of one
Person, all emails sent to
the group were deleted.
This issue is fixed
0-158346-QA Comms/Diary On an install, there was an
issue with Date for users
using Pacific Daylight
Saving Time.
This issue is fixed. We
remind you that if the
Time option is checked in on
the server machine, then it
will affect all users, even if
they have not selected this
time zone settings.
0-158243-QA Documentation A user wanted to know if
Solo was supported on
Windows 8 tablets.
This issue is fixed. The
Software Support Matrix
was updated to reflect that
Solo is run on versions of
Sage CRM which do not
support Windows 8.
0-157040-QA E-Marketing
(SageCRM)
A user was unable to send
out a mail blast using e-
Marketing.
reproduced.
0-151707-QA Exchange
Integration
If an external attendee
refused a meeting invite,
they would keep on
receiving invites, each time
the appointment was
updated.
reproduced.
Integration
A user had an issue with
Exchange Integration. The
integration failed every time.

Integration
On an install, users
received meeting
notifications for past events.
Integration
There was an issue with the
Exchange/Sage CRM
synchronization where
'Display as field' wasn't
always updated properly.
Integration
On a user install, Exchange
integration failed when
Contact Synchronization
was enabled.
Integration
Exchange didn't work
properly because of a
mismatched URL issue.
0-157948-QA E-mail Manager A user had a query about
filing emails issues where
the Communication record
didn't always pick up the
sender's email address after
filing.
This is by design. The 'From'
email address should
always be associated with
the user. If it is not, no email
is filed and you receive the
following error message:
'No Users exist for this From
email address'.
0-152900-QA Find / Advanced
Find
When using Advanced Find,
the wrong error message
was displayed when a user
tried to set an AND/OR
operator on the last row.
0-146358-QA Field Level
Security
After denying read/write
access for
oppo_primarycompanyid to
everyone on an install, the
Company tab was still
available from the top
content.
This is by design.
Security
A user wanted to hide a
field from all users, except
the System Administrator.
The field was still visible to
other users during the chart
design process.
Security
If a user with no read/write
access to a field on, for
example, a Company
record updated the record
and saved it, the field would
become blanked out when a
user with read/write access
to the field tried to edit the
record next.
reproduced.

0-159157-QA Keyword Search It was not possible to do a
Keyword Search on Quotes
and Orders on an install
integrated with Murano.
This issue is on Murano's
side. The customization
package with correction is
set to appear in their June
release.
0-158603-QA Dashboard
(Interactive)
It wasn’t possible to create
an SData gadget based on
Forecasts.
0-156037-QA Leads After converting a Lead to
an Opportunity, the
communications against the
Lead record didn't load
properly.
0-157638-QA Leads The Lead Ratings icon is
missing from the product.
This is by design. It seems
as though the lead_rating
icons were never in the
product with demo data.
Sage CRM doesn't have
icons available for all
selection fields in the
product. A user could create
these icons and put them in
the install files.
A request for enhancement
can also be raised if
needed.
0-159296-QA Leads In the context of a Lead
when a user clicked 'Add or
Find this Company', the
Company 'Industry' field
was displayed as segment
instead, and the default
values set up for Company
entry were ignored.
This issue is fixed. If you
have a comp_industry field
then lead_companyindustry
maps to that, if you don't
then it will map to
comp_sector.
0-156196-QA Mail Merge Mail Merge failed on the
tenth and last page of a
user document template.
0-147715-QA Mobile The Date/Time picker was
displayed in English in
tablet mode on a French
install of Sage CRM with a
French OS tablet.
reproduced.
0-147759-QA Mobile When working on mobile
with the iPhone/Android
theme, it wasn't possible to
view the company and
person linked to an existing
communication, or to create
a new company and person
from the context of a new
communication.

0-150545-QA Mobile On an account integrated
with Sage 300, the
Company Summary screen
couldn't be displayed on
iPhones if a term code was
added to the screen.
0-151884-QA Mobile It wasn't possible to search
for Opportunities by Close
By date when working on
iPhone.
0-154517-QA Mobile When working on iPhone in
Safari, the Date/Time
display didn't match the
Sage CRM user
preferences.
0-154782-QA Mobile It wasn’t possible to search
on an integer field on tablet.
0-155043-QA Mobile It wasn't possible to call
someone by tapping the
phone number displayed on
a record Summary screen
on iPhone.
0-156947-QA Mobile It wasn’t possible to sync
the Sales Tracker app for
On Premise installs
integrated with Sage 300.
reproduced.
0-157585-QA Mobile It wasn't possible to open
hyperlinks on customized
entity grids on the
iPhone/Android view.
Customers still need to
recreate the grids in order to
get this working on installs.
The fields need to link to
custom_lists and customid
fields, rather than tabs for
mobile display.
0-157569-QA Multi Server There was an issue with an
install where users kept
getting logged out.
0-151129-QA Navigation A user created a custom
entity with the 'has library'
option. After creating a
record for the new entity,
the user clicked a
document, saved it without
editing, and then clicked
Back. The user was
returned to the list of all
library entries in the system.
reproduced.
0-152168-QA Order
Entry/Products
A user with info manager
product rights with the rights
to view/edit Opportunities,
but with no rights to insert
was unable to add new
product families.

0-152632-QA Outlook Integ -
Classic
After filing an email to CRM,
it wasn't possible to edit the
About field for Company
and Person.
reproduced.
Classic
The option to install Outlook
Plug-in was missing from
the Preferences screen
when the 'Allow ActiveX
Document Drop' option was
set to No.
note the Install Outlook plug-
in option is only available on
IE.
0-158786-QA Outlook Integ There were issues with the
Outlook plug-in when
Outlook was set to the
Chinese locale.
Exchange
On an install integrated with
Sage 200, it wasn't possible
to file an email against a
contact which wasn't in
Sage CRM.
Exchange
A user with restricted
access to some entities
could not file emails to Sage
CRM.
reproduced.
Exchange
A user was unable to work
with the Exchange Lite
plug-in on IE 11.
look at Working with the
Exchange Outlook plug-in
with IE 11 installed on your
machine, on the 7.2d
section of this patch release
notes.
0-153994-QA Quotes / Orders When you created a quote,
the auto-generated
reference number excluded
deleted quotes, meaning if
you deleted a quote, it was
possible to have a duplicate
reference number.
0-156108-QA Quotes / Orders The Order screen checkbox
for "Include in quotes total"
was set to a default Y value
in Administration. Yet, this
wasn't reflected on Order
screens in My CRM.
reproduced.
0-158797-QA Quotes / Orders On installs integrated with
Sage 1000 ERP, when
creating a new Quote from
the context of an Account
record, the Account details
weren't automatically filled
in.

0-150810-QA Reports If a user created an
Opportunity Summary
report and used 'oppo
forecast' as a selection
criterion of the report, the
report's results weren't
filtered properly.
0-152555-QA Reports When exporting a report to
PDF, line feeds were not
preserved.
0-152655-QA Reports After navigating to a report
category in Sage CRM, a
user received an error
message after clicking the
report category link in the
top content.
0-152656-QA Reports When a user filtered a
report list, the top content
breadcrumbs disappeared.
reproduced.
0-156043-QA Reports A user had issues with
generating a chart. The
legends seemed duplicated
because of an incorrect
setting in the Chart Options.
0-156875-QA Reports Users received a 404 error
message when running a
report onscreen, if the
report name contained a '+'
character.
reproduced.
0-157216-QA Reports On a 7.0 install, if you
create a report looking for
opportunities closed in the
previous week, you get
results from the wrong year.
reproduced. This is not an
issue in 7.2
0-157467-QA Reports Date formats weren't
displayed properly in .csv
output when the Windows
Regional Settings didn't
match with the Sage CRM
date format.
This could not be
reproduced.
0-158349-QA Reports When a user ran a cross
tab report, for example
'Activities Logged Report by
User', the chart data and
the report data didn't match.
0-158285-QA SData Provider Users working with Office
Line needed the ability to
use RTDV (Real Time Data
View) tables in Opportunity
tabs to display orders and
quotes, along with their line
items.
OfficeLine team produced
the customization, and the
Sage CRM team unblocked
it for the Opportunity entity.

0-158207-QA Soap Integration On an install integrated with
Sage 200, there was an
issue with the
synchronization of deleted
shipping addresses.
0-159410-QA GCRM Account On an install integrated with
Accounts, it wasn’t possible
to display Companies’
Communications view.
option ‘errorhandling=strict’
is now the default setting
when installing a
component, which should
reduce the amount of errors.
0-149309-
ENH
GCRM
Integration
There was an issue with
setting up component on
integrated installs.
0-157207-QA GCRM
Integration
A user had an issue with
displaying Sage CRM on
Mozilla.
0-158017-QA Timings There was an issue with the
Holiday Set field when
creating a new SLA.
0-145385-QA Translation
(English prod)
When adding regions to
Sage CRM, the
deduplication process
allowed the creation of
duplicates when sentence
case was used. For
example, 'africa' wasn't
recognized as a duplicate of
'Africa'.
(English prod)
On a user install, it was not
possible to create a gadget
based on a Company
SData feed.
reproduced.
0-144679-QA User Interface The "Home" caption (for
homepage) was incorrectly
translated as "Domicile" on
French versions of Sage
CRM.
caption was changed to
"Accueil".
0-148531-QA User Interface A user wanted to use a
custom favicon.ico for Sage
CRM, instead of the
standard IE logo.
This issue is fixed. You can
change the icon in
WWWRootThemesImgdef
aultIcons
folder.
0-152039-QA User Interface When navigating to the
Security Profiles area in
Administration, a user
received an error message
when clicking the Security
Profiles link in the top
content.
0-154083-QA User Interface A user wanted to open a
case in a new tab in order
to assign it to someone.
This is by design. Sage
CRM can be used in one tab
only.

0-156950-QA User Interface When inserting an inline
image in an email, the
image didn’t get inserted at
the mouse cursor position.
Instead, it was inserted at
the bottom of the email.
0-157610-QA User Interface In 7.1 SP2, it wasn't
possible to delete a user
territory, even if all users in
the territory had been
deleted first.
0-158120-QA User Interface A user wanted to display
comp_accountid on the
Company screen.
This is by design. Any
columns that end in
'accountid' are used for
installs integrated with Sage
Accounts. Users shouldn't
create columns with that
name. The workaround is to
call the column something
like 'xxx_account_id'
instead.
0-152169-QA User
Management
If a user logged into Sage
CRM on an Android mobile
device then logged in on a
desktop machine, the
Android Sage CRM session
didn't terminate.
0-154313-QA User
Management
Using Activity Tracking, it
wasn't possible to track the
actual length of a user login
session, if said user closed
the Sage CRM browser
window without clicking Log
off first.
This is by design. Users
should click Log off before
closing the browser window.
A System Administrator can
also set a User Inactivity
Timeout time which will
automatically log off inactive
user sessions after a set
period of time.
0-158523-QA User
Management
A user was having difficulty
with setting up teams for
other users on the install.
0-158637-QA Web2lead It was not possible to use
web to lead forms if a Date
field was added to the
screen.
0-154958-QA Web Picker The Calendar date picker
was displayed off-screen
when working on a reduced
browser window.
This issue is fixed on IE10.
0-157677-QA Web Services A user working with
integrated Sage 300 had an
issue setting up Web
Services.
This issue is fixed. The user
hadn't correctly marked the
relevant tables as available
for web service access.

0-152130-QA Workflow It was not possible to use
workflow primary rules
using a custom view. No
Progress button was
displayed onscreen.
0-152502-QA Workflow When the Start Mail Merge
functionality was part of a
workflow, the fields for Type
and Category were not
displayed.
0-153803-QA Workflow When editing a workflow,
the available rules were not
displayed if a user scrolled
down the workflow tree.
0-154010-QA Workflow When a user added a
disabled rule to a workflow,
there was no prompt to
notify the user that the rule
was disabled.
0-156245-QA Workflow A user had an issue with
setting up the Opportunity
workflow.
This could not be
reproduced.
0-156645-QA Workflow It wasn't possible to change
the currency of an
Opportunity if a default
currency value was
specified in the Opportunity
workflow.
0-158818-QA Workflow When using a Send Email
workflow action, the email
sent displayed the wrong
record anchor.

Patch D
Released March 2014
Outlook plugin
Document plugin
CTI plugin
7.2.0.5
7.2.0.3
7.2.0.2
7.2.0.2
Patch D Issues List
0-156965-QA Registration
Form
When a user installed 7.2c,
the following error occurred:
"Cannot create machine ID:
Machine Mac Address Can't
be determined".
0-157189-QA Campaign
Management
A user with Info Admin
rights was unable to use
Response Set Up for
outbound calls in the
context of a new wave item.
Management
A user wants an outbound
call list to be sorted in the
same order as the group it
is originally based on.
This is by design. Once you
have created a call list from
a group, then it is not
connected to the group
anymore. This means
editing the group's contents
afterwards doesn't have any
effect on the call list.
When you click the button to
get the next call, it orders
the records like this:
ORDER BY LCall_CallAfter,
LCall_Attempts,
LCall_AssignedToUser,
Pers_LastName,
Pers_FirstName.
This is hard coded. An
enhancement request must
be raised to change the
order.
0-144946-QA Cases When an SSA field was
added to an entity page,
hyperlinks pointing to a
different entity were broken.

Management
On an install with a custom
component used to record
customizations, it was not
possible to use the
Interactive Dashboard.
People
On the New Appointment
screen, it was not possible
to use the Advanced
Search Select button (green
arrow), next to the
cmli_comm_personid field.
0-157303-QA Core Product The entitywizard dll for SDK
was missing from the 7.2
install files.
0-152332-QA CTI Using CTI, if you're entering
details for a Company task
in the CTI frame and hang
up, the mouse cursor
moves away from the
Details field, and you have
to click it again to keep
entering information.
This can't be fixed.
0-151350-QA Customization The fields added to a
custom entity screen
overlapped.
reproduced.
0-153387-QA Customization If a user logged into Sage
CRM externally, the
sessions of all active users
on the Interactive
Dashboard were dropped.
reproduced.
0-154874-QA Customization It was not possible to scroll
custom ASP pages with
embedded URLs on iPad
devices.
0-156120-QA Customization After creating a test table
and adding some fields and
captions, a user had an
issue with Advanced
Search Select fields in Sage
CRM.
This issue is fixed. This was
solved by changing the
user's configuration. You
can find out more below.
0-156817-QA Customization A user was unable to do a
search on Company after
adding a custom Multi-
Selection field to the
Company screen.
reproduced.
0-145167-QA Database A user was unable to
access the Dashboard tab
in My CRM because of
issues with Tomcat.
reproduced.

0-149982-QA Data Upload It was not possible to import
data if required fields were
blank, even though the
Field Security option was
deselected.
0-157325-QA Data Upload There was an issue with the
Person Email Fax Number
field when performing a
data upload.
0-154031-QA Comms/Diary On an install with an
Accounts integration, there
were some performance
differences between
accessing the
Communications tab for an
Account and accessing the
Communications tab for a
Company.
0-148951-QA Document Drop After setting file extension
restrictions, for example,
.jpg files, in Administration |
Email and Documents |
Documents & Reports
Configuration, it is still
possible to import this type
of file as an email
attachment to Sage CRM.
The feature works as
expected for Document
Drop.
This is by design. An
enhancement request must
be raised to make this
feature apply to filing emails.
0-154986-QA E-mail Manager There was an issue with a
.js file when working with an
email template containing
an inline image.
reproduced.
(SageCRM)
It was not possible to
perform an email blast in
Swiftpage because of an
issue with addresses in
dynamic groups.
This issue is fixed
(SageCRM)
Using Swiftpage, it was not
possible to perform an
email blast for a list of
1000+ contacts.
(SageCRM)
Following an upgrade, a
user was unable to use the
Marketing function
"Response Setup".
Integration
A customer had issues with
automatic Exchange-CRM
meeting updates.

Integration
External attendees received
meeting updates
notifications when the
Regarding area of a
meeting was updated, even
when the "Include CRM info
in body" option was set to
No.
Integration
A user was unable to sync
some contacts to MS
Outlook.
Integration
It was not possible to use a
secondary SMTP address
for Exchange
impersonation.
0-155133-QA Facebook The Facebook tab on
Company records was not
displayed correctly on 7.2b.
0-157886-QA Facebook A user was unable to
access Facebook profiles
on Company screens.
Find
Searching for All on a
custom multi-select field
returned no results in 7.2c.
Security
Fields created by users
were set to Required by
default.

0-147557-QA Install / Upgrade A user wanted to use
different System
Administrator login details
to perform a Sage CRM
upgrade, instead of the
standard login details.
This is by design. The Sage
CRM installer uses the
same username and
password that is in the
registry for Sage CRM.
Workarounds are:
1. Temporarily grant the
Sage CRM user more
privileges and revoke them
after upgrade is complete.
2. Change the username
and password in the
registry:
Go into
HKLMSOFTWAREWow64
32eWareConfig/%instance
name% and change the
DatabaseUserID and
DatabasePassword fields to
be the username and
password of the account you
want to use. If you keep the
old values, you can restore
them into the registry after
the upgrade.
Note: After changing the
registry, please do an
IISRESET to apply your
changes.
0-157018-QA Soap Integration On an install with a Sage
200 integration, a user was
unable to delete an order or
quote in Sage CRM, if the
record had been edited too
many times.
200 integration, duplicate
people and addresses can
be created, if you delete a
Person record in CRM, then
add a new Person to the
Company using the same
name and address.
This is by design. This is
due to the way Sage 200
works. This is related to 0-
157785-QA.
200 integration, if a user
deletes an address and
syncs, the address is added
back to Sage CRM.
due to the way Sage 200
works. This is related to 0-
157759-QA.
(Interactive)
A user was unable to create
a new gadget on the
Interactive Dashboard.

0-158453-QA Library and
Templates
When creating a new Merge
document, if the Subject
field was left blank, then
was filled in following the
validation error message, it
was not possible to open
the Merge document.
0-156406-QA Licensing A business partner was
unable to manually register
a customer.
due to the server, not the
Sage CRM product.
0-154400-QA Mail Merge There was an issue with
Mail Merge rendering for a
long Word document (15
pages).
0-157507-QA Mail Merge A user was unable to
perform a Mail Merge from
a Group context.
0-151059-QA Mobile It was not possible to edit
the iPhone Company grid
from IE. Doing so prevented
users from accessing the
Company entity on iPhone.
reproduced.
0-157920-QA Mobile Tapping the Dashboard
button on iPhone brings you
back to the homepage.
This is by design. You can
access the mobile
Dashboard only if you have
configured from your
desktop it first.
0-157742-QA Opportunities It was not possible to filter
the Opportunity pipeline to
All.
0-158313-QA Opportunities A user had a query about
the Opportunity Tracking
tab behavior.
This is by design.
The Duration field on the
Tracking tab displays how
much time a record spends
in each state. Whenever you
make a change to a record,
this creates a new tracking
record. The last tracking
record always displays the
duration from the moment
the tracking record was
created to the current date.
0-151693-QA Outlook Integ It was not possible to file
emails from Outlook after
removing the Regarding
field from the
CommWebPicker screen on
the Comm_Link entity.

0-151849-QA Outlook Integ A user could not use the
Outlook plug-in with Outlook
2010. The user was given
full admin rights to install
the plug-in, then these
rights were removed. As a
result, the plug-in was
checking for a different key
value in the registry.
due to the user's Windows
environment configuration.
Exchange
amend the Details field
(comm_note) on the
Communications entity.
0-146882-QA Reports When a user created a
report and selected the
"Week previous" criterion,
the report did not take into
account User Preferences
settings (My Week Starts
on).
0-151732-QA Reports When a user unselected the
"Opt out of E-marketing
communications" checkbox
on a Company summary
screen, the value of the
comp_optout field changed
to "N" instead of Null.
0-154018-QA Reports A user was unable to add
oppo_stage and
oppo_reason as Group By
and Sort On criteria for
reports.
0-157747-QA GCRM
Integration
An integration with Murano
failed following a Murano
update.
0-158134-QA GCRM
Integration
There was an issue with the
Date Time format of synced
entities.
0-157118-QA Groups / Target
Lists
The contents of groups
were not sorted using the
field orders specified in
Groups Settings on Sage
CRM 7.2b installs with an
SDATA integration.
0-158113-QA Security
Management
A user with no forecast
rights was able to see
forecasting figures
displayed on the
Opportunity pipeline.
0-154636-QA Twitter A user was unable to
access the Twitter tab in My
CRM and from Company
records.

0-156195-QA User Interface On an install with a Sage
300 integration, the vertical
scroll bar disappeared when
clicking New Quote or New
Order.
0-155134-QA Yammer A user was unable to work
with the Twitter and
Yammer add-ons on 7.2a1
or 7.2b.
March iPhone app updates
The following cases were fixed for the Sage CRM iPhone app. Watch out for this upcoming
update which will be announced on the Sage CRM Community.
Edit April 2014: 0 -158212-QA was removed from the Patch Release Notes.
Ref ID Description Status
0-154520-QA A user was unable to synchronize the
Calendar to the app.
0-154453-QA In the app settings, selecting "My
Assigned Contacts" or "My Team
Contacts" only synced the first 200
contacts no matter how many contacts
you actually have.
0-156794-QA A user was unable to update data in
the app and received the following
error: "Download error, unsupported
URL".
0-157270-QA When adding a phone contact to
CRM, the address and mobile number
fields weren't populated.
0-157272-QA Deleting notes, tasks, appointments or
opportunity records in Sage CRM did
not delete them from the iPhone app.
0-157273-QA Users with no admin rights were
unable to Update Data in the app.
0-158372-QA The app did not support iOS 7.1 This issue is fixed.

Additional notes on this patch (D)
More information around 0-156120-QA
This issue was solved easily by changing the user configuration.
An Advanced Search Select is always created as an integer field. This means that the field
can't look up a category table that has a character code value for example. To work around
this issue, create the Advanced Search Select field manually, give it a text type, and then
add it to the necessary screen
1. Create a text field for your category lookup. This ensures that the database type of
the field matches the codes you enter in the field.
2. Change the entry type of the field to Avanced Search Select. You can do this in the
database by typing:
update Custom_Edits set ColP_EntryType = 56, ColP_LookupFamily
= 'ICCATG' where ColP_ColName = 'case_categorytext'
where your new field is called case_categorytext for example.
3. Refresh the metadata.
4. Add the field to your Case screen.
Working with the Exchange Outlook plug-in with IE 11 installed on your
machine
An EDOMParseError can occur if you're working with Internet Explorer 11 and try to file an
email in Outlook.
The workaround is to:
1. Add the Sage CRM URL to the list of trusted sites in IE. You can find the correct
procedure on the Microsoft website here.
2. Add the Sage CRM URL to the Tools | Compatibility View Settings tab. You can
find the correct procedure on the Microsoft website here.
3. Add the Sage CRM URL to your Favorites. When you delete your browsing history
from Tools | Internet Options | Delete in the General tab, please make sure that
the Preserve Favourites website data option is selected.

Patch C
Released December 2013
Outlook plugin
Document plugin
CTI plugin
7.2.0.4
7.2.0.3
7.2.0.2
7.2.0.2
Patch C Issues List
0-148774-QA 3rd Party
Software
A customisation using
MessageBlock to send an
email, was not populating the
CC field correctly.
reproduced.
People
When adding a new company
and linking it to an ERP
system, the content area of
the Company page was not
shown when the link was
made.
reproduced.
People
An error message, "List index
out of bounds" was displayed
after deleting a person.
reproduced.
People
A SQL error was displayed
when accessing the
Company Quick Look tab
after customising the case
list.
reproduced.
0-155263-QA Configuration Removing a check box entry
on an escalation rule did not
disable the rule as expected.
0-155267-QA Configuration Time zone settings for
Central Time (US and
Canada) were out by one
hour.
The documentation has
been updated with the
following note: “If the
Time option is checked in
on the server machine,
then it will affect all users,
even if they have not
selected this option
themselves in their time
zone settings”.
0-149991-QA Core Product There was a typo in a
document library error

message.
0-151956-QA Core Product It was possible to create a
duplicate user name when
one of the users was set to
disabled.
0-153456-QA Core Product Screen contents were not
displaying correctly after
resizing the browser in an
integrated Sage CRM
system.
reproduced.
0-154760-QA Core Product An error message was
displayed when using the
"Add File" feature in Chrome.
reproduced.
0-155269-QA Core Product On-screen notifications were
not displaying when the field,
"Escalation tuned for", was
set to "System Performance".
0-141756-QA CTI An error occurred when using
group pick-up to take an
incoming call using CTI.
reproduced.
0-155416-QA CTI It was not possible to use the
CTI plug-in due a
permissions issue.
0-151984-QA Customization Company and person default
values were not populated on
a custom tab.
reproduced.
0-153481-QA Customization A user was logged out of
Sage CRM when selecting a
link to a list from a custom
entity.
reproduced.
0-154648-QA Customization A url set up in Custom
Content was not displaying
correctly.
0-154971-QA Customization A customised Date Only field
was being deleted rather than
hidden.
0-155777-QA Customization It was not possible to clear a
case field which had been
added to the case filter box.
0-151485-QA Database A stored procedure used
during upgrade to 7.2
required improvement.
0-155122-QA Database System log files were larger
than expected.

0-149610-QA Comms/Diary In a localised French system,
a communication was linked
to a case and saved. When
the link was revisited and
selected, an opportunity
rather than the linked case
was displayed.
reproduced.
0-152434-QA Comms/Diary A communication record for
an external attendee on an
appointment was not visible
from the Quick Look tab.
0-152849-QA Comms/Diary A customised user select
field was not displaying
correctly on an iPad.
reproduced.
0-153510-QA Comms/Diary When creating a follow-up
communication from the
context of a lead, which was
selected from the recent list,
the related company and
person details were not
populated on the
communication screen.
reproduced.
(SageCRM)
A SQL error occurred when
selecting "Click here to view
the recipients of the E-
Marketing E-mail".
Integration
Appointments were not
synching from CRM to
Exchange.
reproduced.
Find
The search results from a
person search where the e-
mail restriction field was
checked, were still showing a
list of all people - not just
people with the e-mail
restriction flag set.
reproduced.
Find
The advanced search select
field on a custom entity was
being incorrectly populated
rather than left blank.
0-155937-QA Install / Upgrade Selected report columns
changed when using the
Previous button in the report
builder.
0-156133-QA Soap Integration Account contact details were
incorrectly updated after
changing a custom system
parameter setting.
0-155812-QA JavaScript API It was possible to activate a
script from the company
name field.

0-151771-QA Leads A lead could not be
converted to an opportunity
because the Opportunity
Person Name field was blank
and not auto-populating.
This is by design. The user
must click "Add or find
person" before converting
the lead to an opportunity.
0-155853-QA Mail Merge "docm" and "dotm" files were
not showing in the document
library.
This issue is closed.
"docm" files work in 7.2c.
"dotm" files are not
supported.
0-155075-QA Mobile An e-mail template was not
showing as a merged e-mail
when viewed from an iPad.
This issue is closed. The
Sage CRM e-mail client is
not fully supported on the
iPad.
0-156570-QA Multi Server It was not possible to log into
Sage CRM in a multi-server
environment with a
configuration of: server 1 –
server 2 with Load Balancing
enabled
0-150979-QA Navigation The user was not returned to
the company context after
using the communication
follow-up check box.
0-138164-QA Notification Case notifications were not
correctly triggered by
workflow.
This issue is could not be
reproduced.
0-147029-QA Opportunities Accessing quotes related to
an opportunity, from the
context of a custom tab, lost
the link to the opportunity.
reproduced.
Exchange
An e-mail communication
record was not displaying in
the company context.
reproduced.
0-155544-QA Quotes / Orders It was not possible to clear
the company and person
details from the Find Order
screen.
0-152621-QA Related Entities A French translation was
missing when adding a new
custom tab using the
"relatedcompanieslist" action.
reproduced.
0-142511-QA Reports Incorrect communications
were shown in report output
on a German Windows 2008
install.
0-151467-QA Reports Arabic data was not
displaying correctly in
reports.
reproduced.
0-152209-QA Reports There was an error in report
output when "Show original

currency values" was
selected.
0-154421-QA Reports Incorrect integer and date
field format displayed in an
opportunity report.
reproduced.
0-153950-QA GCRM
Integration
Synchronisation failed with
an error on the Credit Limit
field in an OfficeLine
integrated system.
reproduced.
(Swiftpage)
When carrying out an E-
Marketing e-mail blast, the e-
mail was taking duplicate
records into account and
therefore exceeding the daily
E-Marketing e-mail
allowance.
(Swiftpage)
E-Marketing statistics were
not synchronising with Sage
CRM as expected.
This is fixed.
Lists
A SQL error was displayed
when editing a group based
on opportunities.
reproduced.
Lists
The Exclude All option was
not working correctly when
creating a new group within
E-Marketing.
Lists
An error was generated when
creating a new group from
the Find screen.
Lists
No data was returned when
creating a group of leads
where the last name field was
left blank - even though this
field had been customised so
that it was not required.
(English prod)
Translations were not
displayed correctly when < or
> was used in the translation
of a caption code.
reproduced.
0-146620-QA Web Services MS Visual Studio could not
connect to the CRM web
service WSDL.
reproduced.
0-156073-QA Web Services An error occurred when trying
to insert an AR customer
from Sage 300 into Sage
CRM.
0-151701-QA Workflow The initiation of an escalation
rule was resetting the
duration time in the tracking
tab. In addition, a custom
The first issue is by design.
The second issue could
not be reproduced.

check box field was not being
updated.
0-152221-QA Workflow A customised case field
showing addresses was not
restricting the addresses to
the current context when
used within workflow.
Instead, a list of all addresses
was displayed.
reproduced.
0-154330-QA Workflow A custom label, which was
part of an Execute SQL
workflow action, was
incorrectly displayed on the
case screen.
This is by design. Please
set the "Show confirmation
message" to "No" on the
workflow action.

Patch B
Released October 2013
Outlook plugin
Document plugin
CTI plugin
7.2.0.3
7.2.0.3
7.2.0.2
7.2.0.2
Before installing
Many changes have been implemented with this release. Before installing this patch, please
be aware of the following:
Edit and save your existing Notifications
Changes have been made to improve notifications. However, you will need to edit and save
all of your existing on-screen notifications to apply this fix.
As a reminder, System Administrators can create and edit on-screen notifications for their
users in Administration | Customization |Entity | Notifications.
See 0-144545-QA in the Issues List for more information.
Check your customizations
This patch release introduces changes to way ASP pages are rendered in Sage CRM.
These changes mean that customizations not using the GetPage() method will break when
Sage CRM 7.2b is installed.
What has changed?
In Sage CRM 7.2, we introduced the removal of framesets in order to improve the Sage
CRM User Interface. Sage CRM 7.2b further improves the User Interface by ensuring that
the top content and left-hand menu of CRM (the “L”) is always rendering correctly.
Previously ASP pages used to be rendered within a frame and only needed to render the
horizontal tabs (if any) and the page content itself.
Now, ASP pages are rendered within the main browser window and so they need to render
the entire page, "L" included.
To do so, Sage CRM 7.2b now only uses the API method called CRM.GetPage to render
pages.

Sage CRM 7.2b now only uses the API method called CRM.GetPage to render pages.
This change means that all pages and customizations must use the CRM.GetPage method
in order to work with Sage CRM 7.2b.
The following issues may be encountered for pages not using this method:
The “L” is
missing
In this case the CRM.GetPage method is probably not getting called. It is
likely that your asp page is generating HTML and sending it directly to the
browser using Response.Write calls. These calls need to be changed
to CRM.AddContent calls instead, this will add the HTML strings to a buffer
which can be written to the response stream
with Response.Write(CRM.GetPage());.
The CRM.GetPage method will output the entire HTML document, including
all the HTML necessary to render the L and the top tabs. There should be
nothing written to the stream before or after it. There should only be
one Response.Write call.
You can read more about the GetPage and AddContent methods in the online
developer help.
Too many
“L” in the
page
You may see the "L" appear in pop-up windows and within iframes where you
previously did not see it. In these cases you will need to change your
GetPage calls to GetPageNoFrameset calls instead.
GetPageNoFrameset is a new method, its usage and function is exactly the
same as GetPage except it does not render the "L".

Patch B Support
With the release of Sage CRM 7.2b, we have added support for:
- Microsoft Office 2013
- Microsoft Exchange Server 2013
- Microsoft Server 2010 SP3
For more details about what is supported with your version of Sage CRM, please take a look
at the Software Support Matrix, which is regularly updated with the latest updates:
• https://community.sagecrm.com/user_community/m/72_documentation/25765.aspx
Patch B Issues List
0-142297-QA .Net When creating a .Net page
with a Date and Time field, it
was not possible to save the
Time value of the field.
0-148393-QA .Net It is not possible to customize
the Person Entity, so that the
Person Summary screen can
point to another screen
instead, e.g. the Related
Entities screen.
This is by design.
0-152288-QA Registration
Form
Where Sage CRM has
already been registered,
Customer intermittently gets:
"You are using an
unregistered version of CRM.
Please register your CRM
software"
reproduced.
0-144966-QA Address Linking There was an issue with the
cross-side scripting feature
when using IIS auto login
with a user already logged in
CRM at the time.
0-146665-QA Call Handling A user was not able to use
the Quick View Tab in
Communication records.
This issue is fixed. When
selecting Quick Look to
view a communication, you
only have the option to
select "Close" from now
on.

0-153044-QA Call Handling Outbound Call 'Call back
after' Screen 'Save' button &
'Call Back After' date/time
control not working.
Management
Opportunities were not
grouping as expected in the
Reports tab of a campaign.
Management
It was not possible to set
“Export to File available on
Search/Group” and “Send
Email available on
Search/Group” as
Administrator functions only.
0-146495-QA Cases It was not possible to change
the date format to
TT.MM.JJJJ instead of
TT/MM/JJJJ.
reproduced.
0-147493-QA Cases Custom Entity field not auto-
populated when in the
context of a new case.
0-149290-QA Cases When viewing a Case,
choosing 'continue' and
creating a New Case,
Company/Person details are
auto populated.
Management
Component manager scripts
were not JavaScript
compliant.
Management
It was not possible for a user
to use the Component
Manager.
Management
SQL Error in My
CRM|Calendar tab after
running Component Manager
script.
Management
Issue when creating a new
component, and adding new
phone or email type fields
which were being incorrectly
scripted out as Addcolumn.
People
The "Set as default person
for Company" option was
missing from the new Person
screen when the Person was
created via a New
Communication Task.
People
For some users, it took more
than 30 seconds to delete a
company.

People
It was not possible to work
with Email addresses starting
with a quote in CRM.
People
On some SData integrated
installs, a long mobile
international area code may
cause a SQL exception error.
an issue with the
integration schema from
the non CRM side. The
mobile phone number side
adds field but doesn't add
the required custom edit
for the field. In the schema
a custom edit needs to be
added for the addition of
this field size restriction on
the front end of CRM.
0-144140-QA Core Product It was not possible to use the
INCLUDE/EXCLUDE
functions on an asp page in a
vanilla install.
0-145721-QA Core Product After editing the Lead
workflow to set a field as non-
mandatory, this field would
still be mandatory when
trying to edit existing leads.
This is by design. When
you set a field to be
required or not on the new
Lead workflow rule, this will
only apply when you are
creating a new lead, it will
have no effect on editing a
lead - if you want to make
the field required for editing
then go to Administration|
Customisation | Leads and
set the field to be required
there.
0-153379-QA Core Product Custom ASP pages were
scrolling vertically (up/down)
but not horizontally (left/right)
on the iPad.
0-153457-QA Core Product When loading a Custom
Entity record using your
Recent List, custom asp page
multiline text fields appear
without scrollbars.
0-139265-QA CTI When working with CTI, the
user could not transfer an
incoming call internally with
the Consult button.
0-140941-QA Customization There was an issue with the
size of the Calendar window
for Dutch Sage CRM.
0-144088-QA Customization It was not possible for a user
to add a custom Chart tab on
Company.
reproduced.

0-144675-QA Customization An error message was not
correctly translated into
French.
0-145501-QA Customization Advanced Search Select did
not work correctly on a
customer's custom asp page.
0-145714-QA Customization It was possible to leave a
required field blank, even if it
was part of a workflow.
0-146682-QA Customization A user had created a Search
Select Advanced field with
the restrictor field set to
another Search Select
Advanced field. However, it
seemed to ignore the
restrictor field and not bring in
the proper results.
0-147393-QA Customization In CRM, a user was able to
create a selection Code of
more than 40 characters in
length without getting an
error message.
reproduced.
0-148731-QA Customization When creating a custom field
in CRM, it was not possible
for a user to specify an Alias
Name containing the letter ß.
This cannot be fixed. The
user query is used directly
against DB. SQL standard
doesn't support special
characters like Eszett (ß).
Workaround is to use "ss"
in SQL names and use "ß"
in Captions.
0-148878-QA Customization An "unexpected event has
occurred" error occurred
when clicking on an Address.
reproduced.
0-149817-QA Customization Required fields not working
on new, custom Company
Entry screen using
EntryGroupBlock.
reproduced, in the latest
version of CRM, 7.2b.

0-150162-QA Customization Under the Admin area,
creating a new view has a
character limit. This happens
in non-IE browsers only.
Administration area is only
supported in Internet
Explorer browsers.
0-150686-QA Customization There was an issue with
INSERT statement not
adding commas before and
after the field value.
0-151978-QA Customization The Inline Screen Editor did
not display fields from other
entities.
This issue is fixed, via a
workaround. Run this SQL
so the filterbox knows it is
based on a view - then the
inline customisation should
show all the fields from the
view. You will need to
refresh metadata in
Administration after
running this.
Update
custom_screenobjects set
cobj_useentity =
'vListCommunication'
where CObj_Name =
'communicationfilterbox'
0-152564-QA Customization .Net SDK issue resolved -
Error: The Method
”OverrideContent” in the
.NET SDK in CRM 7.2 is not
working properly
0-153682-QA Customization When saving a
communication created via
an asp page, a user would
get an error message on
screen “User or Team must
be selected”.

0-153683-QA Customization When you navigate back to a
custom asp page from a
popup window in 7.2 (e.g.
enable inline customisation
and click on the customise
button for a screen on a
custom entity and click save)
you get a “cascading CRM”
effect.
0-153920-QA Customization 'Object doesn't support
property or method' error
when customised Find menu
option used a customurl
action.
0-147726-QA Customization
Wizard
The paperclip icon did not
display anymore after adding
a new column to the
Documents List.
This issue is fixed by using
the workaround described
here:
https://community.sagecrm
.com/user_community/f/84/
p/8093/22169.aspx#22169
The documentation will be
updated to describe this
procedure at the next full
release.
0-141522-QA Dashboard When alternately opening a
report and a chart on the
Classic Dashboard, the chart
would start displaying the
report's information instead.
An SQL error message would
appear in some cases.

0-148636-QA Dashboard Changing the CRM database
made Tomcat lose the
Internet connection.
This issue cannot be fixed.
If you are using an SQL
instance, it is
recommended to update
the line jdbc.url with this
information formatted this
way:
db.url=jdbc:log4jdbc:jtds:sq
lserver://<Server
Name>:<Tomcat
Port>/<CRM Install
Name>;instance=<SQL
Server Instance Name>;
You can also check this
name from ..:Program
Files
(x86)SageCRM<CRM
Install
Name>tomcatwebapps<
CRM Install Name>jWEB-
INF
0-144379-QA Data Upload After adding a custom
currency field in Lead, a user
would receive a "Currency
not set" error when doing a
Lead Upload.
0-144859-QA Data Upload An unnecessary amount of
connections were created
when carrying out a Data
Upload on an Oracle
database.
0-145404-QA Data Upload When carrying out a Lead
data upload, the lead_source
field did not get inserted into
the database.
0-146402-QA Data Upload Umlaut characters did not
display correctly in CRM
7.1SP2.
reproduced.

0-146738-QA Data Upload When carrying out a
Company Data Upload, if
People from the same
Company lived in different
cities, then, only one city
would be taken into account
and data would be
overwritten.
0-147885-QA Data Upload When performing a Data
Upload, the Address field
would be blank if the .csv file
contained multiple address
fields (e.g. Home and
Business), and only one of
them was filled in.
0-149433-QA Comms/Diary New Emails did not get filed
in the Communications tab
when in a Company context.
0-150980-QA Comms/Diary All communications for
Central time zone users were
1 hour off.
This is due to the Daylight
Saving time Option.
The Sage CRM System
Administrator guide will be
updated with this content:
"Note: If the Automatic
Daylight Saving Time
option is checked in on the
server machine, then it will
affect all users, even if they
have not selected this
time zone settings."

0-153664-QA Comms/Diary Communications created
from a Group could not be
modified. Also there was a
loss of entity context when
you click on attachment tab.
This is by design.
When you view a group
communication from the
context of a person it is not
possible to change the
main communication
details, you can only
change the bits that are
specific to that one person.
So you have to edit from
your calendar or from Find
communication to be able
to change the status.
Additional issue regarding
Company context lost
when switching to
Attachment tab is fixed in
Sage CRM 7.2.b
0-146166-QA Document Drop It was possible for users with
an Info Manager profile to
edit and delete shared
documents.
This issue is fixed. A user
with an Info Manager
profile, but with no Info
Admin rights, will not be
able to see or use the
Delete button.
0-148624-QA Document Drop After creating a lead named
"." into an opportunity, it was
not possible to attach a
document to this opportunity.
This issue is fixed. It is not
possible to use "." as a
name.
0-148770-QA Document Drop For some users, the
document paperclip
attachment icon was missing
from the Document screen.
0-141605-QA Email Client When using the Email
Manager to monitor an
account and create
communications from
inbound Emails, it is not
possible to view Email
attachments and encrypted
Emails.
The internal Delphi engine
Indy10 have a bug that
does not handle "Content-
Transfer-Encoding:
quoted-printable" too well.
This case is similar to 0-
145919-QA.

0-142767-QA Email Client It was not possible to display
the
#comp_phonefullnumber#
field of an Email template.
reproduced.
0-143750-QA Email Client After forwarding an Email
filed against a Person in a
CRM install using an SMTP
sever, the Email was sent but
no communication was
created in CRM.
reproduced.
0-143961-QA Email Client It was not possible to use
#xxxx# fields in the To and
Cc sections of Emails for
workflows and escalation
rules.
reproduced. Also, please
note, that when sending an
Email from the Main Menu,
New Email button, it is not
possible to use #xxxx#
fields either.
0-145452-QA Email Client After creating a default Email
template with Subject "Test"
for example, this subject
would overwrite the actual
subjects of existing Emails
and Communications.
0-145903-QA Email Client In CRM, if an Email template
is selected when forwarding a
message, then the template
will delete the body of
forwarded message.
This is by design.
0-146338-QA Email Client When a user was sending an
Email to a Person in CRM,
the communication link would
be displayed on the Person's
Communication tab, but not
on the user's.

0-148500-QA Email Client Pasting MS Word paragraphs
in CRM to create an Email
template produces
unnecessary paragraph tags
in the HTML code.
This cannot be fixed. It is a
limitation of the FCK editor.
0-148614-QA Email Client When replying to an Email in
CRM, the CC Email
addresses would move to the
TO field.
0-151061-QA Email Client Email not sent from
Escalation rule using Send
Email workflow action, where
#user_emailaddress# is
used.
(SwiftPage)
generate a Swiftpage Email
blast for a group that has Key
attribute data.
reproduced. KA fields are
not supported in
SwiftPage.
(SwiftPage)
If an e-Marketing user, e.g.
Admin whose home territory
is Worldwide, sends an e-
Marketing communication to
People whose home territory
is UK, then other UK users
cannot see this
communication within CRM
because the territory against
the communication defaults
to Worldwide.
This is by design. A User is
not allowed to see a
communication unless they
have rights to the territory
that the communication is
assigned to.
One workaround for this is
to create a new channel
that these communications
can be assigned to. Give
all users view rights to that
channel in territory admin.
Then, assign all email
communications to that
channel.
Integration
When filing an Email against
multiple people in CRM,
some blank communication
records would be created as
well.
reproduced.

Integration
After syncing two Outlook
tasks to CRM, then editing
one of them in CRM and
syncing the change back to
Exchange, the updated task
appears in a separate day for
the Task List View.
This is due to Outlook's
behaviour. If a task is
updated from Sage CRM,
then Exchange will change
its "Follow Up" flag.
Integration
It was not possible to file
external Emails to CRM from
the Inbox.
reproduced.
Integration
For a user, all Tasks and
Appointments created in
Sage CRM had an incorrect
start date in Outlook (or the
web login) after syncing with
Exchange Server (Office
365).
This issue is fixed. It is
originally a Microsoft issue.
Integration
It is not possible to set up an
Exchange impersonated user
for an Exchange integration.
The integration will not work.
This is by design, because
of the way Exchange is
configured.
0-146417-QA Export Data The Export to File option was
not available on a custom
Entity screen.
reproduced. Please note
that the Export to File
option is only available to
custom entities which have
communications records.
0-147615-QA Export Data It was not possible to
correctly export a currency to
Excel.
reproduced.
0-145187-QA Field Deletion The Dedupe process deleted
some of the information
contained in multi-select
fields on the Company
screen.
0-139244-QA Email Manager It was not possible to see
inline images within Emails
filed by the Email manager.

0-143307-QA Email Manager When filing an Email with an
inline picture and two
attachments, then only the
inline picture was filed as an
attachment, and the other
attachments were lost.
0-145919-QA Email Manager The Email Manager on POP
does not handle UTF Email
addresses. When sending an
Email, only the sender's
name is kept, and their Email
address is truncated.
The main reason is that
Delphi 2006 doesn't
support newer versions of
RFC. It supports only RFC
2047.
0-147576-QA Email Manager When using the Email
Manager to handle customer
cases, and sending an
outbound Email in the
Communications tab, only the
body of the Email was blank
and did not contain the
history of past Emails related
to the conversation.
0-147943-QA Email Manager It was not possible to display
inline images when reading
an Email from the Email
Manager.
Find
When doing a Search, the
case_status field would revert
back to its default value.
Find
It was not possible to search
for results containing square
brackets.
Security
It was possible to leave a
checkbox empty, even if it
had been marked as
mandatory.

Security
It was possible to leave a
required field blank if no
changes were made, when
selecting Change then Save.
0-139285-QA Soap Integration In Sage 200, after creating an
account, then deleting one of
its contacts, it was not
possible to synch the account
to Sage CRM.
0-148072-QA Soap Integration When doing an integration,
and importing People to
CRM, these people would all
get the same companyid.
reproduced.
0-144823-QA Interactive
Dashboard
A customer had an issue
displaying Opportunity
reports in a Chart gadget on
the Team Dashboard.
This issue cannot be fixed
for a patch release. Re-
saving the reports resolves
the issue for a given report.
The underlying issue will
be resolved in the next full
release. The reason for the
delay is because applying
a SQL script in a patch
release will cause reports
to break for existing
customers.
Dashboard
to see the Gadget Templates
screen.
reproduced.
Dashboard
Creating a new dashboard
gadget with a new task
drilldown produced a 'page
cannot be displayed' error on
the Interactive
Dashboard.N.B. This
happens when default IIS
port is changed from default
port 80.
Dashboard
It was not possible to click on
a website address in the
Interactive Dashboard List
gadget. It produced a '404 -
File or directory not found'
error.

0-153105-QA JavaScript API A Custom Entity's Summary
page (Custom ASP page)
was displayed without left
menu and top content.
(Interactive)
It was not possible to filter the
columns of an SDATA gadget
by ascending or descending
order in the Interactive
Dashboard.
(Interactive)
On French installs, the tooltip
available for the Calendar
Gadget was in English.
(Interactive)
to load SData Dashboard
gadgets.
(Interactive)
When creating an
appointment in CRM, the
appointment would be one
hour off.
reproduced.
(Interactive)
In 7.1f, it was not possible to
open the Gadget Template
screen.
reproduced.
0-148292-QA Leads When adding a Send Email
action to the primary rule in
the standard Lead Workflow,
the Email notification was
only sent to the Leads
created in CRM. Leads
created via Web to Lead did
not receive an Email.
0-154326-QA Leads There were issues when
adding a new person from
the New Lead screen.
reproduced.
0-145055-QA Mail Merge It was not possible to give
several HTML mail templates
the same name.
This issue is fixed. File
names are appended by 1,
2, or 3, if a file name
already exists.

0-146612-QA Mail Merge It was not possible to use
Mail Merge with IIS autologin
turned on, when there was a
value in the user_password
field of the user in the Users
table of the database.
0-148612-QA Mail Merge When viewing a
communication under the
company communications
tab, the recipient’s name
(#pers_firstname#) isn't
displayed - this happens
when emails have been sent
to a Group.
0-149258-QA Mail Merge Ampersand appears twice in
Mail Merged document.
0-150279-QA Mail Merge "Page cannot be displayed"
error occurred when carrying
out a Mail Merge from a
Custom Entity, where the
'Create Communication'
checkbox was selected.
0-151980-QA Mail Merge Issues with Mail Merge of
documents using special
characters (+, &). The ‘view
document’ or ‘edit document
buttons were not available.
reproduced.
0-143994-QA Mobile A user had created a custom
Communication script which
did not work on iPhone
devices.
reproduced.
0-146041-QA Mobile There was an issue
displaying custom fields in
the company grid on iPhone
devices.
0-149760-QA Mobile It was not possible to change
the filter settings for certain
entities on iPhone or iPad
mobile version of CRM.

0-130400-QA Multi Server The Load Balancing
redirection was not functional
when using IIS autologin.
0-143591-QA Multi Server A user is not able to access
CRM using only FQDM.
This is by design.
0-145735-QA Multi Server There was an issue working
in a multi-server environment
exposed to the Internet using
HTTPS.
This is by design. This
case is similar to 0-
143591-QA.
(Classic)
Special characters were not
displayed correctly in a
Classic Dashboard Chart
gadget.
reproduced.
(Classic)
It was not possible to display
charts on the Classic
Dashboard on an Oracle
install.
(Classic)
There were some speed
issues with Fusion Charts on
the Classic Dashboard in
v6.2m.
0-144545-QA Notification Notifications against the
Quotes entity did not
populate the Escalations
table correctly.
However, please edit and
save your existing
notifications to apply this
fix.
0-145966-QA Notification After rebalancing territories,
e.g. creating a new territory,
notifications set with a
Worldwide territory would
stop working.
0-147308-QA Notification When creating an escalation
rules with two Email actions,
deleting the second Email
action would automatically
delete the first one as well.
0-147398-QA Notification It was not possible to edit and
save the details of an
appointment/task notification.

0-147400-QA Notification It was not possible to save
notifications outside of the
Company entity.
This issue is fixed. This
case is related to 0-
147398-QA.
0-148212-QA Notification When creating a meeting and
sending reminders, if 10
people were flagged in the
meeting, each person
received 10 Emails.
reproduced.
0-144077-QA Opportunities A user wanted the
quot_rollup field to be
included on the Opportunity
screen on a vanilla install.
scripts in the vanilla install
are there to be adjusted as
required on a customer
basis.
0-145200-QA Opportunities A custom Minutes field added
to the Opportunity screen
was not incrementing
correctly.
0-146529-QA Opportunities When adding a new Person
to CRM from the New
Opportunity screen, the
Person's address would be
pre-populated with an
incorrect address.
0-149790-QA Opportunities In an Opportunity context,
when selecting Add Related
Company, the About box
information was not filled in.
Classic
The entity select field was
missing from the top context
area when logged into Sage
CRM via Outlook.
reproduced.
Classic
A user was not able to file
Emails when using Terminal
Services.
This is by design. Both
Exchange Outlook plug-in
and the Classic Outlook
plug-in are not supported
when accessing CRM over
a terminal server.
Classic
It is not possible to
synchronize tasks concerning
a Search List or a group from
CRM to Outlook.
This is by design.
Communications that are
part of a target list or group
(e.g. created from a saved
search) cannot be synched
to and from Outlook.

0-144611-QA Outlook Integ When adding a Person as the
default contact for a
Company from Outlook, this
new Person did not inherit
the Company's address, and
it had to be entered manually.
Exchange
When using Outlook
Integration, after closing
Outlook, the user session
persisted.
Exchange
There was an issue when
filing an email using the
Outlook Plug-in, where the
Email content included the
"square" symbol.
605-153914-
QA
Outlook Integ -
Exchange
When filing an email, the
communication did not get
linked to the relevant
Opportunity in the
"Regarding" field.
0-149835-QA Quotes / Orders Where 'decimal point' user
preference is set to “,” and
'thousand separator' is blank,
an incorrect Line Item Quoted
Price was saved.
0-142611-QA Reports When using the Print Preview
option, it is not possible to
copy/paste the resulting PDF
document to Word.
This is by design.
0-143737-QA Reports When doing a print preview
of a report using Advanced
Search Select, the report
switched back to search
mode instead of Advanced
Search Select mode.
0-145147-QA Reports Charts were still displayed
with a Legend after setting
ShowLegend(false).
customer did not have
Adobe Flash installed on
the server.

0-145728-QA Reports It was not possible for
multiple users to do an
Export to File at the same
time.
0-146913-QA Reports It was not possible to export
reports for users with a space
in their user code e.g. John
Doe.
0-149081-QA Reports Report based on Company
Group with >4,000 contacts
not generating.
reproduced.
0-153129-QA Reports When running a report that
used Advanced Find, and
exporting it to XLSX, CSV, or
EXCEL CSV formats, a new
window opened with left hand
menu buttons but no data.
reproduced.
0-140909-QA SData Provider When retrieving a
Communications payload via
SData, the
comm_opportunityid and
comm_orderid do not hold
the IDs, but the references
instead.
This is by design. When
working with SSA fields,
please note that references
are returned, not IDs.
0-151324-QA GCRM
Accounts
Officeline GCRM integration
issue - acc_int_defaultoppoid
was not set anymore when
an opportunity was synched.
This issue is fixed. Account
entries now will have the
correct id set in the default
opportunity field.
0-146302-QA GCRM
Integration
After editing the default
address for a Company then
saving, the Default checkbox
got unchecked.
reproduced.
0-146692-QA GCRM
Integration
When creating a new
Company, the City field was
pre-populated with the city
name of the last created
company, instead of being
blank.
reproduced.

0-147844-QA GCRM
Integration
It was not possible to create
an SData integration if the
ERP URL used contained a
blank space.
0-148514-QA GCRM
Integration
Article with ampersand at end
of name causes pricing
service to fail.
0-151977-QA GCRM
Integration
Incorrect $schema/common
request during
synchronisation.
0-152125-QA GCRM
Integration
Schema change with new
user defined field incorrectly
overwrites
vSummaryAccount view.
0-153265-QA GCRM
Integration
When creating a Quote with a
Comment Line item added,
then selecting the Link to
ERP button, the synch would
fail.
0-153449-QA GCRM
Integration
In the context of an Account,
select left hand menu to
search for another. Company
Name Search field was pre-
populated, instead of being
blank.
0-153452-QA GCRM
Integration
An opportunity total sum was
not correctly calculated
based on rollup via
synchronisation.
This issue is fixed. In 7.2b,
quotes will be excluded
that have rollup marked as
null (or 'N') when
calculating the opportunity
total.
0-154039-QA GCRM Pricing
Service
When creating a new line
item, and choosing “Product
Family", a blank popup
appeared with no product
families listed.

0-151969-QA GCRM Quotes /
Orders
Order/Quote not fully
synchronised from CRM to
ERP, problem caused by
error
"SageRecordIsLockedExcept
ion: Record is locked by
user".
(Swiftpage)
In a Person Group, the “New
E-marketing Email" action is
selected.
Enter first letter of Wave and
press Enter - the Wave Name
does not appear in list, SQL
log shows error: "Ambiguous
column name 'Wave_Name'.
Lists
to export a group to .csv or
Excel.
maxAllowedContentLength
parameter should be set,
so that it is bigger or equal
to the transitive file size.
For example:
<security>
<requestFiltering>
<requestLimits
maxAllowedContentLength
="250000000" />
</requestFiltering>
</security>
Lists
A customer was not able to
use 'Export To File' and 'Start
Mail Merge' on a group
based on a custom entity.
reproduced.
Lists
Opening the Email editor
from the Groups screen, then
selecting "Cancel", brought
the user back to the Mass
Email Editor instead of the
Group screen.

Lists
Outbound Call, Refresh Call
Lists, not removing records
that do not meet the criteria
of the group.
Lists
Advanced Find not returning
results from Custom "Groups
View", SQL Error appears on
Find.
Lists
Tasks created on a Group of
Leads were not assigned to
the correct Lead, Company
or Person.
This issue is
fixed.Additional Note: If the
lead is matched against a
Company or Person,
Company/Person
information is displayed on
the communication list
when carrying out a
Find|Communication. If the
lead has a
Company/Person assigned
but NOT matched to the
Lead, the
Company/Person is not
displayed on the
communication list.
Lists
Edit a Static Group's
Advanced Find fields (by
adding more fields to the
Advanced Find) Save it. An
unrelated Group's Advanced
Find fields are also being
modified.
Management
CRM displayed a number of
fields as restricted on a
Company Screen in
Dashboard context.
Management
On a German install, after
changing the settings of a
security profile, the
Profilname column displayed
the Territory Profile ID
instead of the correct
translation.
reproduced.
(English prod)
A field in the User
Configuration area of
Administration was not
correctly translated into

French.
0-136581-QA User Interface After creating a new System
Menu button, a user got
logged out when selecting it.
0-149136-QA User Interface People List was not sorted
correctly when the list
contained more than 10
people (where the "Grid Size"
user preference is set to 10).
reproduced.
0-148261-QA User
Management
A CRM user with View/Insert
(not Edit) permissions had an
issue working with the
Financials tab of Sage 200,
and was not able to create
opportunities, merge
companies or sync data to
Sage 200.
.
0-147693-QA Web Services It was not possible to bring
back deleted records through
Web Services.
0-145164-QA Workflow If a user had a User Select in
a Set Column Value workflow
action, and had set the value
to be from another field by
using the ## format in the
value, then it retrieved the
translation instead of the
code for the field.
0-145529-QA Workflow On the Opportunity screen, it
was not possible to create a
linked Progress field.
reproduced.
0-147453-QA Workflow A Hidden task in workflow did
not save against a Custom
Entity's Communications tab.

0-148556-QA Workflow In workflows, it was not
possible to create a Send
Email action using a Qualify
Rule of '--Users Forecasting
- Reports To--' in the To field.
Rolled-up Fixes
Fixed cases for 7.1j are rolled up to this Release. Please refer to the 7.1 Patch Release Note
for the full list.
Patch B Known Issue
There is currently an issue on patch B for customers working with Oracle 11g R2. It is not
possible to use the Company Name field when searching for communications. Instead,
please use the Keyword Search field.

Patch A
Released June 2013
Outlook plugin
Document plugin
CTI plugin
7.2.0.2
7.2.0.2
7.2.0.2
7.2.0.1
Patch A Issues List
0-151276-QA Licensing Product registration URL
missing when registering the
product manually”
0-152241-QA Customization Issue when trying to edit the
translation of a field in the
Communications entity.
0-152495-QA Quotes/Order User was logged off when
trying to save or cancel line
items on quotes and orders.
This issue is fixed,
provided you set your User
Preferences to Split for
Line Items.
0-152086-QA Customization Multiple Activity records were
created by the Sage API
0-151697-QA Self Service Access Violation error when
trying to display the Self
Service Case List.
0-151721-QA Library and
Templates
In Cases, not possible to
open attached documents
due to the removal of the
"Libr_userid" field.
0-151446-QA Mail Merge Not possible for a user with
worldwide unrestricted
access to sensitive info to do
a MailMerge for a Person or
Company outside of their
own territory.
0-149663-QA Customization After adding custom buttons
to the New Person popup
screen, users were switched
to a record from another user
session while navigating this
popup screen because of a
SID mismatch.
0-149711-QA Mail Merge Issue with MailMerge using
workflow steps, where the
MailMerge did not copy the
right data.

0-150844-QA Notification Some users could only see
their tasks notifications one at
a time.
This issue is fixed. Some
queries can take time to be
processed. We
recommend setting the
Notification timeout
(sysparam:
NotifyTimeoutSeconds) to
10 seconds instead of 5.
0-152210-QA Quotes/Orders Not possible to add free
text/lines or comments.
case is a duplicate of 0-
151938-QA.
0-151938-QA Quotes/Orders Not possible to add free
text/lines or comments.
case is a duplicate of 0-
152210-QA.
0-147242-QA Core Product CRM crashed following a
security update made
available to 7.1 SP2 users.

Patch A
Released May 2013
Outlook plugin
Document plugin
CTI plugin
7.2.0.2
7.2.0.2
7.2.0.2
7.2.0.1
Patch A Issues List
0-151276-QA Licensing Product registration URL
missing when registering the
product manually”

Sage CRM 7.2 Patch Release Notes (Patch E June 2014)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (12)

Similar to Sage CRM 7.2 Patch Release Notes (Patch E June 2014)

Similar to Sage CRM 7.2 Patch Release Notes (Patch E June 2014) (20)

More from Sundae Solutions Co., Ltd.

More from Sundae Solutions Co., Ltd. (20)

Sage CRM 7.2 Patch Release Notes (Patch E June 2014)