back to top

Disabling Asset Creation in the Infor CRM Web Client

In the Infor CRM web client, when you Close and Win an opportunity one of the things that happens is the Opportunity Products on the Opportunity become Assets at the Account level.

Several of our clients have asked how to turn off this functionality. Unfortunately it is not as easy as it should be to disable this but it is possible. This post will walk through how to do this.

There are 2 places that Assets can be created from an Opportunity. On the OnBeforeUpdate event and on the OnAfterInsert event there are actions to create these Assets. Both of these events have a primary step that calls a compiled method in the Sage.Saleslogix.BusinessRules.dll assembly. Since this is a compiled assembly we cant modify these events. Instead what we need to do is to replace the primary steps with our own custom primary steps.

OnBeforeUpdate
In the OnBeforeUpdate event you will want to add a new Primary step. Make this new step the active one which will disable the standard event OnBeforeUpdate wired up to the standard Business Rule Event.

In your Primary step, you will choose a C# Code Snippet.

You will need to add an assembly reference to Sage.SalesLogix.Plugins.dll

In the code itself you need to add the following:

Sage.SalesLogix.Opportunity.Rules.ValidateOpportunity(opportunity);
if (opportunity.Status ==  "Closed - Lost")
    opportunity.CloseProbability = new int?(0);
else if (opportunity.Status ==  "Closed - Won")
{
    opportunity.CloseProbability = new int?(100);
    //Rules.MoveOppProductsToAssets(opportunity);
}
Sage.SalesLogix.Opportunity.Rules.EnsureDocumentPricing(opportunity);
Sage.SalesLogix.Opportunity.Rules.SetBOEKeyFields(opportunity);

OnAfterInsert
In the OnAfterInsert event you will want to add a new Primary step. Make this new step the active one which will disable the standard event OnAfterUpdate wired up to the standard Business Rule Event.

In your Primary step, you will choose a C# Code Snippet.

You will need to add assembly references to

  • Sage.SalesLogix.Plugins.dll
  • Sage.SalesLogix.BusinessRules.dll

In the code itself you need to add the following:

if (opportunity.Status ==  "Closed - Lost")
	opportunity.CloseProbability = new int?(0);
else if (opportunity.Status ==  "Closed - Won")
{
	opportunity.CloseProbability = new int?(100);
	Sage.SalesLogix.Opportunity.Rules.ValidateOpportunity(opportunity);
	//Rules.MoveOppProductsToAssets(opportunity);
}
//SetupSalesProcess, this had to be re-written because it is protected in the assembly			
string commonOption = Sage.Platform.Application.ApplicationContext.Current.Services.Get<Sage.Platform.Application.Services.IUserOptionsService>().GetCommonOption("cboSalesProcess", "OpportunityDefaults");
if (string.IsNullOrEmpty(commonOption) || !(commonOption != "NONE"))
	return;
			
string pluginIdFromName = string.Empty;
foreach (Sage.SalesLogix.Plugins.Plugin salesProcessPlugin in (System.Collections.Generic.IEnumerable<Sage.SalesLogix.Plugins.Plugin>) Sage.SalesLogix.SalesProcess.Helpers.GetSalesProcessPluginList())
{
	if (string.Equals(commonOption, salesProcessPlugin.Name, StringComparison.InvariantCultureIgnoreCase))
		pluginIdFromName = salesProcessPlugin.PluginId;
}						
      		
if (string.IsNullOrEmpty(pluginIdFromName))
	return;
			
Sage.Platform.EntityFactory.Create<Sage.Entity.Interfaces.ISalesProcesses>().InitSalesProcess(pluginIdFromName, opportunity.Id.ToString());
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