Login /
Register
 search
 syndication
|
|
 |
Note: this subscription applies to the current blog only.
You will receive each new post via e-mail. Your e-mail
address will not be used for any other purpose.
Browse by Tags
All Tags » SalesLogix Web ( RSS)
-
|
In the SalesLogix web client you may run across a reason you need to generate a “Pretty Key”. This is what the SalesLogix Ticket Number is. This key is a combination of a Pretty Prefix and a Pretty Suffix. The Prefix is an equivalent to a system’s site code and the Suffix is a numerical equivalent to a primary table ID.
To generate these you can simply call the functions in the Sage.SalesLogix.System.dll for each
|
-
|
Often when adding custom code to SalesLogix you need to reference Assemblies that are not included by default in Code Snippets or action items. This problem will often manifest itself with an error when building like “The type or namespace name 'Data'...
|
-
|
Starting in SalesLogix 7.5.1, Sage released an undocumented Reporting enhancement that allowed for interacting with the SalesLogix web reporting Server. The SalesLogix 7.5.2 release had this API enhancement built in, however little documentation exists and now standard samples are used in the web client.
Hopefully this article will help out those who are trying to figure this out.
|
-
|
Occasionally we have clients who do not use the Opportunity components of the SalesLogix web client. They have asked us to remove the Opportunity visibility within the web client. Since this is not a common occurrence, I usually end up having to go back...
|
-
|
In SalesLogix you can use the Sage.Platform.Repository.ICriteria class to query the entity model using standard ICriteria. One thing I have been asked in the past is how do you exclude certain conditions? A common example might be show me all of the non...
|
-
|
I recently ran into this error on a client’s system when users logged into the SalesLogix client and navigated to a recently updated page. The administrator did not encounter the same issue when navigating to the same page. Since I knew no log-in specific...
|
-
|
The SalesLogix entity model offers a really great way of working with data in SalesLogix and letting the system establish all of the links for you- as long as you know what you are doing.
One of the really great things that you can do is to add child entities to a parent, even if the parent is not yet in the database. This is especially helpful if you need to create child records while still on an insert screen.
|
-
|
SalesLogix web has a “ComboBox” control which is actually rendered on the deployed page as an ASP ListBox control. In the Application Architect you can see the control has two properties for Value and Text. The value One would assume SalesLogix would...
|
-
|
The SalesLogix web client has a couple of locations that they have a button to add a user time stamp within a memo field. For instance, on the standard Ticket Extended Details, on the Problem and Solution fields. If you look at these buttons they are...
|
-
|
SalesLogix released hotfix 1 for SalesLogix 7.5.2. One of the published resolutions of the hot fix was a modification to the dependency lookup to fix defect 1-72412 “Editing ACI values on the ticket causes the ACI view to freeze”. This fix...
|
-
|
Each user of the SalesLogix web client can define various user based settings while they are using the SalesLogix web client. Things such as splitter height, visible tabs, open tabs, etc are all stored per user. Sometimes these settings block other changes...
|
-
|
In the SalesLogix web client the insert Account Contact screen behaves differently than the LAN version in that you can modify the Account level fields when you select an existing Account to use. I was recently asked how to make it work like the LAN client...
|
-
|
"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, '\Portal\SlxClient\ChildPages\Access\Access.page.xml' failed validation.
|
-
|
I have found what appears to be a bug in 7.5.2 and the handling of external assemblies referenced for use in SalesLogix code, like business rules, events, custom properties, etc. I had a system that had multiple external assemblies handling some...
|
-
|
I have not found any official reference to this change anyplace: prior to 7.5.2 the Sage.Entity.Interfaces.IOwner entity contained a RightsCollection collection of user rights (Sage.Entity.Interfaces.IOwnerRights which represents the database table SECRIGHTS...
|
-
|
During the SalesLogix upgrade from a previous version of the SalesLogix web client ot 7.5.2 one of the procedures is to create a manifest bundle of all of you customizations. SalesLogix has now provided a utility to help compare what from your custom...
|
-
|
Not sure under what circumstances this will occur but I just ran into this on a Windows 7 64bit computer and thought I would post. After upgrading the computer from a 7.5.1 installation to 7.5.2 I was unable to open the Application architect. An error...
|
-
|
In my previous post , I mentioned how to get the selected ID of a gridview’s row when you click the row. Since then I have found that sometimes SalesLogix will implement an extra DataKey in the grid when it is deployed as a quick form. (For...
|
-
|
SalesLogix has a couple of numeric based custom text controls including currency, and numeric. One of the things you will find is that using these controls gives the user a slightly different experience based on the custom control chosen. ...
|
-
|
One of the things that is often asked is how can you call a certain lookup’s “Popup event” from code in the SalesLogix web client. The SalesLogix web uses JavaScript to launch these lookups. You can see the invoke code of the JavaScript by...
|
-
|
I recently was having problems seeing changes I was making to a deployed ASP.Net SalesLogix web page. Specifically, the changes I was making to a Lookup control. What I discovered is that the changes to my page were not reflected in my lookup...
|
-
|
If you have ever added code similar to: mygrid.Sort("CreateDate", SortDirection.Descending); You may have seen an error similar to this: System.Web.HttpException: The GridView 'mygrid' fired event Sorting which wasn't handled.
|
-
|
One of the cool things about the SalesLogix web client is that you can re-use the same form for inserting a new record or updating a record. While you could do this with Data forms in the SalesLogix LAN client, if you wanted to use the same form...
|
-
|
I have been asked a couple of times about what are the things that I would like to see work better/different in the SalesLogix web client. I have thought about it and have come up with a few things I think would make a big difference. So here...
|
More Posts Next page »
|  |
|