This part lets managers keep each job title's plan up to date: add a competency, change its level or remove it, from one Competency screen. Every change applies to everyone with that job title, so the screen says so, checks for duplicates, asks before removing, and tells reviewers when a plan changed under a response.
Adding an item and editing one need almost the same screen. Instead of building two, build one and open it in two ways: with the item's ID to edit it, or with a blank ID to add a new one. Each formula that differs asks one question, IsBlank(locCompetencyId).
Some actions deserve a second thought, such as removing something many people use. Instead of acting at once, the button asks a question on the same screen, with Yes and Cancel below it. Nothing happens until Yes, and screen readers announce the question.
A screen reader reads where the user is. When an action makes a message appear somewhere else, its users don't hear about it. A live region fixes that: screen readers announce whenever its text changes. In Power Apps, a classic Label becomes a live region with its Live property.
A soft delete hides an item instead of deleting it. A Yes/No column, such as IsActive, says whether the item is in use. "Removing" sets it to No, and every list in the app shows only items where it's Yes. The item stays in SharePoint with its history, and it can come back.
To stop people from adding the same item twice, look for it before you save. If a matching item exists, show a message and don't save. On SharePoint, the lookup can run in the list itself, as long as it compares columns with =.
With gives a value a name for the length of one formula. Calculate it once at the top, then use the name as often as you need below. When the formula ends, the name is gone, so nothing is left behind on the screen.
The modern Combo box lists options for people to pick from. It allows several choices and a search box by default, so for a short list where one answer is right, turn both off. Then read the answer from Selected.
A SharePoint Choice column already knows its options. Choices gives them to your app as a table with one column, Value. Use it as a combo box's Items, and the app lists exactly the options defined in SharePoint, with nothing typed twice.
When a new screen looks like one you already have, duplicate it instead of building it again. Duplicate screen copies the screen with all its controls and formulas, and adds _1 to every name. Then you rename the copy and change what's different, starting with anything other screens send to the original.
