---
id: video/KkOr-hX0frQ
type: video
title: How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview
summary: Business Central version 29 (preview) lets you change an existing table field from integer to BigInteger without it being treated as a destructive change, provided the extension targets runtime 18.0 or later. The demo shows the change failing as destructive on version 28 and deploying on version 29 with the data and related records kept. In the preview, the expected narrowing and table relation warnings did not appear yet.
tier: community
language: en
tags:
  - big integer migration
  - integer overflow
  - field type change
  - schema synchronization
  - code cop
  - destructive change
  - table relations
  - data loss prevention
  - al compiler
  - runtime version requirement
  - extension dependency
  - narrowing conversion
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-07T23:19:03.314Z"
  flags: []
generated:
  at: "2026-10-07T23:19:03.367Z"
  pipeline: 0.2.0
  prompts:
    extract-video: 1
    summarize-video: 2
  input_hash: 2920ab876bf3d73bfe3c8f0dfd5ffb7ba0eb8c08c7033358db05479c32dff33f
evidence:
  - kind: video
    url: https://www.youtube.com/watch?v=KkOr-hX0frQ&t=110s
    title: How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview
    date: "2026-09-15T05:53:01.000Z"
    commit: null
    t: 110
    quote: Big integral feed migration is a new compiler and a runtime feature in Business Central version 29
  - kind: video
    url: https://www.youtube.com/watch?v=KkOr-hX0frQ&t=124s
    title: How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview
    date: "2026-09-15T05:53:01.000Z"
    commit: null
    t: 124
    quote: the platform updates the SQL column for you without considering it as a destructive change
  - kind: video
    url: https://www.youtube.com/watch?v=KkOr-hX0frQ&t=204s
    title: How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview
    date: "2026-09-15T05:53:01.000Z"
    commit: null
    t: 204
    quote: They have a custom transaction log table with an entry number field defined as integer. At some point the entry number gets uncomfortably close
  - kind: video
    url: https://www.youtube.com/watch?v=KkOr-hX0frQ&t=614s
    title: How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview
    date: "2026-09-15T05:53:01.000Z"
    commit: null
    t: 614
    quote: But it doesn't give me warning of changing this integer to a big integer which I was expecting that it should give me.
  - kind: video
    url: https://www.youtube.com/watch?v=KkOr-hX0frQ&t=827s
    title: How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview
    date: "2026-09-15T05:53:01.000Z"
    commit: null
    t: 827
    quote: Whereas in version 29 based on the new changes of shifting from integer to big integer it'll easily update it
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
video_id: KkOr-hX0frQ
channel: yt-saurav
source_name: Saurav Dhyani
url: https://www.youtube.com/watch?v=KkOr-hX0frQ
published_at: "2026-09-15T05:53:01.000Z"
duration_s: 1413
captions: derived
audience:
  - developer
  - administrator
  - functional consultant
chapters:
  - t: 0
    title: Introduction and Problem Statement
  - t: 97
    title: Big Integer Field Migration Feature Overview
  - t: 184
    title: Business Impact and Real-World Scenarios
  - t: 262
    title: Technical Architecture and Implementation
  - t: 401
    title: Demo Setup and Table Configuration
  - t: 511
    title: Field Type Change and Code Cop Validation
  - t: 689
    title: Publishing and Version Comparison Setup
  - t: 782
    title: "Deployment Comparison: Version 28 vs Version 29"
  - t: 918
    title: Developer Considerations and Migration Strategy
  - t: 1000
    title: Selective Migration Approach and Best Practices
  - t: 1144
    title: Extension Dependency Validation
  - t: 1230
    title: Common Mistakes and Frequently Asked Questions
  - t: 1328
    title: Summary and Recommendations
features:
  - name: Big Integer Field Migration
    status: unclear
    t: 110
    verified: false
    status_source: video
  - name: AL Compiler Validation for Integer to BigInteger Conversion
    status: unclear
    t: 149
    verified: false
    status_source: video
  - name: App Source Cop Warnings for BigInteger Dependencies
    status: unclear
    t: 163
    verified: false
    status_source: video
  - name: Runtime Schema Synchronization for BigInteger
    status: unclear
    t: 370
    verified: false
    status_source: video
  - name: Compiler Narrowing Conversion Detection
    status: unclear
    t: 1120
    verified: false
    status_source: video
  - name: No Upgrade Codeunit Required for Integer to BigInteger Migration
    status: unclear
    t: 1284
    verified: false
    status_source: video
  - name: Runtime Version 18.0 Requirement for BigInteger Support
    status: unclear
    t: 1080
    verified: false
    status_source: video
  - name: Irreversibility of BigInteger to Integer Conversion
    status: unclear
    t: 1299
    verified: false
    status_source: video
objects_mentioned:
  - table demo table
  - table vendor table
  - table customer table
  - codeunit get next entry function
  - table entry number
quotes:
  - t: 110
    text: Big integral feed migration is a new compiler and a runtime feature in Business Central version 29
    check: exact
  - t: 124
    text: the platform updates the SQL column for you without considering it as a destructive change
    check: exact
  - t: 204
    text: They have a custom transaction log table with an entry number field defined as integer. At some point the entry number gets uncomfortably close
    check: exact
  - t: 614
    text: But it doesn't give me warning of changing this integer to a big integer which I was expecting that it should give me.
    check: exact
  - t: 827
    text: Whereas in version 29 based on the new changes of shifting from integer to big integer it'll easily update it
    check: exact
---

# How to Migrate Business Central Table Fields from Integer to BigInteger | Version 29 Preview

