Limit of total fields [100000] has been exceeded

Description

Steps

To resolve this issue and successfully sync your content, follow these steps:
 

1. Reduce Field Mappings:

   • Add the attribute [GraphProperty(PropertyIndexingMode.OutputOnly)] or set the indexing type via the Conventions API on properties not needed in searches/filters. This reduces the number of mappings for each field, helping to stay within the limit.
     
     Attribute Method
     https://docs.developers.optimizely.com/content-management-system/docs/install-and-configure-optimizely-graph-on-your-site#outputonly-mode
     
     Example:
     [GraphProperty(PropertyIndexingMode.OutputOnly)] public virtual string AStringProperty { get; set; }
     
     Conventions API method

     https://docs.developers.optimizely.com/content-management-system/docs/conventions-api#set-indexing-type-for-fields
     
     Example:
     conventionRepo.ForInstancesOf () .Set(page = page.Keywords, IndexingType.Searchable) .Set(page = page.Price, IndexingType.Queryable) .Set(page = page.Quantity, IndexingType.OnlyStored);

     
      

2. Adjust Content Expansion Depth:

   • Consider reducing the depth of content expansion. For instance, if the current depth is set to 3, lowering it to 2 can significantly decrease the number of mappings required.
     https://docs.developers.optimizely.com/content-management-system/docs/install-and-configure-optimizely-graph-on-your-site#disable-inlining-contents-in-the-expanded-field-of-reference-properties

      

3. Optimize Field Usage:
   • Review the fields being synchronized and identify any that can be consolidated or removed if they are not critical to the operation.

   • Ensure that only essential fields are included in the synchronization process to minimize mapping usage.
     https://docs.developers.optimizely.com/content-management-system/docs/conventions-api#exclude-all-content-types-except-some