# Partition Field Count Limits (DATE vs CUSTOM) > Source-anchored research for Partition Field Count Limits (DATE vs CUSTOM). Run status: COMPLETED. Parent: [Online Archive partition-field selection](https://llms-explorer.com/tree/online-archive-partition-field-selection/) · 2 facets · 4 facts · page: https://llms-explorer.com/tree/partition-field-count-limits-date-vs-custom/ ## How it works - When creating a DATE archive through the API or Terraform, include criteria.dateField (Terraform date_field) in the partition-field list. It consumes one of the three available slots. (high confidence) (verified as of 2024-11-13) — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13/operation/operation-getgroupclusteronlinearchive) ## Facts and statements - For criteria.type DATE, the documented maximum is three partition fields total, including the required archival date field; at most two other fields can be added. (high confidence) (verified as of 2024-11-13) — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13/operation/operation-getgroupclusteronlinearchive) - For criteria.type CUSTOM, the documented maximum is two partition fields total. The DATE three-field allowance is conditional on DATE criteria, not a general allowance for every archive. (high confidence) (verified as of 2024-11-13) — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13/operation/operation-getgroupclusteronlinearchive) - An Online Archive must have at least one partition field; the documented maxima are not a requirement to populate every available field slot. (high confidence) (verified as of 2024-11-13) — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13/operation/operation-getgroupclusteronlinearchive)