Skip to content

Biml updates in BIDS Helper 1.7.0 and Mist 4.0

↓ Click to read full article

Biml (Business Intelligence Markup Language)

2015 is such an exciting year for everyone using Biml! Varigence recently released version 4.0 of Mist, and now version 1.7.0 of BIDS Helper is released. Both products have implemented the changes to the Biml language, and they have both been upgraded with new features and improvements. Only some of the changes are mentioned in this post, but you can find the full release notes here:

Bids Helper 1.7.0 Downloads and Release Notes
Mist 4.0 Release Notes
Mist 4.0 Update 1 Release Notes
Mist 4.0 Webinar Recording on YouTube

Biml language highlights

Nested included files now work.

ConstraintMode is no longer a required attribute on SSIS packages, but the default has been set to Parallel so you will still need to specify the ConstraintMode if you want to create a Linear package:

<!-- Now valid: -->
<Package Name="EmptyPackage" />

Hadron is no longer used, and all namespaces that included “Hadron” have 1:1 replacements with “Biml”:

<!-- No longer valid: -->
<#@ import namespace="Varigence.Hadron.CoreLowerer.SchemaManagement" #>
 
<!-- Now valid: -->
<#@ import namespace="Varigence.Biml.CoreLowerer.SchemaManagement" #>

New code directive to reference C# or VB files directly from BimlScript:

<#@ code file="C:/Common/SharedScript.cs" #>

New Change Data Capture tasks and components: CDC Control Task, CDC Source and CDC Splitter:

CdcControl
CdcSource and CdcSplitter

BIDS Helper 1.7.0 highlights

Properly supports emitting SSIS 2014 packages in SSDTBI for Visual Studio 2013!

Shows a progress bar when Checking Biml For Errors or Generating SSIS Packages:

Checking Biml For Errors

More useful errors dialog and brings the Output window to the front:

Changed Hadron to Biml

Mist 4.0 highlights

New Metadata Modeling! (Mist 4.0 Metadata Preview on YouTube)

True Multiple Document Interface (MDI), multiple editor windows can be open at the same time (yay tab groups!):

Multiple Document Interface (MDI)

Logical View and Ribbon revamp for more intuitive grouping:

Mist 4.0 Logical View
Ribbon

New designerbimlpath attribute in the template directive so intelliprompt works correctly on code fragments like callable BimlScripts or include files:

designerbimlpath

Improved intelliprompt completion lists and option to toggle content:

Intelliprompt Toggle Extension Methods

…and much, much, much more, YAY! :) Read and/or see all the changes here:

Bids Helper 1.7.0 Downloads and Release Notes
Mist 4.0 Release Notes
Mist 4.0 Update 1 Release Notes
Mist 4.0 Webinar Recording on YouTube

About the Author

Cathrine Wilhelmsen is a Microsoft Data Platform MVP, BimlHero Certified Expert, Microsoft Certified Solutions Expert, international speaker, author, blogger, and chronic volunteer who loves teaching and sharing knowledge. She works as a Senior Business Intelligence Consultant at Inmeta, focusing on Azure Data and the Microsoft Data Platform. She loves sci-fi, chocolate, coffee, craft beers, ciders, cat gifs and smilies :)

Comments

Hi! This is Cathrine. Thank you so much for visiting my blog. I'd love to hear your thoughts, but please keep in mind that I'm not technical support for any products mentioned in this post :) Off-topic questions, comments and discussions may be moderated. Be kind to each other. Thanks!

Great post Cathrine, thanks for the info.

Hi Cathrine,

Great blog. Just started to test Mist 4.0, as bids helper nor BimlExpress do the trick anymore for my team…

We have just upgraded to Visual Studio 2015, coming from 2012. The bids helper for SQL 2016 isn’t ready at all in my opinion, we can’t even build SSIS packages or check for errors… error straight away when I right click the script to build the package(s).

So we moved on to BimlExpress, which does the trick, as long as one sticks to general stuff, which off course is never the case in an organization.

In short, we use ADO.NET on DB2 for some of our source components in DFTs and BimlExpress just can’t build packages using the DB2 ADONET provider from IBM (giving error message that sql server couldn’t be found). Pretty frustrating because this used to work on VS2012 and without biml, meaning “hard-coding” in SSIS this works just fine as well.

Same with CDC Source. The package is generated but we can’t edit the CDC Source component (has a generic icon and can’t double-click or right-click -> properties)

Next step then was to try Mist. Generating an empty package works, but once I add a simple (and empty!) DFT, it still builds fine, although the generated package is corrupt when I try to open it in the VS designer and the DFT becomes uneditable with that annoying generic icon.

I don’t expect any solution from your side, just your thoughts regarding following would be great.
Do you work with VS2015 and if yes, do you think biml is capable to build complex packages and if yes, what “generator” would be your choice?
Maybe it is due to our environment, but seriously, we have nothing but trouble ever since upgrading our VS/SSDT.

Cheers,
Tom

Tom, we are also looking at ADO.Net and DB2 and running into the same issue you note above with the error message that sql server couldn’t be found. Did you find any solution? Catherine do you have nay tips/tricks for this situation you can point me to?
Thanks,
-Luke.

Hi Cathrine, where do I download Mist 4.0 and BimlStudio from ?

Hi Kevin, BimlStudio is the new name for Mist. You can download a trial from Varigence’s BimlStudio website.

Hi! This is Cathrine (again). Just a reminder. I'd love to hear your thoughts, but please keep in mind that I'm not technical support for any products mentioned in this post :) Off-topic questions, comments and discussions may be moderated. Be kind to each other. Thanks!

Leave a Reply to Reeves Smith Cancel reply