The blogs on customerfx.com go all the way back to 2003. There's years and years worth of information that we've accumulated and shared. Since the beginning of the Infor CRM (Saleslogix) web client, we've been posting and sharing what we've learned ever since. However, if you're just starting with developing & customizing the web client, it might be hard to know what to start reading. This post will contain an index of pos...
Once you’ve started creating customizations for your SalesLogix Mobile, at some point you’ll want to start getting those customizations into production by deploying them or bundling them to add to your production system. This article will walk you through how to do this in both SalesLogix v8 as well as in SalesLogix v7.5.4. You’ll even […]
Time to take SalesLogix Mobile to the next level. Customization! This article will outline how to add custom fields to SalesLogix Mobile, from start to finish. You'll walk through every step, from creating the custom field to viewing and editing it in SalesLogix Mobile. Best part? You'll see a video that walks you through the whole process.
One of the first steps to doing customizations for the SalesLogix Mobile product is to set up a development environment. This task can be confusing for those just starting out with mobile, but with the help of the SalesLogix Mobile Developer Toolkit this is made much simpler. Even better, this article includes a video to walk you through the process.
When using Git, or really any source control system, you don't want everything in your SalesLogix model to be under source control. There are some files that the Application Architect uses for it's own purposes and volatile files that have no importance for your purposes and are recreated as needed. These files that change often with no importance to what you're working on can make things difficult when working with source control sin...
In the last post in the Git for the SalesLogix Developer series, I outlined how to set up a repository. Once that is complete, other developers can use that repository to collaborate on the project. This post outlines how to use a repository and bring it locally so you can use it for development.
If you've been following along in the Git for the SalesLogix Developer series, you should now have Git installed and configured. Now it's time to start putting it to use. In this post (and included video), I will outline the steps to take an existing SalesLogix project and put it under Git source control. Setting up the initial repository is not a hard task, but knowing all the steps is the only way to get it done.
In this second post in the "Git for the SalesLogix Developer" series, we will be taking a look at how to install and configure Git. This tutorial will give you everything you need to know if you are new to Git so you can get it all set up and ready to use. In a later post we'll look at how to use Git, but it all starts with knowing how to get started.
The first in a new series of posts on how to use Git for source control in SalesLogix development, this post will introduce Git, some Git terminology and some of the software you'll use.
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.
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
There are times when the SalesLogix Administrator is asked to import users from an .xls spreadsheet. Fortunately there is a handy little import wizard built right into the Admin application
In SalesLogix 7.5.1 Web client on a SQL2005 database there is a known defect where null values in the activity table prevent users from seeing activities in the Activities View. We have used scripts to correct the issue but those scripts must be run every time the issue reappears.