When adding columns to an entity/object in Creatio, there are a few column names you need to avoid. The object editor won’t stop you from using these column names, but you’ll see a build error when publishing the object if you don’t avoid these. Scenario You’re adding columns to an object, which can be a […]
Have you ever had an Opportunity that you were unable to update due to Errors when trying to Save the record?
There is a specific Saleslogix Web Client error that is caused by having Infor CRM open in multiple tabs on the same browser.
You can view the errors logged by Infor CRM by looking at the Application log in the Windows Event Viewer.
If your organization uses G Suite and Creatio and you’ve just started getting an “Error 400: admin_policy_enforced” error when attempting to connect, or reconnect, your Gmail or Calendar to Creatio, this is due to a Google policy change that went into effect on November 4th, 2019. The error you see when you connect/reconnect your account […]
The most recent version of Chrome (67) is incompatible with some older versions of the SalesLogix web client.
After adding a custom bundle to Infor CRM (formerly Saleslogix) in the Application Architect two users were missing the Edit Option on a Manage Mail Options Form that was not affected by the new custom bundle, and one other user still had the Edit Option on the form. So the first thing we checked is the user's roles
We were recently contacted by a client who had a user unable to log in to the Infor CRM web client. The user was logging in with Chrome on a Microsoft Surface tablet device. As it turns out, the Infor CRM 8.1 web client is not compatible with Chrome’s touch screen drivers.
If users are not seeing the SLX Desktop Integration in Outlook after installing SLX Desktop Integration there are two troubleshooting steps that will need to be performed
An unusual error cropped up with a single Crystal Report in InforCRM. Other reports were running fine, and I was having quite a bit of trouble figuring out what the issue was.
If you see an error like this "The following SData diagnosis occurred: Description=Operation failed. Message=Could not load type 'Sage.Entity.Interfaces.ICollection`1' from assembly 'Sage.Entity.Interfaces'. HTTP status: Internal Server Error (500)." in the web client when opening an entity the issue could be a corrupted group.
Every so often we hear that a user can no longer add products to an opportunity whether it is a new opportunity or an existing opportunity. The add product plus sign is missing for no apparent reason.
We had a user looking up an opportunity by description so they could attach an email to the Opportunity. This brought the SData feature of SalesLogix into play since it is used by the SLXDesktop integration. However the Opportunity Lookup returned SData 500 error Internal Server Error.
If you are working in the SalesLogix entity model and try to loop through a collection and delete certain records, you will not be able to. This is because while you are looping through the collection you can not start removing items from the collection you are in. Instead what you can do is […]
An exception occurred executing the dynamic method Lead.SaveLeadHistory.: Transaction not successfully started. Error occurring in the SalesLogix web client and the reason for it.
If you have ever tried adding a reference to an external assembly in the SalesLogix entity model through the Application Architect and have received the error: Could not load file or assembly ‘file:///SomepathSomeAssembly.dll’ or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. […]
Ever run into an error similar to this? When trying to build a new group on a new custom entity in the web client you receive an error similar to “Unable to resolve “SomeTable” in XML Schema…”. Here is how to fix it:
I recently ran into an issue where a client was trying to restore a file system copy of the VFS into the database VFS after completing a development project. This file system VFS had been shared by several developers using a Git repository. When restoring to the database VFS, the restore process would reach near […]
"Invalid Index X for this OleDBParameterCollection" I recently ran into this error on an upgraded SalesLogix 7.5.2 web client when attempting to save changes to an entity using the standard entity.Save() method
Recently I upgraded a SalesLogix web environment from 7.5.1 to 7.5.2. Once I had done so when I tried to deploy I received the following error: ERROR - The following project item, 'PortalSlxClientChildPagesAccessAccess.page.xml' failed validation.
Subscribe To Our Newsletter
Join our mailing list to receive the latest Infor CRM (Saleslogix) and Creatio (bpm'online) news and product updates!
You have Successfully Subscribed!