Skip to main content

Migration Tool — Project Validation

This article describes the objects that cannot be migrated from Jet Analytics 20.10 to Jet Analytics Data Integration. The Migration Tool identifies these objects during the Project Validation step. Some can be skipped and migration can continue; others must be resolved before migration can proceed.

See Migration Tool — Upgrade from Jet Analytics 20.10 to Jet Analytics Data Integration for the full migration procedure.

Project Validation step

If the project contains objects that cannot be migrated and cannot be skipped, the Next button is greyed out and the affected objects are listed as errors. These must be resolved before migration can continue.

If the project contains objects that can be skipped, they are listed as warnings. Selecting the I confirm that the listed items will not be migrated checkbox allows migration to continue without those objects. No manual changes are required for warnings.

Warnings — can be skipped

The following objects cannot be migrated but can be skipped — no action is required before continuing.

SSAS Multidimensional (OLAP) cubes

Note:

SSAS OLAP cubes cannot be migrated. Rebuild the OLAP cubes as Tabular models in Jet Analytics 20.10 first, then migrate the Tabular models.

Data Exports

External SQL connection

TX Financials

Qlik Sense Server

Qlik Model

Errors — must be resolved before migration

The following objects must be manually changed or deleted inJet Analytics 20.10 before migration can proceed.

Time Table

Right-click the time table in the Business Unit or Data Warehouse and select Delete Time Table.

External Business Units

Right-click the external business unit and select Delete External Business Unit.

Project Variables

A project variable of type System with value Environment Name cannot be migrated. For variables of types Source, Destination, and Contextual Scope, only the value Name can be migrated — other values for these types cannot be migrated.

To remove a project variable that cannot be migrated:

  1. Open the Tools menu and select Project Variables.
  2. Select the variable to remove.
  3. Click Delete.

Entire Row Hash Key field

To remove this deprecated setting:

  1. Right-click the table and select Table Settings.
  2. Select the Miscellaneous tab.
  3. Set the Entire row hash key property to Not Used.
  4. Click OK.

Lookup fields using Partition by as SQL mode

To remove this deprecated setting:

  1. Expand the table that contains the lookup field.
  2. Right-click the lookup field and select Edit Lookup Field.
  3. Change the SQL mode setting to Group by.
  4. Click OK.

To locate affected lookup fields in the Jet Analytics 20.10 repository database:

SELECT dw.[Name] AS [Data Warehouse], t.[StagingName] AS [Table], l.[Name] AS [Field] FROM [dbo].[LookupFields] l INNER JOIN [dbo].[ConditionalLookupFields] cf ON l.[ConditionalLookupFieldId] = cf.ConditionalLookupFieldId INNER JOIN [dbo].[DataFields] d ON cf.ConditionalLookupFieldId = d.DataFieldId INNER JOIN [dbo].[DataTables] t ON d.DataTableId = t.DataTableId INNER JOIN [dbo].[SqlServerConnections] s ON t.SqlServerConnectionId = s.SqlServerConnectionId INNER JOIN [dbo].[DataWarehouses] dw ON s.DataWarehouseId = dw.DataWarehouseId INNER JOIN [dbo].[Projects] p ON dw.ProjectId = p.ProjectId WHERE l.SqlMode = 'Partition_by' AND l.[ValidTo] = 99999999 AND cf.[ValidTo] = 99999999 AND d.[ValidTo] = 99999999 AND t.[ValidTo] = 99999999 AND s.[ValidTo] = 99999999 AND dw.[ValidTo] = 99999999 AND p.[ValidTo] = 99999999

Conditional lookups with Force sub select or Use a temporary table

To remove these deprecated settings:

  1. Expand the table and then expand the field that contains the conditional lookup.
  2. Right-click the conditional lookup and select Edit Conditional Lookup.
  3. Deselect the Force sub select checkbox.
  4. Ensure that either Take the first value or Take the first non-empty value is selected for the Multiple lookup fields property.
  5. Click OK.

To locate affected conditional lookups in theJet Analytics 20.10 repository database:

SELECT dw.[Name] AS [Data Warehouse], t.StagingName AS [Table], d.StagingName AS [Field] FROM [dbo].[ConditionalLookupFields] cf INNER JOIN [dbo].[DataFields] d ON cf.ConditionalLookupFieldId = d.DataFieldId INNER JOIN [dbo].[DataTables] t ON d.DataTableId = t.DataTableId INNER JOIN [dbo].[SqlServerConnections] s ON t.SqlServerConnectionId = s.SqlServerConnectionId INNER JOIN [dbo].[DataWarehouses] dw ON s.DataWarehouseId = dw.DataWarehouseId INNER JOIN [dbo].[Projects] p ON dw.ProjectId = p.ProjectId WHERE (cf.[ForceSingleLookup] = 1 OR cf.[MultipleLookupFields] = 'UseTemporaryTable') AND cf.[ValidTo] = 99999999 AND d.[ValidTo] = 99999999 AND t.[ValidTo] = 99999999 AND s.[ValidTo] = 99999999 AND dw.[ValidTo] = 99999999 AND p.[ValidTo] = 99999999

