IncidentAnalytix supports two complementary ways to classify incidents. This design provides both standardized reporting and customer flexibility.
IA Type of Incident (Standard Classification)
IA Type of Incident is a standardized, multi‑select classification provided by IncidentAnalytix.
Examples include:
- Injury
- Illness
- Behavioral Issue
- Near Miss
- Property Damage
Purpose
This field is used for:
- Consistent analytics and reporting
- Regulatory and compliance scenarios
- Cross‑organizational comparisons
- Product features that rely on standardized incident semantics
Key Characteristics
- Multiple values can be selected for a single incident
- Values are managed by IncidentAnalytix
- Values cannot be modified or deleted by customers
This ensures reporting consistency and allows IA to safely deliver enhancements and upgrades.
Incident Type Lookup Table (Customer‑Defined)
Incident Type Lookup is an optional, customer‑managed lookup field that allows organizations to apply their own internal classification.
Examples might include:
- Department‑specific categories
- Program‑specific labels
- Organization‑specific terminology
Purpose
This field is intended for:
- Customer‑specific categorization
- Internal reporting needs
- Alignment with existing organizational taxonomies
Key Characteristics
- Fully customer‑managed (add, rename, retire values)
- One category per incident
- Not used by IA for core analytics or compliance logic
How the Two Fields Work Together
These fields are designed to be complementary, not redundant:
| Field | Role |
|---|---|
| Type of Incident | Standardized classification used by IncidentAnalytix |
| Customer Incident Type Lookup | Optional customer-defined primary category |
An incident may be tagged with multiple IA Type of Incident while also having one customer-defined type.
Why This Design Matters
This approach allows IncidentAnalytix to:
- Maintain consistent semantics across all customers
- Deliver safe upgrades without breaking customer customizations
- Provide reliable analytics and reporting
At the same time, it allows customers to:
- Use their own terminology
- Align IA with internal processes
- Extend the model without modifying managed components
Advanced Customization
Organizations that require:
- Multiple customer-defined tags per incident
- Hierarchical or domain-specific classification models
may further extend the data model using additional tables or relationships, following standard Power Platform customization practices.
Summary
- Use IA Type of Incident for standardized classification and reporting
- Use Customer Incident Type Lookup Table for organization-specific labeling