Upgrading to BimlStudio 2027
This article covers the changes in BimlStudio 2027 that can affect a project built with an earlier version of BimlStudio. Each section says who is affected, what changes and, where there is something to do, what to do. For everything else that is new, see the BimlStudio 2027 release notes.
Which sections apply to you
| Section | Read it if |
|---|---|
| Retired Azure Data Factory connectors | A project has linked services, datasets or copy sources for a connector that Azure Data Factory has retired, or for an earlier connector version that it has replaced, or a QuickBooks or Xero linked service. |
| Other Biml language changes | A project has a Jira or Xero copy source, a Jira dataset, a QuickBooks or Vertica linked service, or a Databricks Jar or Python activity. |
| Classic Azure Machine Learning | A project uses the classic Azure Machine Learning linked service or its two activities. |
| SSIS casts to DT_NUMERIC | An SSIS variable or property expression casts a value to DT_NUMERIC or DT_DECIMAL, or writes such a value as text. |
| Subversion | You use Subversion or TortoiseSVN as the source control provider in BimlStudio. |
Retired Azure Data Factory connectors
This section applies to you if a project has linked services, datasets or copy sources for any of the connectors in the tables below, or a QuickBooks or Xero linked service. Before you upgrade, remove the retired connectors in the first table from your projects or replace them with a supported connector. For the earlier connector versions in the second table, change to the current element. For QuickBooks and Xero, change how the linked service signs in after you upgrade.
Microsoft has removed the first ten connectors in the first table from the Azure Data Factory service. For these ten, existing pipelines no longer execute and new workloads cannot be created, so they do not work in Azure Data Factory regardless of this change in BimlStudio. The Azure Data Factory service retired the other five on 31 December 2024.
BimlStudio 2027 removes the Biml language elements for these connectors and the support for building them. A project that still uses them reports Biml schema errors in BimlStudio 2027.
| Connector | Retired by Azure Data Factory | Error in BimlStudio 2027 |
|---|---|---|
| Amazon Marketplace Web Service (MWS) | Removed after Amazon shut down the MWS API on 31 March 2024 | Biml schema errors |
| Concur | 31 December 2024 | Biml schema errors |
| Couchbase | 31 December 2024 | Biml schema errors |
| Drill | 31 December 2024 | Biml schema errors |
| HBase | 31 December 2024 | Biml schema errors |
| Magento | 31 December 2024 | Biml schema errors |
| Marketo | 31 December 2024 | Biml schema errors |
| PayPal | 31 December 2024 | Biml schema errors |
| Phoenix | 31 December 2024 | Biml schema errors |
| Zoho | 31 December 2024 | Biml schema errors |
| Azure Database for MariaDB | 31 December 2024 | Biml schema errors |
| Oracle Eloqua | 31 December 2024 | Biml schema errors |
| Oracle Responsys | 31 December 2024 | Biml schema errors |
| Oracle Service Cloud | 31 December 2024 | Biml schema errors |
| Salesforce Marketing Cloud | 31 December 2024 | Biml schema errors |
A project that uses Azure Database for MariaDB or Oracle Service Cloud builds in BimlStudio 2026 R1, but the output it produces for them does not work. BimlStudio 2026 R1 writes the Azure Database for MariaDB linked service and copy source without a type. It writes the Oracle Service Cloud linked service without the host from its Host attribute, so that linked service does not work unless you supplied the host another way. BimlStudio 2027 reports Biml schema errors for both connectors when you build.
BimlStudio 2027 also removes the Biml elements for earlier versions of connectors that Azure Data Factory has replaced with a newer version. A project that still uses one of them reports Biml schema errors, so change it to the current element. The current elements do not always take the same attributes as the earlier ones. ServiceNowV2 is new in BimlStudio 2027, so make that change after you upgrade.
| Removed element | Use instead |
|---|---|
MongoDb and MongoDbSource | MongoDbV2 and MongoDbV2Source |
ServiceNow and ServiceNowSource | ServiceNowV2 and ServiceNowV2Source |
GoogleBigQuery and GoogleBigQuerySource | GoogleBigQueryV2 and GoogleBigQueryV2Source |
Snowflake and SnowflakeSource | SnowflakeV2 and SnowflakeV2Source |
MySqlLegacy | MySql |
PostgreSqlLegacy | PostgreSql |
OracleLegacy | Oracle |
A project with a PostgreSqlLegacy linked service builds in BimlStudio 2026 R1, but the linked service it produces has the type PostgresSql, which is not an Azure Data Factory type, so it does not work. BimlStudio 2027 reports a Biml schema error for it when you build.
The QuickBooks and Xero linked services stay, but the way they sign in has changed, and the earlier attributes and elements report Biml schema errors:
- QuickBooks. The
AccessToken,AccessTokenSecretandUseEncryptedEndpointsattributes and theAccessTokenKVSandAccessTokenSecretKVSelements are removed. UseRefreshTokenorRefreshTokenKVS. - Xero. The
ConsumerKeyandPrivateKeyattributes and theConsumerKeyKVSandPrivateKeyKVSelements are removed. UseTenantId,ClientId,ClientSecretorClientSecretKVS, andRefreshTokenorRefreshTokenKVS.TenantIdis required.
These attributes and elements are new in BimlStudio 2027, so change a QuickBooks or Xero linked service after you upgrade.
Other Biml language changes
This section applies to you if a project uses any of the elements in the table below. BimlStudio 2027 removes some of their child elements and makes some of their attributes required, so a project that builds in BimlStudio 2026 R1 can report Biml schema errors in BimlStudio 2027. A removed child element reports that its parent has an invalid child element, such as has invalid child element 'Query'. A missing required attribute reports an error such as The required attribute 'Schema' is missing.
The last column says when you can make the change. Before you upgrade means that BimlStudio 2026 R1 already accepts what to write instead. After you upgrade means that what to write instead is new in BimlStudio 2027, or that BimlStudio 2026 R1 still requires the element that BimlStudio 2027 removes.
| Element | What changes in BimlStudio 2027 | What to write instead | When |
|---|---|---|---|
JiraSource copy source | The Query element is removed. | Name the data with the Schema and Table attributes of the Jira dataset. | After you upgrade, because BimlStudio 2026 R1 requires Query on this source. |
Jira dataset | The Schema and Table attributes are required. Schema is new in BimlStudio 2027. | Add Schema and Table. | You can add Table before you upgrade. Add Schema after you upgrade. |
XeroSource copy source | The Query element is removed. | Name the table with the Table attribute of the Xero dataset. BimlStudio 2027 reports an error for a Xero dataset without Table. | You can add Table before you upgrade. Remove Query after you upgrade, because BimlStudio 2026 R1 requires it on this source. |
QuickBooks linked service | The ConsumerKey attribute is required. | Add ConsumerKey. | Before you upgrade. |
Vertica linked service | The Server, Database and Uid attributes are required. They are new in BimlStudio 2027. | Add Server, Database and Uid. | After you upgrade. |
DatabricksJar activity | The MainClassName attribute is required. It is new in BimlStudio 2027. A project with this activity builds in BimlStudio 2026 R1, but the activity it produces has no mainClassName, so it does not work unless you supplied one another way. BimlStudio 2027 reports the missing attribute when you build. | Add MainClassName with the full name of the class that contains the main method. The class must be in a JAR provided as a library. | After you upgrade. |
DatabricksPython activity | The PythonFile attribute is required. It is new in BimlStudio 2027. A project with this activity builds in BimlStudio 2026 R1, but the activity it produces has no pythonFile, so it does not work unless you supplied one another way. BimlStudio 2027 reports the missing attribute when you build. | Add PythonFile with the URI of the Python file to run. DBFS paths are supported. | After you upgrade. |
Classic Azure Machine Learning
This section applies to you if a project uses the classic Azure Machine Learning linked service (Data Factory type AzureML) or either of the classic Machine Learning activities, AzureMLBatchExecution and AzureMLUpdateResource. Before you upgrade, remove those items from your projects or replace them.
The Azure Data Factory service refuses the classic Azure Machine Learning linked service type, so BimlStudio 2027 removes the Biml language elements for the linked service and the two activities, along with the support for building them. A project that still uses them reports Biml schema errors.
The Azure ML Service linked service and the Machine Learning Execute Pipeline activity are still supported.
SSIS casts to DT_NUMERIC
This section applies to you if an SSIS variable or property expression in your project casts a value to DT_NUMERIC or DT_DECIMAL, or writes a DT_NUMERIC, DT_DECIMAL or DT_CY value as text. Check those expressions before you upgrade, because they can now evaluate to a different value or stop the build.
BimlStudio 2027 evaluates these expressions differently from earlier versions:
- Values too large for the precision. A cast to DT_NUMERIC whose value has more whole digits than the declared precision minus the scale allows now reports a truncation, such as
Expression with value 12.345 is truncated by (DT_NUMERIC,3,2). In a Biml build, the truncation is a build error. Earlier versions evaluated such a cast to a value without reporting anything. - Scale. A cast to DT_NUMERIC treats its scale as the number of digits after the decimal point, and truncates the value to that number of digits without rounding. A DT_NUMERIC cast of a value with more than one whole digit can also evaluate differently, because earlier versions cut the value one digit shorter for each whole digit beyond the first.
- String variables. A String variable whose expression is a cast to DT_NUMERIC or DT_DECIMAL now holds the value at the declared scale, up to the 28 fraction digits that a .NET decimal holds. A declared scale above 28 prints 28 fraction digits.
- Decimal separator. The text that the build writes for a DT_NUMERIC, DT_DECIMAL or DT_CY value, either in a variable value or through a cast to DT_WSTR, DT_STR, DT_TEXT or DT_NTEXT, now always uses a period as the decimal separator, regardless of the regional settings of the build machine.
- Arithmetic. The result of arithmetic on these casts can show a different number of fraction digits.
- Text length. The length of the text changes in a cast to DT_WSTR. Text cut to the declared scale can now fit a length that was too short for the old text. Text padded to the declared scale can now exceed a length that the old text fit, and the cast then reports a truncation.
| Expression | BimlStudio 2027 | Earlier versions |
|---|---|---|
(DT_NUMERIC,3,2)12.345 | Reports a truncation, which is a build error in a Biml build | A value, with no report |
(DT_NUMERIC,10,2)12.345 | 12.34 | 12.3 |
(DT_NUMERIC,10,2)12.3456789 in a String variable | 12.34 | 12.3000000, or 12,3000000 on a machine with a comma decimal separator |
(DT_NUMERIC,10,0)12345 in a String variable | 12345 | 10000 |
(DT_WSTR,30)(DT_NUMERIC,38,28)12.3 | Reports a truncation | No truncation |
Subversion
This section applies to you if you use Subversion or TortoiseSVN as the source control provider in BimlStudio.
BimlStudio 2027 removes the Subversion and TortoiseSVN source control providers. The Git and Team Foundation Server providers remain.