Choose names.
Save the right IDs.

Build and compare

• Back up the latest closed Lesson 2 file.
• ProjectsForContact uses the existing Projects table; match ContactID to ContactID, creation/deletion off.
• Choose Task Project is based on FollowUps; portal shows project names and full IDs as read-only fields.
• Read the core action, then add all eight hidden UI/controller scripts with safeguards.
• Bind Choose project on the task row, Apply inside the project row, Clear project and Cancel below the portal.
• Capture the clicked key before Commit; validate task context and project owner; write only ProjectID.

Try it yourself

1. Work in a disposable copy. Open Task Project Links, Browse mode, List View; Show All. Note the task and contact counts. The supplied file starts with four tasks and no project assignments.
2. On Rivera’s Send meeting summary, click Choose project. Confirm Rivera and that task appear at the top. Expect Website refresh and Autumn workshop, each with its own full ID. Morgan’s separate project must not appear.
3. Click Apply on Rivera’s Website refresh row. The chooser returns to Task Project Links. That task should now display Website refresh. Check its task text, date, status and contact are unchanged; other tasks should remain unassigned.
4. On Morgan’s Send project outline, click Choose project. Expect only Morgan’s Website refresh. Apply it. Both tasks now display the same project name but store different project keys.
5. Open Rivera’s chooser again and click Cancel without applying. The existing assignment must stay. Open it again and click Clear project. The task’s project display becomes blank; the task and both project records remain. Reassign Website refresh for the next lesson.
6. On a disposable copy, create another project with the same name for Rivera using Contact Projects. Reopen Rivera’s chooser: both records should appear with different IDs. Choose deliberately; do not rely on row order. The chooser does not combine equal names.
7. For a task whose contact has no projects, expect an empty chooser and a working Cancel button. Create any test task through your existing contact task-entry screen. Do not create or delete records merely to match a screenshot; keep test additions in a disposable copy.
8. On a disposable copy, enter Choose Task Project directly from the Layout menu, or move to another task while the chooser is open. Apply/Clear should reject an unprepared or changed task. Use Cancel and start again from the intended task’s Choose project button.
9. Check the fields cannot be edited on the chooser, the portal scrolls when needed, and the complete project names, IDs and buttons fit. Check earlier task controls and project entry still work.
10. Save and close, then reopen. Confirm Rivera’s and Morgan’s tasks still show their intended projects, with original counts except deliberate test additions. Keep this saved working file.

Explain what you learned

How do ProjectsForContact and ProjectsForTask answer different questions?

Why can two Website refresh choices remain separate records?

Why capture the selected key before Commit, and why is Cancel not an undo after a failed save?

Your notes and questions