• Users are receiving a global unique identifier (GUID) error message during Sage ACT! install.

• Users are now able to perform Sage ACT! schema update (database update) with User Account Control (UAC) turned on and without having to run as a local Windows administrator.

• When a user opens Sage ACT!, the system will check to make sure the Microsoft SQL Server® (ACT7) service is running. If it is not running, Sage ACT! will start it for the user. 

• Picture fields were causing a view error after updating database.

• Timeless activities that span for more than one day miss the last day when synced to Google.

• Database files synchronized from a remote database always overwriting database files in the Publisher database if both were modified, instead of last modified file winning.

• Synchronizing modifications of supplemental files causes exponential sync file growth, causing remote sync to slow and timeout.

• File sync performance issue with attachments between the remote/subscriber database and the main/publisher database.

• Sage ACT! no longer performs the file processing for access/ security on the sync from a remote/subscriber database to a main/publisher database as is done from main/publisher to remote/subscriber database. The remote/subscriber database sends everything up to the main/publisher database. Making this change indirectly improved sync performance on attachments from the remote/subscriber database to the main/publisher database.

• Syntax error occurring when a file has had permissions changed and the file having an apostrophe in the file name.

• Error displayed after changing database location on server and remote/subscriber, and manage connection information on remote/subscriber database sync.

• Assigning a different drop down list to a field does not sync to remote databases.

• In previous versions, updates on the parent database do not get synchronized to remote if both sides modify the same contact. Original data on the remote replaces the changes on the parent.

• The changes made in the document attached to a contact in the remote database are not synchronized to the document in the main database. After editing and syncing to parent, a GUID number is added to the file and updated properly in the remote database. In the main database, the document is still linked to the original file name. On remote, the document is linked to the edited attachment. 

• Outlook contacts are removed from the remote database after syncing to main database.

• Unable to change settings when creating multiple remote databases.

• Contact and Calendar sync were failing with the following combination of conditions: User Account Control enabled in Windows, Outlook sync is run from the Sage ACT! menu or sync is run from the Sage Integration menu, and both Outlook and Sage Integration are run by a Windows non-administrative user. In a failure occurs under other user permission scenarios, the proper messaging guiding users on how to resolve the issue is displayed.

• Outlook add-in for Sage ACT! displays a runtime error during loading when upgrading from Sage ACT! 2011 SP1.

• Performance degradation when loading task list after sending an email via Outlook. Specific to Windows 7® and Office 2007 environments.

• In Terminal Services environment, Act.Outlook.Sync.exe errors display when logging in with multiple users. Multiple users can now log on to the same machine and sync Sage ACT! and Outlook simultaneously. 

• When attempting to send an email to two separate distribution lists in the same email message, the email will not attach to contact history.

•  When creating a new Company record, unable to proceed without saving the Company name.

• Salutation field is deleted when users have set a preference to not auto-fill the Salutation field.

• Error while editing data in Company list view while in customize columns mode.

• In the Company detail view, if a user creates a company with Divisions and then expands the tree view in the left navigation to show divisions, then switches the layout of the detail view to another layout, the expansion in the left navigation collapses.

• Company name is right-justified in the company name field after performing a lookup.

• If a contact with multiple name parts is not mapped in the multiple contact name dialog, nothing is imported into the database.

• Contacts linked to Opportunities are not exported when exporting from one database to another database.

• Import from Microsoft Excel® showing incorrect date format.

• When admin preference to attach emails to history when sent by database users is unchecked,  emails sent to other users are incorrectly to the attachment supplemental files folder.

• No response after clicking "Go to Advanced Query" link in the Lookup Opportunities view.

• Record Manager field listed incorrectly listed as "Manager" when doing lookups.

• Unable to delete users in empty copy of database after applying Sage ACT! 2011 SP1 has now been resolved.

• Unable to change default duplicate checking criteria in empty copy of database after applying Sage ACT! 2011 SP1.

• Teams created in original database are not listed in empty copy of database when setting team level access.

• Sales Analysis by Record Manager report generating incorrect numbers with decimal point.

• Gross Margin by Product report calculates Total Cost incorrectly.

• Opportunity by Product report display incorrect information.

• Group reports coming up blank when all sub-groups are selected in report filters.

• Deleting or changing an attachment to a Smart Task step after that Smart Task has been set to auto-run results in no attachments being included in the Smart Task step.

• When adding a Resource to an Activity, the activity is duplicated in the task list if the filter criteria for the Task List is set to "All Users". 

• Restoring database from a backup does not restore custom layouts.
  
  Workaround: Use the "Restore As" function instead of Restore.

• Attaching emails to contact history is not working in Sage ACT! Email client.

• History recording to Groups or Companies not working with emails sent through Sage ACT! Email client. 

• Error message displays when users select "Add Permissions" link in Manage Users dialog screen.

• Sage ACT! Office Add-in disables Quick Print function in Microsoft Word 2007 & 2010 after applying Sage ACT! 2011 SP1 update.

• Company Web Info tab links are not refreshed with current company data if the Web Site field has never contained data.
• Information on relationship between two contacts is not saved when using the Relationship hyperlink.
• When printing calendars using Quick Print, data from days other than those showing on the screen are printing.

• When using the Facebook® and Google® links in Internet Explorer® 8, information will not display in the Web Info tab due to changes made by these websites to not display in frames.

• In the OLEDB2 provider, ambiguous Column Name displays when querying a table that has spill-over tables.

• SDK: CustomSub Entity Record Creation Error. When attempting to create a new row for a custom sub entity, if this entity contains a yes/no or memo field with IsTracked (generate hsitory) set to true, then an error will be thrown either when the record is created, or when you attempt to modify the row.

• SDK: GetHistory(Guid entityID) returns empty collection. When attempting to retrieve a HistoryList using HistoryManager.GetHistory(Guid entityID) you will be returned an empty collection regardless of the entity ID used (Activity, Contact, Company).

• Snoozing activity alarms causes the error: "Index was outside the bounds of the array".

• Follow-up activities are not marked "private" even though the preference of "Make new activities public" is unchecked.

• If a user edits a layout within the first two minutes of opening Sage ACT!, Sage ACT! will switch between views and the layout designer 5 times. This behavior is intentional; therefore there are no plans to disable the background loading at this time.
  
  Workaround: Wait for more than two minutes before editing layouts after opening Sage ACT!.

• When performing a mail merge to a Microsoft® Word document using Microsoft Word 2010, no history record is created for the merge.

Return to top