7/1/2025 7:35:10 AM
|
|
slxdeveloper.com Community Forums |
|
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Web client vs. desktop client
Posted: 19 Jan 10 3:36 PM
|
We're moving to 7.5 from 7.2 shortly, and we've only used the desktop client. We've got several remote users, and a web-based solution will be better than a desktop/fat client solution.
We have some customizations in our slx currently, the majority of which is on the Account main view, and on a custom tab.
Can anyone give me a rough guide on the level of effort required to add the web client to the mix?
Will I be able to use both at the same time?
I've heard that all of my customizations (all done in vbscript, none in .net) have to be re-done fo the web client. is this true?
Any suggestions/guidance would be appreciated.
Thank you,
Tony
|
|
|
|
Re: Web client vs. desktop client
Posted: 20 Jan 10 9:16 AM
|
Indeed all customizations done on the Windows Client will have to be ported to the Web Client and currently that Implies that in order to keep both versions around you will need to do dual development, otherwise you have the chance of data corruption.
Now, if you are ready to move to the Web Client, it may be a good time to re-evaluate your Processes and Business Rules and do a "new" implementation on the Web (that way you may trim any excess "fat").
|
|
|
|
Re: Web client vs. desktop client
Posted: 23 Jan 10 6:28 AM
|
Strong suggestion: don't go down the road where you are doing customisations in both environments. It's just not economical.
If you are intending to do the work yourself, you should know that you will need to spend a lot of time learning how to do those things in SLX web which you already know in SLX LAN. It's a very different environment in which to develop.
Once you are up to speed, the customisation work which you currently have in LAN will take as long, or most likely longer (as you try to work out how to reproduce the required behaviour), as it took originally, to apply in SLX web.
Not trying to come over negatively here, but you need to be able to justify the cost and time differences between an upgrade to 7.5 on the LAN client (relatively straightforward) and switch to SLX web + customisation work (a new world). |
|
|
|
Re: Web client vs. desktop client
Posted: 09 Feb 10 7:16 AM
|
I agree with Phil. Customizing the WebClient is a PAIN. Requires a lot of effort and documentation is not there. There are a lot of good samples of sage education website, but they usually taking you just 1 inch away from where you want to be. |
|
|
|
Re: Web client vs. desktop client
Posted: 09 Feb 10 9:59 AM
|
Thanks for followup up. Yeah, that's a bit of a disappointment, as I'd like to get rid of the hassle of the fat client. One of our challenges is we've got 30+ workstations, so migrating to a new version is a pain. I know it would be a pain on a web version, but at least the pain is concentrated on the server side...
So I think I'll stick with fat client for now! |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|