back to top

SalesLogix v8.0 “Core Web Update 04” and “Quote and Forecast” breaks Speedsearch

We recently installed the SalesLogix web update 04 into a demo system and after doing so were unable to use Speedsearch in the SalesLogix web client.  Looking into the error I was lead to the Speedsearch.aspx file’s Page_Load code.

 

Looking into the Page_Load, I can see the actual error was caused by the call to LoadIndexes.

Looking in the event logs on the server I found this error:

  “message”: “An item with the same key has already been added.”,

 OK so we see that a Dictionary object is having problems with a duplicate key attempting to be added.  Lets look at that LoadIndexes script.

    private void LoadIndexes()
    {
        if ((_Indexes == null) || (_Indexes.Count == 0))
        {
            IRepository<IIndexDefinition> rep = EntityFactory.GetRepository<IIndexDefinition>();
            IQueryable qry = (IQueryable)rep;
            IExpressionFactory ef = qry.GetExpressionFactory();
            ICriteria crit = qry.CreateCriteria();
            IExpression accessExp = ef.Le(“UserAccess”, _UserType);
            crit.Add(ef.And(accessExp, ef.Eq(“Enabled”, true)));
            crit.AddOrder(ef.Asc(“IndexName”));
            IList<IIndexDefinition> tempIndexes = crit.List<IIndexDefinition>();

            Assembly interfaceAsm = Assembly.GetAssembly(typeof(IIndexDefinition));
            Type[] types = interfaceAsm.GetTypes();
            _TablesEntities = new Dictionary<string, Type>();
            foreach (Type entity in types)
            {
                AttributeCollection attrs = TypeDescriptor.GetAttributes(entity);
                foreach (Attribute attr in attrs)
                {
                    ActiveRecordAttribute activeRecord = attr as ActiveRecordAttribute;
                    if (activeRecord != null)
                    {
                        _TablesEntities.Add(activeRecord.Table.ToUpper(), entity);
                    }
                }
            }
….

The line 

Type[] types = interfaceAsm.GetTypes()

Is creating an array of every interface object in the system.  They then loop through each interface and add the underlying table the entity is bound to the index (which is where the problem is).  Adding an debugging output I found that CUSTOMSETTING is the duplicate key being added.

Sure enough looking into the Web Update 04 manifest I see it is being added:

 

But the problem is that results in a duplicate entity in the entity model:

 

So where did the CustomSettings come from?  The Quota and Forecasting manifest!

 

Hence the duplicate key in the dictionary!

I removed the CustomSettings and kept the CustomSetting entity. 

Doing the reverse does not allow SLX to open.

However deleting the CustomSettings entity breaks the Quota and Forecast.

Here are the conflicts that must be resolved:

 

The only ones that need to be fixes are:

  1. The FinancialSettings quickform (the code throughout out the form)
  2. The FiscalAPI.cs file, all of the references in the code.

SalesLogix needs to fix this one pronto obviously.

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