I had a couple of major bugs creep up on me. Some of them were due to neglegance or my rush in getting things done.
I'll be implementing the fixes this weekend as well as finalize the sync service, my maintenance routines running outside of the lame scheduler, and finally make it so the Admin user doesn't have to be logged in for the server to function normally. I could have had this mended in 5.2 but my limited knowledge of the sync service didn't make me confident enough.
One of the bugs is in the FormatCurrency and FormatPercent functions in VBScript. In fact, it probably affects any Format* function. If you try to pass a null value to formatcurrency or formatpercent, you get a lovely error. My error checking in all of my forms will halt everything on error (which may be an issue on my part) but it makes it so that I have to catch every error before the user sees it. This isn't a problem for me but it'd be nice to know this about FormatCurrency before I finalized the customization.
Other bugs are merely cosmetic problems. The forms are way too big on a 800x600 screen and the guides SalesLogix gives in the Architect are good but not good enough. I think the problem is simply that everyone is content with 800x600 when in actuality SalesLogix almost demands a 1024x768 screen. I can bump up the font size if this is a problem but people here are content in using the max setting for graphics cards back in '92 (I'm making up the year but it's been FOREVER since 800x600 was the max resolution by both monitor and graphics card).
I have one bug that is a show stopper, and the reason I'm batch updating this weekend. It seems that on my implementation and even the new database I upgraded that DBInsert isn't going to work correctly in the legacy environment. It may be that I deleted plugins I shouldn't have, or used delete from plugin when I should have somehow hacked Architect to remove the stale plugin types (or left it in like a good little boy, but I'm anal and I want the database as small as possible). Anyways this problem is royally pissing me off because on top of DBInsert throwing an error, using CreateIDFor(”Contact”) give me a FALSE value instead of the normal id value it should produce.
I've tried everything. I thought it was hotfix 3 so I reinstalled SalesLogix on my testing machine upgrading to SP2 but leaving the hotfix off. No dice. What's strange is this worked in every one of my upgrade tests but it's an issue in the production and even development databases. My testing on this will be limited. I'm going to add a small customization that calls the VBScript GetIDFor which should produce a correct ID for the system tables. If this works then I'll have to install the original bundle in the hopes that the original works correctly. If so then I'll repackage it with my changes and hope that it finally functions in our production environment.
I plan on releasing my upgrade plan and developing software around it to hopefully help upgrades in the future. I like our database to be as lean as possible and the default SalesLogix upgrade plan just doesn't do that. I've noticed a number of stale plugins so hopefully I can develop something that'll keep the clutter to a minimum and upgrade the database like I want it instead of how it has to be.