Release Date: February 2, 2021.
In this release, we are rolling out limits on the creation of the following entities in phases.
- Custom fields
- Store entities
- Product attributes
- Payment mode attributes
- Sharingan apps
- Behavioral events and
- oAuth API clients
List of such entities, their default limits and release timelines can be found below.
The following table provides a detailed cap for each entity.
|Custom fields||Loyalty registration custom fields||30|
|Loyalty transaction custom fields||30|
|Store custom fields||30|
|Product data model||Product categories||50|
|Payment modes||Payment mode attributes||10|
|Sharingan apps||Active Sharingan apps||100|
|Behavioral events||Behavioral events||20|
|Behavioral events for Loyalty+ Destination||10|
|Attributes in a Behavioral event||20|
|Store data model||Stores||500|
|Tills per store||20|
|Zones per org||30|
|Concepts per org||30|
|OAuth API client||API clients||15|
If agreed that an Org is not paying based on the usage, the updated pricing would be decided by CSM/Sales PoCs. The business teams collaborate with the Org to suggest subsequent actions.
When the limit is exceeded, the imported record numbers' limitation will not allow any data ingestion. However, the limit on record imports is already fixed and can be increased if required. Using this feature, it is possible to set the limit on records at the Org level.
For specific brands that require higher import limits, such as CP All, the limit can be increased so that the FTP import gets executed without interruption.
|Currently, CP All is considered as an exception.|