Love the diagram portion of BI Documentor but cannot use it since I have to redraw from scratch. Either allow diagrams to be imported to the next snapshot, import SQL Server's diagrams, or maintain file lists across snapshots.

After deploying package(s) I would like to be able to schedule them from BI xPress too

This would enable a customer to automate publishing of SSIS code through an an automated process. Ability to hook into DLLs of BI XPress could also enable automation.

Add a property to the advanced lkp transform that allows the developer to keep and share the cache within a package. In the current version the cache gets cleared after use and you have to make a other instance of the cache with the same data, this is a bit annoying with large fact tables.

Load documentation from BI Documenter into a WIKI in SharePoint

Details about Linked Servers would be helpful because many BI systems reference Linked Servers in ETL solutions found in SSIS or SQL queries.

Have a checkbox in the deployment utility that will create a msi installation file for my packages. Very common that developers are not permitted to deploy and to have a package that can depoy all changes that can be handed to DBA would be great.

In order to have this be a functionally useful as the SSIS OLEDB Destination component we need the ability to be able to create a destination database table based upon the metadata of the SSIS data flow pipeline metadata. This would avoid having to use an OLEDB Destination simply to create the table based on the SSIS data flow pipeline metadata and then turning around and replacing that component with the Task Factory Upsert Destination component.

I don't want high pri emails for success and I may want a different group than failure or warning. I want to be able to choose each alert type differently.

It'd be nice to be able to have more flexibility with the email templates used by the Notification framework. Adding package variables and custom messages to the notification framework would be nice.

When you want to generate snapshots by recurring schedulation, it would be great if there was a possibility to have BI Documenter automatically add new SSIS packages to the solutions. Could work like SSRS, where you add a location for reports and it will document everything that has been deployed there upon snapshot creation.

Destination to load a fact table and do the surrogate key lookups.

Provide a new wizard to edit many properties of packages and tasks of selected project or folder/files.

It would be great if we had a Framework that we can apply to all SSIS packages to handle and audit NoMatch Output and Error Output for all Lookups. For example, In some cases we would like to return -1 for NoMatch lookup values and errors and be able to log in a SQL Server table such rows. This will be a great piece of information to add as an exceptions report in BIxPress.

After the audtting framework is applied, how about iterating through all of the data flows and resetting them to use Format->Auto Layout -> Diagram or do something... they look like spaghetti after your done.

Make it possible to notify different groups of people depending on the outcome of the package.

It would be great to have a search feature that would search through all of the packages in a project. This would be able to find things like variables, expressions, and task names.

BI Documenter needs to document tabular models as well as multi dimensional models.

We have some extended properties on tables whose values are different between environments (like lastrefreshdate). Because extended proprties on tables cannot be deselected all tables are marked as changed.