>> Problem is theres never any situation in which we need to change or to some calculation inside the loop of the view,
That doesn't sound like a problem. Clearly I'm not going to remove the embed points just because _you_ don't find them useful? So I'm not sure what you are asking me to do there
>> If its possible, it will be very useful to add the template the feature to save the view values in the session (when selected) to be used in the server side code.
If you need to set additional values aftr a Drop item is selected, then the correct place to embed the code is in validate::somefield routine
The following code should be sufficient;
This has nothing to do with additional View fields. And you should not use Additional View fields for this purpose. I recommend you don't add to the Additional View Fields unless you want to use the field in an expression, or embed point, as discussed earlier.
this might become a template option in NT14, but I'm not adding things to NT12 at this point.