Visio Guy

All of you, who ever had to implement a complex software solution (Visio or other) were certainly concerned to avoid cul-de-sacs resulting from hard-coded values. The obvious way – even if more tedious – is to implement an additional layer, in which you implement one internal – and immutable – set of values and one external – visible to your users – that you can modify with small effort.
For Visio shapes I came up with the following solution, which I wanted to share with you.
The values of the shape data (in lists) need to reference to variable lists. These lists would reside either in the user-defined cells section if the shape is only to be modified by Visio experts, or in the shape data section, if your trust in your users is big enough. (These variable lists can easily be made with text editors or as in the enclosed example with excel.)
One major issue in this solution was to be able to remote control the shape without destroying its ability to react to users commands. A "SetF/GetRef" command from a user defined cell (user.ID_Ext) to the aimed shape data value (prop.fruit) did the job.
Extending that reflection, I added a shape in which you can switch the language of preference.
I'd enjoy your comments regarding better solutions, as this one blows up the shapesheet if you have more than one variable to handle.

The excel file...