web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / System Sequence table ...
Microsoft Dynamics AX (Archived)

System Sequence table showing only data from "DAT" company only

(0) ShareShare
ReportReport
Posted on by @rp@n 56

Dear All,

Can you please let me know in development environment DAT company. We are creating new legal entity based on customer requirement. I checked in SQL "SystemSequenceTable" it's showing only records from DAT company not all companies.

SystemSeq.png

Other tables are showing data perfectly.

Please give me more shed on this.

Thanks!

Arpan

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    The SystemSequences table stores the state of RecId counters for each table, as well as other global counters like TransactionId.  These counters are not company specific, thus you will only find records in SystemSequences for company DAT.

    In older versions of AX (pre-4.0), the RecId counter was specific to each company.  That was changed in AX 4.0.

    In other words, that is completely normal and nothing to worry about.

  • @rp@n Profile Picture
    @rp@n 56 on at

    Thanks Brandon,

    we are creating a new company "USIP".

    Example : Suppose if I want to know the next  value of RecID in SalesTable. Then how to came to know?

    Please give me more shed on this.

    Thanks!

    Arpan

  • Verified answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    The short answer is that you cannot.

    While you can find the record for a specific table in SYSTEMSEQUENCES using the TABID field, which equals the table number of the table in the AOT), the NEXTVAL may or may not actually reveal the next RECID that will be used by a running AOS.

    Here's why.

    When an AOS inserts a record into a table, it will grab a block of RECID's from the SYSTEMSEQUENCES record for that table, not just 1.  In other words, it will fetch the NEXTVAL, and then advance it by 256, thus reserving for itself a block of RECID's.  Obviously the advantage to this caching is reducing the need to query and/or update the database as RECID's are used for inserts.

    Now if you have a cluster of running AOS servers, as each inserts a record into the table for the first time it fetches its own block of 256 RECID's.  Thus, a record inserted by AOS 1 will have a different RECID than a record inserted by AOS 2 for the same table, and so on with AOS 3, and 4, etc.  

    And, and this is the critical part to understand, NONE of those RECID's assigned by any running AOS machines will be the NEXTVAL on the SYSTEMSEQUENCES record, UNLESS the record being inserted happens to be the first for that table for that AOS (in which case the NEXTVAL is fetched and advanced 256, and the first value in that reserved block is used).

    Hope this helps.

  • @rp@n Profile Picture
    @rp@n 56 on at

    Thanks Sukrut

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans