The most recent version of Chrome (67) is incompatible with some older versions of the SalesLogix web client.
If you are building a group based on a date and using => for the date condition we are seeing issues on selecting the beginning date
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
Start by determining if this is a click-to-run Office 2013 install
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.
If someone has deleted an existing SalesProcess and you need to restore it you can follow this guide.
This version will run on Windows 2003 x64 and is backed by Sage Support.
One of our creative SageCRM admins created a custom entity in SageCRM 6.0 and was successfully using that entity for over a year. Just recently one of his unrestricted users started getting the following error every time he tried to enter a new entity
Everyone has heard about SaaS and now the all the buzz is the Cloud. We may have our own opinions but here is how the National Institute of Standards and Technology defines the Cloud.
If you get the message "cannot login non-admin" when trying to open the Application Architect you will need to make a change to the usersecurity table
If a SalesLogix 7.5.1 Web Client user is unable to access a particular type of page, (Account, Contact, or Opportunity pages for example) even when the SalesLogix login is performed at different workstations, and other users do not experience the same problem, it probably is due
Larry Halsrud has written a thorough guide for setting up Web Clients. I would recommend it to anyone setting up a SalesLogix Web system.
We had a web client user successfully using MailMerge on a test web installation but after production was put into place mailmerge failed. With a little digging we discovered the initial download to install the Active Mail components places a .dll, Slxemailnotifier.dll, in the Windowssystem32 dir and writes a registry setting detailing what web site the SLXclient opens.
The standard settings for Reporting in SageCRM are not sufficient. We repeatedly see issues with reports failing to preview or print.
The SalesLogix WGLogs folder contains all the files the system has created for syncing data from the main database to remote users. If you have installed the Synchronization server and ran an initial sync these log files will continue to build in the WGLogs folder until the sync server runs and removes all but the active log file.
Have you ever wanted to use the Quick Find option in SalesLogix Client but wanted to look at a different field then the Account.Company, Contact.LastName, or TicketID? The quick way to accomplish this is by adding the More button to the Main View.
After a recent import into SageCRM we noticed the Person table did not reflect the same Account Manager when those people are in the same Company. We decided to update the tables in SQL rather then rerun the import and risk overwriting any new data