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 / Finance forum / Table Partition Signif...
Finance forum

Table Partition Significance

(0) ShareShare
ReportReport
Posted on by Pete Alberts 3,542

Hi

I noticed the property Save Data Per Partition in the VS table property pane. I have been ignoring the field on Common. I would like to know what the significance is of this field (and the property) for development.

I have read the following briefly: https://docs.microsoft.com/en-us/dynamicsax-2012/appuser-itpro/data-partitioning-architecture

And I understand Save Data Per Company very well. It seems like Partitions are somewhat in the same direction.

Thanks for your attention.

Categories:
Development / Customization / SDK
I have the same question (0)
  • Verified answer
    Satish Panwar Profile Picture
    Satish Panwar 14,671 Moderator on at

    Hi Pete,

    Data Partition was deprecated with AX7.0 and later on. Instead of data partition, MS suggest to use different instances of F&O. Refer link below.

    docs.microsoft.com/.../deprecated-features

    Thanks,

    Satish Panwar

    Please help verify answer(s) if they guide you in right direction so other community members can also benefit from your question with verified answer.

  • Pete Alberts Profile Picture
    Pete Alberts 3,542 on at

    Thanks Satish.

    That makes sense as the Partition ListPage's MenuItem is not available on any menu. However, I am still not sure whether it is something I can flat out ignore from a dev side:

    1. The property on the VS Table Editor Properties Pane is relatively new (I'm reasonably sure about it, but the possibility is there that I only started noticing it recently and it has always been there). Anyhow, if MS added the option for me as a developer to change the property, it must surely still do something. Even more so if the option was added recently.
    2. MS still uses the property. Have a look at BIDateGregorian table.
  • Verified answer
    Blue Wang Profile Picture
    Blue Wang Microsoft Employee on at

    Hi Pete,

    In AX 2012 ，If a table has its SaveDataPerPartition property set to Yes, meaning the table has the Partition system field. The system can maintain data from the table in a data cache. Cached data for one partition can never be access from a second partition. However, a cache flush command that is issued in one partition can sometimes flush data for all partitions.

    For AIF, Batch tables – Save data per partition is set to “No”,because those are shared across partitions.

  • Suggested answer
    Satish Panwar Profile Picture
    Satish Panwar 14,671 Moderator on at

    May be MS is planning something around it to handle on their side to start with and may come to DEV later on. Haven't seen any this surfaced up on any recent documentation.

    Thanks,

    Satish Panwar

  • Suggested answer
    Khushhal Garg Profile Picture
    Khushhal Garg 1,514 on at

    Do you have more than one partition in your implementation? If not, then just ignore it since with latest version, it is deprecated anyways. You can have multiple partitions and then separate out companies between partitions. Then to not share data between partitions, this property is applicable.

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 303,730 Super User 2026 Season 1 on at

    Hi Pete,

    You may believe the answers above. It has been deprecated. The best reason is that it was impossible to backup and restore a single partition. Therefor a full data backup/restore is the better approach.

    There is no reason for Microsoft to bring back this feature. Yes, there are differences on this setting across multiple tables, but that is a legacy from the past.

  • Pete Alberts Profile Picture
    Pete Alberts 3,542 on at

    Thank you friends.

    Blue - does that mean that partition's are still there? Meaning Partition management (adding new ones) is deprecated, but the concept still exists? I am aware of the fact that any SQL join will include the Tx.Partition = Ty.Partition which makes me think you are correct.

    Khushhal - 90% of the time I am busy with ISV solutions. So it's not implementation specific.

  • Blue Wang Profile Picture
    Blue Wang Microsoft Employee on at

    Hi Pete,

    Removed as of Dynamics AX 7.0.

    Just like my reply tagged "In AX2012".

    Data partitions were introduced in Microsoft Dynamics AX 2012 R2 to enable data isolation.

  • Pete Alberts Profile Picture
    Pete Alberts 3,542 on at

    Ahhhh - I missed the "In AX2012" part. Thanks for pointing it out again. So that means that the implicit SQL join condition Tx.Partition = Ty.Partition does not do anything and is also a legacy from the past?

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 303,730 Super User 2026 Season 1 on at

    Hi Pete,

    In fact this is indeed legacy, but probably still used in database calls and indexes as well. I haven't checked the latest versions, but initially, the partition field was indeed used in the database storage and indexes. In fact this value is always the same per environment.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Finance

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans