Migrate bc2adls from PTE to appsource extension

Key points

• bc2adls is now on AppSource; a migration app moves existing PTE users over without losing data that was already exported
• First upgrade the PTE to 27.47.0 or later and install the AppSource ADLSE app at 27.46.0 or later, then install the migration app
• The migration app copies the ADLSE setup, table, field, timestamp, category, enum translation, deleted record and run tables to the AppSource tables
• Tenant ID, Client ID and Client Secret must be entered again manually in ADLSE Setup after migration
• Check the configuration and test exports, then uninstall the migration app and the old PTE

Quotes

• “This migration app will automatically copy all the data from the PTE tables to the appsource tables.” (Explains the key benefit: data preservation during the migration process without manual intervention)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

• table “ADLSE Setup”
• table “ADLSE Table”
• table “ADLSE Field”
• table “ADLSE Table Last Timestamp”
• table “ADLSE Export Category”
• table “ADLSE Export Category Table”
• table “ADLSE Enum Translation”
• table “ADLSE Enum Translation Lang”
• table “Deleted Tables Not to Sync”
• table “ADLSE Deleted Record”
• table “ADLSE Run”

Not found in BC28-30: table “ADLSE Setup”, table “ADLSE Table”, table “ADLSE Field”, table “ADLSE Table Last Timestamp”, table “ADLSE Export Category”, table “ADLSE Export Category Table”, table “ADLSE Enum Translation”, table “ADLSE Enum Translation Lang”, table “Deleted Tables Not to Sync”, table “ADLSE Deleted Record”, table “ADLSE Run”.

Context

• Features: data export to azure data lake, data export to microsoft fabric, extension migration
• Versions: 27.47.0, 27.46.0

Source: Discover MS BC - Bert Verbeek, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.