Howdy all:

I'm working on a nabbed a Dwindling Value List example file off the 'net and in the JOB layout, I can't see why the List_SelectedPeople__lxt field doesn't update after deleting its corresponding record from the portal. (A script trigger fires when deleting a record from the portal that (should) delete the corresponding ID in the aforementioned field.) 

What happens is, when you click on the "<-Click Me ->" pop-up menu, a value list of names appears, you click a name, it commits, then dwindes the list. That part works fine. The problem is, if you click the Delete link in a portal record, it'll dutifully delete the portal record (with its id_People value) but it won't delete it from List_SelectedPeople__lxt field--with the "deleted" ID still in that field, that ID (person) can't be chosen again from the "<- Click Me ->" list...it's only after I manually delete the id_People's ID from List-SelectedPeople__lxt, or if I choose a new name from <- Click Me ->", that the latent id_People value disappears.

I tried tweaking the Set Selected People script by using the Substitute command (with a stored Global Variable of the id_People ID) to null the value in List_SelectedPeople__lxt, but that didn't work, so what would be a fix to address the problem?

 

Cheers,

Rich 

 

Dwindling.fmp12

I took a peek at your file.

Here's my dilemma: should I try and hunt down where it breaks, or should I advise you to follow a better example? Just for starters, I see no reason why the List_SelectedPeople field shouldn't be an unstored calculation. 

 

I'm for a better example, thanks. : )

See how this one works for you.

A couple of points worth mentioning:

• There is a script trigger attached to the PersonID field in the portal;
• The cAssignedPersonIDs calculation field is set to evaluate always;
• In your file the value list is defined to show only the names. This is possible only if you know that the names are unique.

 

DwindlingVL.fmp12

Beauty! Thanks!