Remove deactivated or disabled customizations
Category: Maintainability, Supportability
Impact potential: Low
Symptoms
Deactivated or disabled customizations should be removed from a solution to improve solution management and to decrease the risk of utilizing or managing an outdated component.
Guidance
Ensure that each solution component that is deactivated, or disabled, has been done so intentionally. If so and will no longer be utilized, consider removing it from the solution to prevent confusion for users and system customizers. These components include:
- SDK Message Processing Steps
- Processes
- Record Creation and Update Rules
- SLAs
As well as table components such as:
- Forms
- Views
- Business Rules
See also
Apply custom business logic with business rules and flows in model-driven apps
Events in forms and grids in model-driven apps
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應