back to top

Field level security restrictions causing errors in the SalesLogix Web Client

I recently had a client that was experiencing errors trying to navigate to Account records in the SalesLogix web client.  The errors that were displaying were similar to: “Component Parameter name: The argument component cannot be null.”

A search of the event logs on the web server reveled errors like so:  Component Parameter name: The argument component cannot be null. at
Sage.Platform.Exceptions.Guard.ArgumentNotNull(Object argumentValue, String
argumentName) at Sage.Platform.ComponentModel.ComponentView..ctor(Object
component, ComponentViewPropertyDescriptor[] extendedProperties) at
Sage.Platform.ComponentModel.ComponentView..ctor(Object component) at
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.convertTypedCollectionToComponentView(Int32
maximumRows, Int32 startRowIndex, String sortProperty, SortDirection
sortDirection) at
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.getFullCollectionList(Int32
maximumRows, Int32 startRowIndex, String sortProperty, SortDirection
sortDirection, Boolean asComponentView) at
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.GetData(Int32
maximumRows, Int32 startRowIndex, String sortProperty, SortDirection
sortDirection, Boolean asComponentView) at
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.GetData(Int32
maximumRows, Int32 startRowIndex, String sortExpression)

 

After digging what I discovered was the error was coming from the Account Opportunities tab.  The user that was experiencing the errors had restricted field level security to the Opportunity table.  One of the restrictions was the Status field was set to no access.  The Web client has several computed entity fields showing $ per status that is then displayed on the Opportunity tab at the Account.  Because of the field level security on the Status field, the entity level formulas were what was causing the errors.  Adding Status back as a read-only field in their field level security fixed the issue.

On a related not I also noticed that the Opportunity groups would not work until I added back in field level access to the following Opportunity fields: OpportunityID, AccountID, SeccodeID.

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