Just a quick note – I’m playing with the production release (R1P) of QuickBooks Enterprise 10.0 this morning, trying some of the new features relating to custom fields (more on this later), and there are problems. I can’t say how extensive this is, or how it might affect you, as I haven’t yet pinned down all of the parameters. HOWEVER, at least as far as custom fields in invoices, there are a lot of problems. If you have recieved Enterprise 10, and you use custom fields, you might want to wait awhile before using this release.
One of the traditional hassles in QuickBooks has been the limit to the number of custom fields that are available. With the 2010 release of Enterprise (10.0) I was interested to see that there are a number of improvements here. I’ll be writing about this in more detail very soon.
Two changes – an increase in the number of custom fields, and the ability to set a “type” of field (numeric, date, etc.).
I’ve run into problems with this feature. I hadn’t seen it in the beta test, as I was testing the Premier version, not Enterprise. When I create an item and a customer with the maximum number of custom fields, and modify a template to use the maximum number of fields, QuickBooks Enterprise does not behave well. I’m losing data, having problems with the fields displaying properly, and more. The problems are not consistant they don’t happen all the time, but I’m a bit concerned.
KEEP IN MIND that this is an Enterprise issue that won’t show in Pro or Premier. Also keep in mind that I’m pushing the limits of the program by maxing things out.
But, if you are using an earlier version of Enterprise, I would wait awhile before jumping into version 10.0. At the very least, install it in parallel with your current version for testing, while still using your older version for production use.
Every year I recommend that people wait to use the new release – there always are problems that show up right away. This year is no different…
Update October 6, 2009: I have been working to try to document and reproduce the problem that I ran into with my first Enterprise test. At this time I have not been able to duplicate the problem. It is possible that it had something to do with my particular installation (I have Premier and Enterprise both installed, 2008 through 2010), or some other issue that I can’t determine. Subsequent tests have not shown problems here.
Note that if you are using the additional custom fields AND you are using a third party product that works with these custom fields, you should check to make sure that third party program can handle these extra fields.
Update October 9, 2009: There are a number of potentially odd things happening with “custom fields” in QuickBooks 2010. The full extent of this isn’t clear at this time. If you use a third-party program that works with “custom fields” you should be careful before committing to QuickBooks 2010 at this time. We have definately seen some problems. However, it is not clear if these problems occur just in the “sample company” files, or if they extend to “real” company files. Intuit has changed how custom fields are handled internally, but they did NOT provide any updates to third party developers (which could be a problem).
Update October 12, 2009: Another third party software developer and I have been uncovering more and more problems with QuickBooks 2010 and “custom fields”, problems that are new to QuickBooks 2010. Again, I’ll caution people, if you use third party software that integrates with QuickBooks, be cautious about switching to QuickBooks 2010 at this time.
About the Author (Author Profile)
Charlie Russell is the founder of CCRSoftware. He’s been involved with the small business software industry since the mid 70’s, focusing on inventory and accounting software for small businesses. Charlie is a Certified Advanced QuickBooks ProAdvisor. Look for Charlie’s articles in the Accountex Report blog, as well as his California Wildflower Hikes blog.