Bluyah Development Blog

Version 1.0.1 of the Bluyah app was released today.  The following bug fixes and enhancements are included:

• Fixed a problem where creating a new Marquee could throw a fatal error if created against an RSS feed that contained no data. [Ticket #198]
• Fixed an issue with charts where IE users (gotta love IE!!) were not able to view or edit any charts. [Ticket #212]
• Hardened all of the Exports to better inform the user if they were attempting to render an export against a deactivated (or deleted) report. [Ticket #85]
• In a related issue, changed the list display for Reports and Exports to highlight those items where the underlying data Connector had been invalidated.  This should make it easier for users to know when a connection to their data source can not be made (Feed went away, or DB password is no longer valid, etc.).  [Ticket #208] 
• Added logic to the Report create/edit screen to prevent users from creating a report with a name that is already in use. [Ticket #187]
• All exports in the Export list now contain a direct link to their underlying report.  This should make it easier for you to make tweaks to the right report, if needed. [Ticket #126] 
• Added better messaging to the Google Docs parser to inform users if their underlying spreadsheet is in a format that can not be understood by Bluyah (hint: All reportable columns MUST have a column name in row 1).  [Ticket #214]
• Added support for Microsoft SQL Server database Connector.  This has been a much-requested feature - so have at it. [Ticket #111]  

Just to keep everyone up to date: DB2 and PostgreSQL database support is coming soon.  We’re still running through all of the test cases, so thanks for your continued patience.   We will let everyone know via Twitter when we have settled on the actual launch date.  You are following us on Twitter, right?