If you’re using SData to create Opportunity records, you’ll likely need to also start sales processes for those opportunities as well. Sales processes in Infor CRM (SalesLogix) is a mess with all the XML etc. Luckily, there’s an out of the box business rule we can use that does all the messy stuff for us. […]
It’s a good practice when customizing the Infor CRM (Saleslogix) Web client to always be aware of how your customizations will impact performance. A good way to make sure that the client performs quickly is to offset work to the client, instead of always using server-side code. Using the SData API in the web client […]
Customizing the Activity Dialog in Infor CRM to Default the Activity Location to the Selected Contact’s Address
Reading Data Using the Infor CRM SData REST API from a .NET Application Using the DotNetSDataClient Library
When working with the Infor CRM SData REST API from a .NET application or website, there are a few different choices for libraries you can use to make the SData code easier. The original library was called the SDataCSharpClientLib, which I have written about previously. However, the SDataCSharpClientLib was replaced with the newer DotNetSDataClient library. […]
When you hit the test link it should test with the "The feed tested successfully" message. However, if it does not and does not change the Saleslogix Feed and instead returns Error 500 then you will need to modify the ENDPOINTURL in SQL Management Studio.
I had the need to call a business rule in Infor CRM from a stored procedure in SQL. This turned out to be a relatively easy task, although you want to make sure you think through what you’re doing for this to not introduce performance problems in SQL. Keep in mind, sometimes SData requests can […]
If this is a constant issue in the Event viewer "ERROR Sage.SalesLogix.Web.SLXMembershipProvider - No error message available, result code: E_FAIL(0x80004005)." It may be due
Accessing system level data, such as picklists, groups, etc, is an easy task with the SData system endpoint. In this post we will look at how to retrieve picklists and picklist items using SData, C#, and the DotNetSDataClient library. The DotNetSDataClient Library As I mentioned in an earlier post outlining SData resources, the DotNetSDataClient Library […]
The Infor CRM SData REST API is a web API that allows you to access the entire Infor CRM entity model, complete with business rules & events defined in the Application Architect along with other system data such as users, picklists, etc. The SData API allows you to interact with Infor CRM data over the […]
If you started with an earlier version of SalesLogix Mobile, let's say version 7.5.4, and customized the mobile platform at level 1.2 you may find the mobile client no longer runs and the existing custom screens don't allow you to upgrade to version 3.0.4. You have two options here - have someone recreate the custom screens for version 3.0.4 or remove the customized screens and start over with a basic mobile v3.0.4.
Saleslogix is very light on how to use client side processes to do things in the Saleslogix web client. I have decided to start to try to document snippets of things I find useful and make a repository of them. The first one I am showing here is how to retrieve a list of picklist […]
When installing the new XBar application I found the instructions a little vague so I thought I would pass on a clarification.
Often times a web implementation will have an application server that is used to deploy the web portals to a web host server. When the Saleslogix web client and SData portals are deployed and then tested an Internal Server Error is encountered on the URL, similar to the following: Http://Webserver:3333/slxclient/slxdata.ashx/$app/scheduling/-/executions?
I recently ran into an issue with a client’s system who was using SQL views as entities. This is a powerful capability of Saleslogix but there is one caveat. Make sure that the Saleslogix view is in all caps. When you add the view as an entity, one of the attributes that gets generated is […]
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.
If your company is using windows authentication in the SalesLogix Web client then you will want to use Windows Authentication for your mobile clients.
Although these steps are primarily for an application server with a web server to host IIS some of these steps are good checks on any Job Server install. 1. Ensure that the actual executable (SLXJobServer.exe) has been upgraded
In the SalesLogix 7.5.4+ web client the “editable grid” control that allows for inline editing and the like is based on a client side SData feed to bind and control updates. An example of this is on the Sales Order Product’s tab. This grid is actually rendered completely client side using dojo and its DataGrid […]