SugarCRM 5.2.0 patch D Released

bsoremsugar —  April 24, 2009 — 2 Comments

I just wanted to bring to your attention that SugarCRM has released 5.2.0d.  Here’s what you need to know:

New Features, Enhancements, and Behavior Changes

A new Repair option named “Repair Non-Lowercased Fields” allows you to use mixed-case field names when searching for records

Fixed Bugs in 5.2d

Bug 20619 – The get_relationships function fails for custom modules.

Bug 20728 – Fields referencing a custom drop-down list that was not created through the Module Builder do not load properly in Module Builder when exported and loaded on another system, and hence cannot be edited in the new system.

Bug 22836 – The Group User name does not display in the record’s Detail View.

Bug 25151 – When you click an email address in the Employees List View to compose an email, the “To” field does not display.

Bug 25485 – When using a SQL Server database, when you sort a paginated Accounts List View by a custom field, the system displays an “incorrect syntax” error if you click the Next button to navigate to the next page.

Bug 25598 – The value Amount of an opportunity is not converted correctly from EUR to USD for a contract with a default currency of EUR.

Bug 25718 – You are unable to import data for custom multi-select fields with default value.

Bug 26666 – You cannot use mixed-case field names in Search forms.

Bug 27476 – When installing Sugar 5.2.0 with MS SQL database, an error prompts Sugar to create a new MSSQL user.

Bug 27490 – Account links in the Contacts dashlet are incorrect.

Bug 27491 – Related record links in the Meetings dashlet are incorrect.

Bug 27564 – When composing an email, personal and group email addresses are not differentiated in the “From” drop-down list.

Bug 27674 – If you do not have the latest Sugar version, the Configure Sugar Updates page displays strange characters.

Bug 27693 – When you click an email address from the Leads List View, the To field does not display the email address of the lead.

Bug 27877 – Roles created for a custom module are deleted if you re-deploy the module.

Bug 28159 – The Campaign Log label incorrectly displays as “Campaigns”.

Bug 28411 – The My Pipeline By Sales Stage dashlet displays wrong total sum value if the user’s default currency is different from the system default currency.

Bug 28412 – Bar charts do not work if the user’s default currency is different from the system default currency.

Bug 28461 – When importing multi-byte data into Sugar, the length is calculated in bytes instead of characters.

Bug 28586 – When you run a cron job from the Suger User Interface or cron.php from the command line, the tracker table is populated when Tracker Actions is the only box selected on the Tracker Settings page.

Bug 29037 – When importing emails, any email with the word “java” in the message ID is imported multiple times.

A full listing of all bugs fixed in this patch including further details on the bugs listed above can be found in the Bug Tracker.

Compatibility Matrix is available here

Known Limitations

Some entry points were changed in Sugar 5.1. Hence, a custom file created in 5.0, unless you manually updated it with the new entry point in 5.1, may fail in 5.2 with the error message “Not a valid entry point”.

For example, if you have customized vCard, navigate to custommodules
<modulename>metadatadetailviewdefs.php
and replace:

<name=”vcard” action=”vCard.php”>

with the following:

<name=”vcard” action=”index.php”>

<input type=”hidden” name=”entryPoint” value=”vCard”>

2 responses to SugarCRM 5.2.0 patch D Released

  1. 

    Hi,

    I am struggling with the vCard “not a valid entrypoint” issue from the contacts module. I have not made any adoptions to the vcard form, I am running 5.2, latset patch, the above is NO guidance.

    Any other clever suggestions?

    Regards

  2. 

    Hi,

    I am struggling with the vCard “not a valid entrypoint” issue from the contacts module. I have not made any adoptions to the vcard form, I am running 5.2, latset patch, the above is NO guidance.

    Any other clever suggestions?

    Regards

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s