Posted Tue, 13 Mar 2018 03:56:55 GMT by jacob alley

Thank you for bringing this to our attention. I have confirmed that I am able to reproduce the issue, and I have filed a bug for you here: ...please subscribe to follow along for updates as we progress and fix the issue.

Posted Thu, 12 Apr 2018 15:00:48 GMT by
Thank you, Jacob! I've subscribed myself to the GitHub thread, so I'm following the updates of the issue.
Posted Fri, 13 Apr 2018 00:31:10 GMT by jacob alley

I did not see you subscribed, but I just closed the issue as we have found a solution. We will get you a build in the next few days that contains this fix. However in the meantime i believe you should be able to use this workaround:

<Expression ExternalProperty="TransactionOption">
  <![CDATA[@[$Project::TransactionEnabled]  ? 2 : 0]]>

Sorry that we did not get this work around to you sooner.

Posted Tue, 12 Jun 2018 17:39:16 GMT by
Good morging Jacob, with the work around you suggested I'm able to compile my projects. Thank you.
Posted Sat, 01 Dec 2018 02:56:42 GMT by

Good morning, I want to know if there is a way to dynamically disable or change the TransactionMode of a Container. With BimlExpress Build 5.0.60425.0 and lower we was able to set the SSIS TransactionOption property via Expression (see All most recent builds does not recognize anymore the values for the SSIS TransactionOption property, as you can see in my previous thread. Can you fix this regression or explain me how to reach the same goal with newer versions of BimlExpress? Unitl this error persists, I cannot update BimlExpress on my Visual Studio. Thank you.

You must be signed in to post in this forum.