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 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기