One of the beefs I've had with Netsuite is the lack of documentation on the data schema and how customizing reports can make you want to pull your hair out in clumps.
Making what I would consider to be simple changes many times renders a report useless. A prime example is when you want to run a sales summary by customer by state. Pretty basic report for a national sales manager. However, if you use the wrong "state" field, you could have some really funky results, because there are 3 different state fields you can choose from.
Other reports seem to break when you look at them cross-eyed. And don't even get me started on the formatting of financial statements.
I've got extensive experience using various SQL database engines, various report engines, and even wrote a line or two of code in my day. Interestingly enough, when I've worked with other CRM tools I was able to extract anything I wanted, mainly because the schema wasn't protected as vigorously as the habitat of a family of garter snakes that lives next to my lot line.
Even though the new report builder puts some nifty drag and drop goodies into the GUI, I see nothing that allows me to really understand the data relationships or to warn me when I'm customizing a report that probably shouldn't be touched.
I have resorted to customizing all reports so that I can export to a web query, and then dumping what amounts to all the detailed transactions out to Excel. From there, I build a summary pivot that allows me to summarize and filter and ultimately get what I need. Highly inefficient, and a painful experience learning how to finally get some meaningful reports. And because of the effort I've expended learning (and still learning) the Netsuite way of reporting, I've not been able to focus my efforts on business development.
Netsuite - I hope you're listening. Your system has helped my company immensely, but the reporting has been nothing short of woeful. The measure of any system is not the bells and whistles you advertise, but rather, how you execute the basic blocking and tackling.
Open up the vault and let us know how your schema works. Even though your competition may learn something, I'll bet the current customer base, solution providers, and 3rd party developers will sing your praises.
</rant>
Regards,
Rick Chamberlain
Director of Sales and Marketing
storeWALL, LLC
www.storewall.com