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 are my holdiay wishes for SalesLogix:

1. Better control over the quick form control rendering and placement.  Too often the quick forms get rendered looking terribly bad.  Controls are squished or captions wrap, controls don't line up to ones around them, etc, etc.  I know that you can add custom CSS properties to overcome this somewhat,  but really couldn't the quick from design time be better?
2. A fix for how grids are all inner joins based on the entity model.  I have discussed this one in detail in another post. 
3. Fix the resource files disappearing.  Nothing is more frustrating then completing a form, then going on to other areas only to find that, after some build and deployment, you have lost all of the data contained in a resource file for some quick from you haven’t touched recently.  In case you don't know, all of the captions, grid column headers, button captions, confirmation dialogs, and pretty much any other descriptive text you add to a quick form is stored in an associated resource file.  It is really no fun having to go back and re-key all of that information numerous times because of some glitch.  A screen with 30+ controls is a dreadful thing to have to redo.
4. The forthcoming attachment functionality in SalesLogix 7.5.2 adds attachments to the Sales order tab.  This was almost really cool in that the way the form was designed attachments can be added to any entity-almost.  The problem is that the associated compiled logic hard codes case statements to only allow attachments to work with certain entities.  Lame.  If Sage would change that logic to accept passing in an entity then the product would allow adding attachments to any entity.  That would be cool.

There are other things too like lazy initialization of the entity model that prevents some properties being usable in IRepository and grids and the like.  But the above list would be some huge wins if they were addressed.