Introduced in Release 1.1.1, Sharing allows you to create a connector to a private data source, but “share” read-only access to that connection to other users in the account.
In this next screencast in the series, we present a overview on how to share connectors, with other users linked to the same account:
Release 1.1.1 introduces several new exciting features and fixes a handful of application bugs. The application upgrade will be applied to production servers during scheduled maintenance hours on Saturday, July 11th, 2009.
New Features:
Slicing:
You’ve been requesting this feature since the day Bluyah launched — and it’s finally here! Slicing is just our fancy name for the ability to apply filtering, sorting, and mathematical functions (COUNT(), SUM(), AVG(), etc.) to your data sets.
To enable slicing capabilities, you need to first create your “Report”. This will ensure that the structure of the data source is fully understood by Bluyah so that we can accurately enable the proper type of slicing.
Once your Report has been created, go back into the report (via the Edit link) and click on the “Slice Data” link to the right of the report title input field. This will bring up the Slicing Control Panel where you can define each of the filters, sorts, or functions to apply to your data set.
A screencast further explaining Slicing will be coming soon.
We’ve elevated the functionality of sharing several notches. Now you have complete control over every aspect of how you share your Connectors with other users in your account.
If you created a database connection and you want to only share two tables and three database views with the guy sitting at the desk next to you, the intuitive drag-n-drop interface we’ve introduces will let you do just that.
The sharing management interface is reached through several places in the application. Or you can simply click on the “Sharing” link under the My Account section of the application.
A screencast further explaining Sharing will be coming soon.
You can now get access to every invoice you’ve received from Bluyah through the application. Simply navigate to the My Account section of the website, then click on the “Invoice” link in the top navigation bar.
This feature is only available to account “admins”. This is usually the person who created the Bluyah account.
You’ve given us your feedback about needing a better way to … well … give us feedback — and we’ve heard you! Thanks to the great folks at GetSatisfaction, and the wonderful drop-in feedback form they’ve created, we now offer a community-driven knowledge base that is powered by you.
Ask a question; Answer a question. Report a bug; Offer praise. You can now do it all by simply clicking on the “Feedback” tab conveniently located on the left-hand of the screen.
Remember: we always love hearing about how folks are using Bluyah to solve new and interesting data transformation problems. So if you have done something particularly useful with Bluyah, please use the Feedback tab to share your solution with other users. You never know who might be out there trying to figure out how to do exactly the same thing.
Bug Fixes:
#267 - Report Title reset when dropping column from Report Edit screen : Fixed problem where the custom report title would ‘reset’ to the previous value if you removed from (or added a column back to) your report in the Report Edit screen.
#276 - NoMethodError (private method `format’ called for nil:NilClass) : Fixed problem where a generic (and completely unhelpful) error message would be displayed in the browser if a user attempted to view an Export for which the underlying Report had been deleted. The error message now informs the user that the export is no longer valid and that they should contact the report owner if they feel they erroneously received this error.
#285 - Handle behavior of deleted exports in Presentation : Related to #276 above, this fixes some bad behavior that would occur within the application if a Bluyah user deleted an export (eg: a map) that had been embedded in a Presentation.
#286 - Generic Xml Reports/Exports only show one line of data : Occasionally, reports based upon the “XML” connector type would only display the first row of data when rendered. It was a wily little bug, but we tracked it down and squashed it.
#310 - Source RSS parse error : There is a known (and still open bug) when attempting to parse RSS feeds that contain multi-byte characters. Given the usage of Bluyah to-date, we are not going to solve the multi-byte issue at this time. If you have a compelling need to build reports/exports off of data sets containing multi-byte characters, please submit a request through the Feedback tab so we can discuss this further.
#308 - DB Hostname field (create/edit) is too short : It was brought to our attention that users attempting to connect to databases hosted on Amazon’s EC2 service could not make a connection because we didn’t allow enough characters for the hostname field within the DB create/edit form. This has been resolved. Build all of the EC2 databases you want - and connect to them via Bluyah!
#322 - Google Spreadsheets not creating data sample : Google Docs connectors would on occasion not grab a data sample from the spreadsheet when first creating a report. This would cause the application to throw an error when users went back into the Edit the Report (though it did not affect any of the Report’s Exports.) This has now been resolved. If you load a Report in the Edit screen and do not see any data displayed, click on the “Refresh Data” button to re-fetch the data sample.
Oh yeah — you will notice that the look and feel of our homepage has been updated as well with this release.
Tell us what you think by logging in and clicking on the Feedback tab on the left of the screen. We’d love to hear from you!
