Script to Edit Specific Value List?

[dmontano]

I know there is a script step that opens the Define Value List dialog. I would like to add a button with a script that would open the specific value list for me so I can start editing the list.

I know the edit option is available in the actual list at the bottom - but I do not want users to be able to edit in this particular field.

[Vaughan]

When setting up the field on the layout, there is an option to allow editing of values (or word to that effect). Select this option and a window opens that allows the values to be changed.

[normanicus]

Yes, it is possible but I do wonder how often one has to say the same thing.

Base your value list on a field in a one record table. Values to be shown should be carriage return separated. You can control who can edit this field with the FM access controls. The list is completely controllable via scripts,

Norman

[dmontano]

Thanks Vaughan - I am aware of that option. I was looking for a way to script the opening of the precise Custom Value that I have already created. I have quite a few of them.

Hi Normanicus,

That is not what I was asking about - so I am not sure what you mean when you wrote: "I do wonder how often one has to say the same thing."

Since you said it is possible, can you explain the script steps involved?

I do not want to create a value list in one table. I am looking for a scripted way to quickly get to the specific Custom Value lists that already exist - there are over a hundred of them.

The routine of editing a custom value list is quite tedious when there are so many value lists AND FileMaker places quite a few dialog windows to get to the actual list and then you have to get all the way back out.

[LaRetta]

I know the edit option is available in the actual list at the bottom - but I do not want users to be able to edit in this particular field.

A hundred custom value lists is a lot. I would do it this way (see attached), placing this one field on a Developer or Admin layout for editing capability. You can then leave the Users to their own copy of the field without edit options.

Another option is to stack each field (one copy of the field with standard VL and other with edit option) and allow entry to field according to privilege set or restricting via script. But it would be much more task intensive. I've used the first option in similar situation and I believe it might fit the bill here. I know, I know ... it's not what you asked for. But sometimes we have to go round-about to get things done. I just thought it might be worth considering.

UPDATE: Don't let the global field throw you; nor the fact that all the value lists are attached to it; nor that you are changing the values within the same field. FM keeps them straight and the field is only for editing.

LaRetta :-)

customEditVL.zip

Edited July 4, 2008 by Guest
Added update - what's new :o)

[LaRetta]

I have again blown it ... I have not asked the right question here. I do not know your perspective or purpose.

There are three levels for value lists (whether custom or via field data): 1) Users who are not allowed to edit or add to the value lists (which should encompass 99% of users because they add garbage to the lists and destroy categorized reporting among other things), 2) Admin Users who can edit/add SOME value lists (they must also be restricted to a degree) and 3) Developers.

But even Admin users (2) should NOT have access to Manage Value Lists. Why? Because there are some value lists (usually) which a Developer must control that are used in navigation, portal filtering, script branching and other such design functions. And even with value lists which Admin SHOULD be able to modify, there needs to be tight controls in place. For instance, if an Admin removes a value from a value list then a business decision must be made on what to do with all the records containing that value! This should all be tightly controlled and FM does not really provide us this control; thus my sample file. But I responded thinking you wanted the solution as a Developer!! I mixed purposes and perspectives and I was wrong to do so without clarity. If the solution is for Admin then my sample file is incomplete because it should contain scripted process which searches for records with a removed value and allows replacement data.

If you are an in-house Developer then my file would allow easy view/modify of all the values but I STILL think opening Modify Value Lists would be simpler if it is just for your use. So without knowing your purpose and perspective all answers provided will fall short in one way or another.

LaRetta

[comment]

FWIW, I kinda liked your idea (though it took me some time to get it, with the fields having white text ??!). I have no need for this but if I did, I'd probably use a repeating calc =

GetValue ( ValueListNames ( Get (FileName) ) ; Get ( CalculationRepetitionNumber ) )

instead of the global, so that each "editor" displays the name of the value list it accesses (note that if you change the order of the value lists, you have to do some layout maintenance too).

But IMHO the real answer is that custom value lists should not require "routine editing". Custom value lists are best used for static lists, such as month names or phone types (e.g. "home/work/cell"). Frequently changed lists should be kept in a table.

[LaRetta]

Hi Michael, I made the text white because it looked confusing to see a flower entry in the fruit 'box' and vice versa. I thought white text (signifying that no entries counted at all) would be less confusing but it looks like I was wrong.

...I'd probably use a repeating calc ... instead of the global, so that each "editor" displays the name of the value list it accesses...

NOW THIS ROCKS!! But I can only make it work if I split the repetitions apart so I can attach different value lists to each repetition. Is this what you mean? But this is so clever ... we can still select 'edit' to change a Custom Value List item on a CALCULATION!! WOW!! I thought I would need a global but we don't! And, as you say, it will display the value list name again when you exit the field. Very very cool and something I will use in probably more ways than I can even visualize right now! I hope everyone understands how cool this idea is!

:yep:

[comment]

I can only make it work if I split the repetitions apart so I can attach different value lists to each repetition. Is this what you mean?

Yes, of course. You need separate instances - otherwise every repetition would access the same value list.

[dmontano]

Hi LaRetta,

Thank you for your input. I will delve into what you have posted.

I am the "developer" (beginner mind you) and my purpose was to speed up the process of getting into the define value list dialog so I could edit the specifications quickly for a specific list. FM does make one jump through a lot of hoops going "in" to edit the specific list - then quite a few "clicks" out. I was hoping a script could take me to the "exact" list and open it so I could start editing.

However, from what Normanicus posted, it got me thinking that there must be some other manner in which "developers" are building value lists that I am not even aware of. So while my original question was perhaps misconstrued - I have obviously accidentally overturned a rock that points to the fact that Value Lists are commonly treated in an entirely different manner than what I have been doing.

Thanks