What to consider before using multiple property sets
Access and authorization
Define which user groups can access each property set. Do not assume that introducing property sets removes the need for authorization design. Some areas may still require authorization filters, and user groups may need to be created or maintained for each property set.
Integrations
All inbound and outbound integrations must identify the correct property set. Include a property-set identifier in interface messages and validate it before processing an update. Incorrect or missing identification can route a transaction to the wrong data domain or update the wrong record.
Codes and numbering
Decide whether object codes and sequence numbers must be unique throughout the environment or only within an individual property set. System-wide unique codes are the preferred default because they reduce ambiguity and the risk of duplicate business keys. Use property-set-specific numbering only when there is a clear business requirement.
Configuration management
Plan for repeated setup and maintenance. Reports, web configurations, mobile applications, Enterprise Talk components, Service desk configurations, and other elements may need to be deployed separately for every property set. A template-based deployment process can help keep these configurations consistent.
Reporting and analytics
Determine whether managers need consolidated reporting across entities. Separation can make cross-property-set reports and dashboards more complex. For exports and analytics, include the property-set identifier so that records remain traceable to the correct data domain.
Cross-property-set processes
Verify whether processes require references to data in another property set. Some condition filters that reference other records do not work across property sets and may require workaround logic.
Performance and scheduling
Coordinate scheduled tasks across property sets. Avoid running multiple resource-intensive batch processes simultaneously, and assign central ownership for the schedule where possible.
Lifecycle management
Deleting a property set can take considerable time because the operation can include many properties and linked records. Treat the creation and removal of property sets as controlled architectural changes rather than routine data maintenance.