3
Related to this discussion : https://github.com/microsoft/AL/issues/6545#issuecomment-803894400
I propose to change the current behaviour of the ObsoleteState or (as @qutreson suggested) gives the hability to opt-in to a new behaviour: when a control is marked as obsolete, then all child control should inherit this state.
It would mean:
- If I mark a page, at the object level, as ObsoleteState = Pending, then all fields, actions, procedures are automatically obsolete.
- If a group/repeater is ObsoleteState = Pending, then all child controls becomes obsolete.
If the child element has its own ObsoleteTag/ObsoleteReason, this one should overload the same property at the parent level.
I propose to change the current behaviour of the ObsoleteState or (as @qutreson suggested) gives the hability to opt-in to a new behaviour: when a control is marked as obsolete, then all child control should inherit this state.
It would mean:
- If I mark a page, at the object level, as ObsoleteState = Pending, then all fields, actions, procedures are automatically obsolete.
- If a group/repeater is ObsoleteState = Pending, then all child controls becomes obsolete.
If the child element has its own ObsoleteTag/ObsoleteReason, this one should overload the same property at the parent level.
STATUS DETAILS
Needs Votes
Comments
See also my answer on GitHub:
If a group inherited the obsolete state to its children, it would mean that we could never extract an action from a group. We would need to copy the action.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Best regards,
Business Central Team