> Business Central version 29 (preview) lets you change an existing table field from integer to BigInteger without it being treated as a destructive change, provided the extension targets runtime 18.0 or later. The demo shows the change failing as destructive on version 28 and deploying on version 29 with the data and related records kept. In the preview, the expected narrowing and table relation warnings did not appear yet.

[Watch on YouTube](https://www.youtube.com/watch?v=KkOr-hX0frQ) · Saurav Dhyani · 2026-09-15 · 23:33 · tier community · reviewed (checked by Opus)

## Overview

The video explains a new compiler and runtime feature in Business Central version 29 that lets developers change an existing table field from integer to BigInteger. The platform updates the SQL column from int to bigint without data loss and without flagging a destructive change. The motivating case is a high-volume custom transaction log table whose entry number field is getting close to the integer limit.

The demo changes a field type, shows the code cop validation, and deploys the same change to version 28 and version 29 for comparison. Version 28 fails with a destructive change error, while version 29 deploys and keeps the data. The presenter also covers selective migration, extension dependencies, and common mistakes. Several compiler warnings, for table relations, related fields and calc formulas, were not yet present in the preview at the time of recording (15 September 2026).

## Key points

- The integer to BigInteger change requires the extension to target runtime 18.0 or later; extensions on a lower runtime must update it first.
- No upgrade codeunit is needed: the platform converts the SQL column and handles the data and related records.
- In the demo, version 28 rejects the change as destructive, while version 29 deploys it as is and keeps the data.
- Per the presenter, the compiler and AppSource cops (rule AS0141) are meant to warn when a BigInteger value may be narrowed or overflow; assigning a value above the integer range to an integer causes a runtime overflow.
- In the preview, no warnings appeared for the field change, table relations, related fields or calc formulas, and the presenter hopes they arrive by GA. Table relations pointing to integer fields need manual updating.
- Going back from BigInteger to integer is destructive: move data to another table, empty the table, then move the data back.
- Migrate only fields that need 64-bit capacity, and start listing high-volume tables that may need it for your roadmap.

## Chapters

- [0:00](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=0s) Introduction and Problem Statement
- [1:37](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=97s) Big Integer Field Migration Feature Overview
- [3:04](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=184s) Business Impact and Real-World Scenarios
- [4:22](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=262s) Technical Architecture and Implementation
- [6:41](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=401s) Demo Setup and Table Configuration
- [8:31](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=511s) Field Type Change and Code Cop Validation
- [11:29](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=689s) Publishing and Version Comparison Setup
- [13:02](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=782s) Deployment Comparison: Version 28 vs Version 29
- [15:18](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=918s) Developer Considerations and Migration Strategy
- [16:40](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1000s) Selective Migration Approach and Best Practices
- [19:04](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1144s) Extension Dependency Validation
- [20:30](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1230s) Common Mistakes and Frequently Asked Questions
- [22:08](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1328s) Summary and Recommendations

## Features

| Feature | Status | At |
|---|---|---|
| Big Integer Field Migration | status not stated, demoed | [1:50](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=110s) |
| AL Compiler Validation for Integer to BigInteger Conversion | status not stated, demoed | [2:29](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=149s) |
| App Source Cop Warnings for BigInteger Dependencies | status not stated, demoed | [2:43](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=163s) |
| Runtime Schema Synchronization for BigInteger | status not stated, demoed | [6:10](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=370s) |
| Compiler Narrowing Conversion Detection | status not stated | [18:40](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1120s) |
| No Upgrade Codeunit Required for Integer to BigInteger Migration | status not stated | [21:24](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1284s) |
| Runtime Version 18.0 Requirement for BigInteger Support | status not stated, demoed | [18:00](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1080s) |
| Irreversibility of BigInteger to Integer Conversion | status not stated | [21:39](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1299s) |

## AL objects mentioned

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

- table "demo table" at [6:58](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=418s)
- table "vendor table" at [7:43](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=463s)
- table "customer table" at [10:49](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=649s)
- codeunit "get next entry function" at [8:58](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=538s)
- table "entry number" at [14:08](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=848s)

Not found in BC28-30: table "demo table", table "vendor table", table "customer table", codeunit "get next entry function", table "entry number".

## Quotes

- [1:50](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=110s) "Big integral feed migration is a new compiler and a runtime feature in Business Central version 29"
- [2:04](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=124s) "the platform updates the SQL column for you without considering it as a destructive change"
- [3:24](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=204s) "They have a custom transaction log table with an entry number field defined as integer. At some point the entry number gets uncomfortably close"
- [10:14](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=614s) "But it doesn't give me warning of changing this integer to a big integer which I was expecting that it should give me."
- [13:47](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=827s) "Whereas in version 29 based on the new changes of shifting from integer to big integer it'll easily update it"

## Disclaimers in the video

- [0:13](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=13s) preview: this is a big change. I'm going to take a good amount of time for it
- [9:12](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=552s) preview: as per the documentation the code cop is only available for app source app
- [10:34](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=634s) preview: there is a table relation to an integer with a big integer. So there should be a warning and I'm ...
- [16:06](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=966s) coming-later: hopefully when the version 29GA is announced next month this will be this will be fixed
- [17:17](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1037s) preview: I'm pretty sure not in the I haven't seen it in the preview release but hopefully in some cumulative update Microsoft may change
- [18:40](https://www.youtube.com/watch?v=KkOr-hX0frQ&t=1120s) coming-later: As the GA will announce, I'm hoping the compiler warnings will be there

Presenters (as heard): Unknown presenter.