---
id: post/aardvarklabs-blog/3267
type: post
title: Overcoming Integer Limits in Business Central with BigInteger
summary: Business Central's integer data type maxes out at 2.1 billion records, a limit some implementations have hit. AL Version 18 (Business Central 2026 Wave 1) now supports migrating integer fields to BigInteger, which extends the range to 9.2 quintillion values, with compiler warnings to prevent overflow issues.
tier: community
language: en
tags:
  - integer limits
  - biginteger
  - data types
  - field migration
  - compiler support
  - performance
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:55:16.612Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: c4a6ff564048b3a1ac235aa28aee548aea458de422bc59ebe886df714f6bb7ae
evidence:
  - kind: blog
    url: https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/
    title: Overcoming Integer Limits in Business Central with BigInteger
    date: "2026-05-08"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/
    title: Overcoming Integer Limits in Business Central with BigInteger
    date: "2026-05-08"
    commit: null
    t: null
    quote: Changing an existing table field from Integer to BigInteger is now supported when targeting runtime version 18.0 (Fall 2026) or later.
  - kind: blog
    url: https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/
    title: Overcoming Integer Limits in Business Central with BigInteger
    date: "2026-05-08"
    commit: null
    t: null
    quote: The compiler now supports gradual migration between Integer and BigInteger field types.
  - kind: blog
    url: https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/
    title: Overcoming Integer Limits in Business Central with BigInteger
    date: "2026-05-08"
    commit: null
    t: null
    quote: Many Business Central implementation have hit that limit.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "3267"
source_id: aardvarklabs-blog
source_name: Aardvark Labs
url: https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/
published_at: "2026-05-08T12:00:00.000Z"
author: Marcel Chabot
full_text: false
words: 451
quotes:
  - text: Changing an existing table field from Integer to BigInteger is now supported when targeting runtime version 18.0 (Fall 2026) or later.
    why_it_matters: This is the key enabler for solving the 2.1 billion record limit that some implementations have already hit.
  - text: The compiler now supports gradual migration between Integer and BigInteger field types.
    why_it_matters: Gradual migration means existing systems can transition without complete rewrites, reducing implementation risk.
  - text: Many Business Central implementation have hit that limit.
    why_it_matters: Confirms that the integer overflow problem is a real issue affecting current customers, not a theoretical concern.
code_objects_mentioned: []
systems:
  - development
  - platform
versions_mentioned:
  - AL Version 18
  - Business Central 2026 Wave 1
  - runtime version 18.0
preview:
  embeddable: true
  frame_url: https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/embed/
  image: https://aardvarklabs.blog/wp-content/uploads/2025/12/lab-notes.png
  image_alt: null
  image_w: 1024
  image_h: 1024
  site_name: Aardvark Labs
  favicon: https://aardvarklabs.blog/wp-content/uploads/2024/04/design-1.png?w=32
  probed_at: "2026-10-07T11:50:40.869Z"
---

# Overcoming Integer Limits in Business Central with BigInteger

[Read the post](https://aardvarklabs.blog/2026/05/08/overcoming-integer-limits-in-business-central-with-biginteger/) · Aardvark Labs (Marcel Chabot) · 2026-05-08 · 451 words · tier community · reviewed (checked by Opus)

> Business Central's integer data type maxes out at 2.1 billion records, a limit some implementations have hit. AL Version 18 (Business Central 2026 Wave 1) now supports migrating integer fields to BigInteger, which extends the range to 9.2 quintillion values, with compiler warnings to prevent overflow issues.

## Key points

- Integer in Business Central AL is a signed 32-bit type limited to about 2.1 billion positive values when used as a row ID
- BigInteger is a signed 64-bit type supporting 9.2 quintillion values, solving the capacity problem for large datasets
- Data type changes from Integer to BigInteger were unsupported until AL Version 18, which now permits gradual migration with new AppSourceCop rule warnings
- The compiler emits warnings for narrowing conversions (BigInteger to Integer) to alert developers about potential overflow risks

## Quotes

- "Changing an existing table field from Integer to BigInteger is now supported when targeting runtime version 18.0 (Fall 2026) or later." (This is the key enabler for solving the 2.1 billion record limit that some implementations have already hit.)
- "The compiler now supports gradual migration between Integer and BigInteger field types." (Gradual migration means existing systems can transition without complete rewrites, reducing implementation risk.)
- "Many Business Central implementation have hit that limit." (Confirms that the integer overflow problem is a real issue affecting current customers, not a theoretical concern.)

## Context

- Features: BigInteger field migration, Integer to BigInteger conversion, AppSourceCop rule AS0141, CalcFormula support for BigInteger, Property context warnings
- Versions: AL Version 18, Business Central 2026 Wave 1, runtime version 18.0

Source: Aardvark Labs, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.