back to top

Setting the Defaults on the Insert Account/Contact Duplicate Record View

 When creating a new Account/Contact record in Saleslogix Web, you have the ability to check for duplicate values.  With some simple modifications to the code page behind that form, you can set default values for the Match Filters.

 

 All of these changes will be performed on the ContactSearchForDuplicates.ascx.cs script found under Sage SalesLogix->Support Files->Smartparts->Contact in the Portal Manager in Application Architect.

 The first step will be to modify the  LoadMatchFilters method in this script.  After the line setting the item.Value equal to the propertyFilter.PropertyName property, we will add an IF statement to identity which fields should be checked by default:

            item.Value = propertyFilter.PropertyName;
            if (item.Text == “First Name” || item.Text == “Last Name” || item.Text == “Work Phone” || item.Text == “E-Mail”)
            {
                item.Selected = true;
            }
            else
            {
                item.Selected = propertyFilter.Enabled;
            }

As you can see, I’m setting the First Name, Last Name, Work Phone and Email fields to be checked.  Otherwise, I’m just using the PropertyFilter.Enabled property.

Since the filters are set on the OnPreRender method of this form, and the OnPreRender method fires when clicking the “Update Potential Matches” button, we’ll need add a check to make sure the default values are not reset.

To check this, we’ll create a private Boolean variable, set by an OnActivating function

            private bool _runActivating;
            protected override void OnActivating()
            {
                        _runActivating = true;
            }

We’ll set this Boolean in the OnLoad event of the form:

         if (_runActivating) DoActivating();

Finally, we’ll modify the OnPreRender method to conditionally run the LoadMatchFilters and LoadSourceEntity methods after checking the _RunActiviating value:

            if (_runActivating)

            {LoadMatchFilters();
            LoadSourceEntity();}
            LoadPotentialMatches();

 That’s it!  The match filters defined should now be checked when opening the duplicate record view.  Thanks for reading!

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
Jason Buss
Jason Buss
Jason is a senior application developer with Customer FX.

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