I started with this but don't think this is the best way to do it.
What do you need to do with these selected values once they’ve been selected?
they need to be searchable so I can search for i.e.: Which clients do I still need to “Schedule an Interview”
EB-3 Immigration Project Specialist
148 River St., Ste. 202
Greenville, SC 29601
Create a Stage table with these categories. Create a second table that is a child table to your Client table (actually, a join table between Client and Stage, so it needs foreign keys for both these other tables).
When creating a new Client record, import all records from Stage into the ClientStage table (just their ID into the foreign StageID field) and give them the ClientID as a second foreign key. If you add a numerical sorter field in both tables (which you'd also import), you can have them displayed in a desired order different from alphabetical.
Now you can set the status of each stage for each client, and search across ClientStages by Client, Stage, date, status … e.g. find all ClientStage records of type “Schedule Interview” with a status of “not done” …
Oh, the joys of join tables.
Using the existing check box field, you can find all records where a given check box is not selected by doing this:
Enter Find mode
Click that check box
Click the "omit" button at the top of the screen
Perform the find.
This find says: "don't show me any records with that value".
There can be very good reasons to set up a related table of records for the selected values, but this simple find alone doesn't seem like a reason to do so.
But if you want to do that, you can actually set up an interface where you can click what look and behave like check boxes, but the buttons that you are actually clicking create/delete records in a related table. No script to import records is needed to set this up. If interested, see:
Check boxes with scroll bars II in:
Adventures in FileMaking #2-enhanced value selection
I have similar needs for several clients. I will have a 'TaskMaster' table with the TEXT (task), NUMBER (sort_order) - for sorting and prioritizing. This is a place to create the Tasks. This might even have tasks that have a "parent", such as 'Projects' because there may be different tasks based on the Project/project type.
Then I use a method to copy over the needed task(s), & sort order value(s). This can be the import already suggested. Or I may use other means to push "multiple values" to the table where these tasks will be assigned and verified. The actual values are copied over and not merely a relationship to see the task, as I've worked with many variations on this and the "historical" nature of the named task value must be there each time. YMMV, of course. Only you know your needs - I speak from decades of my experience.
So a new table 'client_tasks' would get these multiple values and loop script to create records. Include fields such as clientID_fk, dateCreated, dateDue (perhaps), completed (NUMBER for 1 or 0), dateTimeCompleted (perhaps), and any other fields as desired. The 'completed' field is a checkbox control style with a value list of "one" (1).
As the checkbox is checked on the task, it would trigger the dateCompleted and other possible informational fields. Allowing this to be "unchecked" needs business rules (to be decided) of how it affects other processes.
sort by the "checked"
filter a portal to show: "all", "checked", or "unchecked"
summarize/count the checked/unchecked
report on particular task(s)
allowing a task to be "historical" also allows reporting of types of tasks required as the database evolves.
use conditional formatting using the 'completed' and maybe the comparison of dueDate (if any).
thank you Beverly so much for your response. I am a self-taught Filemaker user who has no programming experience so if you can dumb down your suggestion that would be great. LOL
While I understand a little of what you wrote, a lot of it is Chinese to me.
If you don’t want to take the time, I totally understand! Maybe if you could point me in the direction of some literature that would explain what you are suggesting.
Again, thanks so much!!
Yes, sorry, getting "generic" is not always effective. You've not posted any of your relevant table/field/relationship/layout design that you already have. These tend to help make answers more easily understood if your terms are used in the answers.
Did you look at the example in the file that I recommended?
The examples in that file come with detailed documentation on how they work.
not yet but I will. Thanks for your input!!
right now I’m just playing around with one that I made a little while ago to see if I can modify it to suit this need without a lot of invention of new solution. I was hoping I could use the TASK layout that I used somehow:
No worries! Work on it and come back when you need!
Retrieving data ...