Field mappings with Concatenation or Split data movement methods

To remove a Split:

  1. Right-click the field mapping and select Delete Split.

To remove a Concatenation:

  1. Right-click the field mapping and select Delete Concatenation.

After removing the Split or Concatenation, remap the field by dragging it from the source table to the destination field. Ensure the data movement method for the new mapping is set to Copy.

To locate fields using the Split data movement method:

SELECT t.[Name] AS [TableName], d.[Name] AS [FieldName] FROM [dbo].[FieldSplits] f INNER JOIN [dbo].[DataFields] d ON d.[DataFieldId] = f.[SourceDataField] INNER JOIN [dbo].[DataTables] t ON t.[DataTableId] = d.[DataTableId] WHERE f.[ValidTo] = 99999999

To locate fields using the Concatenation data movement method:

SELECT t.[Name] AS [TableName], d.[Name] AS [FieldName] FROM [dbo].[FieldConcatenations] f INNER JOIN [dbo].[DataFields] d ON d.[DataFieldId] = f.[DestinationFieldId] INNER JOIN [dbo].[DataTables] t ON t.[DataTableId] = d.[DataTableId] WHERE f.[ValidTo] = 99999999

Mapping tables

  1. Expand the relevant Business Unit and then expand the Data Mapping node.
  2. Right-click the mapping table and select Delete Mapping Table.
  3. Click OK.

Target-based incremental load

  1. Right-click the table and select Table Settings.
  2. Select the Data extraction tab.
  3. Deselect Enable target-based incremental load.
  4. Click OK.

BK Hash Key

  1. Right-click the table and select Table Settings.
  2. Select the Performance tab.
  3. Deselect Enable BK hash key.
  4. Click OK.

To locate tables with BK Hash Key enabled in the Jet Analytics 20.10 repository database:

SELECT dw.[Name] AS [Data Warehouse], t.StagingName AS [Table], d.StagingName AS [Field] FROM [dbo].[DataFields] d INNER JOIN [dbo].[DataTables] t ON d.DataTableId = t.DataTableId INNER JOIN [dbo].[SqlServerConnections] s ON t.SqlServerConnectionId = s.SqlServerConnectionId INNER JOIN [dbo].[DataWarehouses] dw ON s.DataWarehouseId = dw.DataWarehouseId INNER JOIN [dbo].[Projects] p ON dw.ProjectId = p.ProjectId WHERE d.[OrigName] = 'BK Hash Key' AND d.[ValidTo] = 99999999 AND t.[ValidTo] = 99999999 AND s.[ValidTo] = 99999999 AND dw.[ValidTo] = 99999999 AND p.[ValidTo] = 99999999

Data Aggregations

Right-click the data aggregations object and select Delete Data Aggregations.

To locate tables with data aggregations in the Jet Analytics 20.10 repository database:

SELECT dw.[Name] AS [Data Warehouse], t.StagingName AS [Table], d.StagingName AS [Field] FROM [dbo].[DataFields] d INNER JOIN [dbo].[DataTables] t ON d.DataTableId = t.DataTableId INNER JOIN [dbo].[SqlServerConnections] s ON t.SqlServerConnectionId = s.SqlServerConnectionId INNER JOIN [dbo].[DataWarehouses] dw ON s.DataWarehouseId = dw.DataWarehouseId INNER JOIN [dbo].[Projects] p ON dw.ProjectId = p.ProjectId WHERE d.[FieldAggregationType] <> 'None' AND d.[SubTypeName] IS NULL AND d.[ValidTo] = 99999999 AND t.[ValidTo] = 99999999 AND s.[ValidTo] = 99999999 AND dw.[ValidTo] = 99999999 AND p.[ValidTo] = 99999999

Navision data source (versions 2.6–4.0)

This legacy data source type must be replaced before migration can proceed:

  1. Right-click the data source and select Remove Data Source.

  2. Expand Adapter Data Sources, right-click Data sources, and select Add Dynamics Business Central (NAV) Adapter to create a replacement data source.

    Contact Product Support for setup instructions.

  3. Once the new data source is configured, remap the Data Warehouse tables that were mapped to the deleted data source so they point to the new data source.

Was this article helpful?

We're sorry to hear that.