back to top

Infor CRM 8.4 Update 01 highlights

Software Update

 

The Infor CRM 8.4 Update 01 release finally happened (again). A few of the highlights I got out of reading the release documents:

In both the LAN and Web client:
The Do not solicit field on the Contact Detail view is now selected by default. When creating a new contact, the default setting for the “Do Not Solicit” check box is now selected. This change was made to provide a process to support compliance with GDPR.

Seems like Leads should also have this setting then also?  But no mention of that.

 

SNC 01
Offers a New Office Profiles Privacy tab which allows Administrators to share anonymous usage data with Infor. Selecting this check box is optional. The documentation says “Data gathered will help Infor improve the product“. Whatever that means.

SNC has a lot of LAN fixes including updates to the following forms:

  • Account: Opportunities
  • Account: Reseller Opportunities
  • Account:Tickets
  • Contact Web Access
  • Dashboard: Manage Dashboard Options
  • Lead: Marketing
  • Sales Dashboard: Pipeline Status
  • Sales Dashboard: Sales Dashboard Detail
  • System: Account Detail
  • System: Account QBE Screen
  • System: Add Edit Qualification Category
  • System: Campaign Detail
  • System: Contact Detail
  • System: Opportunity Reseller
  • System: Insert Opportunity
  • System: Lead Detail
  • System: Opportunity Statistics
  • System: Opportunity Reseller
  • System: Ticket Detail

 

Core 01

Core 01 removed the following methods from the Sage.Platform namespace. This is a breaking change for any customizations making calls to these methods (I don’t think I have ever used these):

  • public static IDbConnection CreateConnection(DbProviderFactory factory, string connectionString)
  • public static IDbCommand CreateCommand(DbProviderFactory factory, IDbConnection connection)
  • public static IDbCommand CreateCommand(DbProviderFactory factory, string commandText)
  • public static IDbCommand CreateCommand(DbProviderFactory factory, string commandText, IDbConnection connection)

The documentation does define new replacements for these methods.  Not sure what the purpose of removing these was but make note if you have used them in, you will need to update the code before moving to 8.4.01.

 

In general there are a lot of fixes to defects in all of these releases. You can see full details of the release notes using the following links.

Infor_CRM_v840_SNC_Update_01

Infor_CRM_v840_Web_Core_Update_01

Infor_CRM_v840_Web_Model_Update_01

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

6 COMMENTS

  1. Thanks for the update!

    I thought the LAN client was no longer receiving updates from Infor?

    As for Leads getting the default ‘Do not Solicit” checked is debatable. Leads, in some cases, are already providing implied consent by filling out webforms, clicking “I Agree”, or voluntarily requesting more information which will insert them as a new Lead in the CRM system.

  2. RE: “The Do not solicit field on the Contact Detail view is now selected by default”

    Is there any way to override this? We use InboxGuru and it’s become a real pain to have all new contacts created either via integrations or imports having all the DONOTs = ‘T’ by default.

    • Hey Ljubomir and Kris!

      Would it work to explicitly set these values on insert over the API? Ljubomir, this would essentially be a hidden field on a contact form.

    • There is a Custom Setting to enable or disable the primary Do Not Solicit field at both Contacts and Accounts. To change this you can go to the web client’s administration nav bar and choose Custom Settings. Then search for a Default settings with a description containing “solicit”. Note that this only affects the main Do Not Solicit value. Other “Do Not” fields are not affected by this. You could however add a custom post step to the on before insert events of both contact and lead to set all of the other “Do Not” fields to be equal to how the main Do Not Solicit field is set.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos