back to top

Fixing lookup restrictions the SalesLogix 7.5.1 LAN Complete History screen

 

In the SalesLogix LAN client there is a bug where the Opportunity and Ticket lookups are not correctly restricting to only showing records associated to the selected Account.

SalesLogix 751 History screen

On the complete History screen in the SalesLogix LAN client you would expect that if you have selected a Contact/Account that when you did a lookup on the Opportunity or Ticket fields it would restrict to show only records associated to the selected Account.  This is how earlier versions behave (like 7.2.2).

 

If you look into the code you can see that on both of the Opportunity and Ticket lookups there is an event called OnOppTicketPopup tied to the OnPopUp event.  This code looks like this:

Sub OnOppTicketPopup(Sender)
    Sender.LookupRestrictValue = lveAccount.LookupID
End Sub

Normal enough, and you would think that it would perform the task of restricting the lookups.  Problem is, neither the Opportunity or Ticket lookup controls have any of the other Lookup Restriction properties ever set.

A lookup control requires 4 properties to be set in order for the lookup to be properly restricted:

  • LookupRestrictAlways
  • LookupRestrictField
  • LookupRestrictOp
  • LookupRestrictValue

We can fix the problem of them not correctly filtering the lookups by simply setting these properties correctly for both controls.  Now you have two options for this, you can set these properties up at design-time for both controls or you can add code to do that at run-time.  I will choose the run-time approach because I only have to set the properties once in code, rather than repeat them for both controls.

Here is the code with the correct attributes also set:

Sub OnOppTicketPopup(Sender)
    Sender.LookupRestrictAlways = True
    Sender.LookupRestrictField = “ACCOUNTID”
    Sender.LookupRestrictOp = ” = ”
    Sender.LookupRestrictValue = lveAccount.LookupID
End Sub

A simple fix.  I am attaching a bundle with this already done.  Please note that the bundle uses the standard 751 version of the plugin as its base.  If you have customized this screen you would want to manually add the code above to your custom screen.

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.

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