The fixes coming on Tuesday, April 19 are being used internally now by the whole company as testing continues by the development team. Everything is looking good so far.

We've traced a recent import problem to it's source and learned in Excel there's two kinds of spaces. The tricky part is they look identical, but to the importer they're different and in the problem we were fixing, that was causing a reference value to be not found. We're fixing the importer so it treats both kinds of spaces the same and that fix will be in the update on the 19th. In the meantime you can try retyping problem values in the Excel file if they have a space.

Need to import a number like "000123" and keep the leading zeros intact? The import reference explains how to do it by inserting an apostrophe in front of the number in Excel. Example: "'000123" is imported as "000123" instead of "123"

I've updated the known issues page with some problems in the new version.

I've finished updating the reference for 3.5.

The reference is no longer available as a Word document. If you miss that option, please let me know.

One of the minor improvements in 3.5 is the ability to add line breaks when entering notes. While typing a not pressing "Enter" ads the note. Now you can press "Shift + Enter" to insert an extra line without adding the note.

Update is done, our most uneventful (best) upgrade yet. Documentation will be online by the end of the day tomorrow (Tuesday) including the import spec.

It's after midnight, why am I still up? Well the development team isn't in until 5pm Monday because we're doing the 3.5 deployment. Depending on which deployment you're on, your RPM will go down at 6pm or 7pm as specified in the email you received. Everything is looking good and I'm excited to be finally letting you all use the improvements you saw at the Users Group meeting. I'll post an update when the upgrade is done.

It was nice to see everyone at the Users Group meeting. The feature survey for Jupiter will be online by the end of the Month.