back to top

Infor CRM Merge Contact- Handling Account Product Contacts

When performing a merge of contacts in the Infor CRM web client it handles merging a lot of child records off the contact. One area that is not touched is the account product area where a contact is defined. if you are merging a contact associated to an account product, the merged contact remains associated to the account product rather than being updated to the contact it was merged with.

This posts shows how to add this feature.

The first thing to do is expand out the entity model in the Application Architect.

Go to the Contact entity’s Rules.

Double click the MergeContact rule.

On the Post Execute task you can see all of the secondary steps to handle moving the child records.

Go ahead and click add to add a new post-step
Infor CRM Add new Post Step
Name the post something unique. In my case I called it “MergeContact_FXMoveAssets” I didn’t follow the Infor naming convention in case they ever decide to add this step by default, having a duplicate step name will cause problems.
InforCRM Post Step

You will now see your step. Go ahead and click the Edit Code Snippet link.

The first thing you will need to do is add an assembly reference. Unfortunately the assembly we need is not located anywhere convenient. It is called Sage.SalesLogix.Services.PotentialMatch.dll I copied the dll from the Bin folder of the web portal to my base build path’s assemblies sub-folder. Then I added an assembly reference in my custom step:
Infor CRM add Assembly Reference

Now with that assembly we can add the code that will use that service which is passed into our event to get the Source Contact Id. From there we use a SQL statement to update all of the account products that have that contact associated and then update them with the new contact, which is also passed in:

			Sage.SalesLogix.Services.PotentialMatch.MergeProvider mp = mergeProvider as Sage.SalesLogix.Services.PotentialMatch.MergeProvider;			
			string sourceContactId = mp.Source.EntityId;	
			string targetContactId = mp.Target.EntityId;	
			string dupId = string.Empty;			
			
			if(contact.Id.ToString()!=sourceContactId) dupId=sourceContactId;
			if(contact.Id.ToString()!=targetContactId) dupId=targetContactId;
			
			Sage.Platform.Data.IDataService datasvc = Sage.Platform.Application.ApplicationContext.Current.Services.Get<Sage.Platform.Data.IDataService>();
		    using (System.Data.OleDb.OleDbConnection conn = new System.Data.OleDb.OleDbConnection(datasvc.GetConnectionString()))
		    {
		        conn.Open();
		        using (System.Data.OleDb.OleDbCommand cmd = new System.Data.OleDb.OleDbCommand("update accountproduct set contactid = '" + contact.Id.ToString() + "' where contactid='" + dupId + "'", conn))
		        {
		            int o = cmd.ExecuteNonQuery();						
		        }
		    }			

            result = true;
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