Partitioning Data by User and Device Identity Guidelines

Follow these guidelines when configuring MBOs that partition MBO data by a requester's identity for client defined partitions.

Guidelines for Defining an MBO That Partitions Data by User Identity
Guideline Description
Setting Partition by Requester and Device Identity You can select this option when defining a new cache group or modifying the properties of an existing cache group. The default value is unselected.
Relationship If an MBO references a user-partitioned MBO then both MBOs must be user-partitioned. User-partitioned MBOs can reference non-user-partitioned MBOs. For example, there are three MBOS:
  • SalesOrderMBO
  • LineItemMBO
  • ProductMBO
The LineItemMBO has a foreign key reference to the SalesOrderMBO and a foreign key reference to the ProductMBO.

In this case the modeler/developer specifies the SalesOrderMBO is requestor-partitioned, meaning that the LineItemMBO must also be requestor-partitioned (since it contains a foreign key reference to another requestor-partitioned MBO).

The modeler does not specify the ProductMBO as requestor-partitioned since doing so needlessly duplicates reference data in the cache.

Cache group The MBO must be in a cache group that uses the On demand policy.
MBO cache affecting operations Any cache affecting operation is localized to the partition of the requester.
Data change notification (DCN) DCN does not support modifying data at the partition level.
Parent topic: Setting Client Defined Data Partitioning by User and Device Identity