Private fields not to be viewed by public
I'm appreciate if you could consider the above mentioned feature.
-
Mineko commented
A useful feature not only for javascript and calculated fields. Every kind of field should have the hidden/private option.
-
Craig commented
It's a so simple and so nice idea, why was it not taken into consideration?
-
Don Daenatur commented
This is the most frustrating thing for me to not be able to keep calculation fields away from users eyes.
-
MarkII commented
@philo I think that such a useful feature should be active for every library and for every user, not just libraries shared on the cloud and team users. I need that feature as well.
-
philo commented
I's an implemented feature. Just go to [cloud storage] -> [choose a library] -> [add user or group] -> [field permission] -> [choose field] -> [choose invisible].
-
Brad commented
It would be a great enhancement for memento. It would let build semi-professional applications.
-
Samantha Lestofanth commented
Sometimes I create a field definition (such as a Javascript field or a calculation field) that should remain invisible to the user, useful to keep data in complex calculations or to obtain and show data in an aggregated form.
Such a field shouldn't appear in the Library entries list screen, nor in the Entry view card, nor in the Entry edit card. The final user shouldn't see such a field as it contains internal calculations.
So this is the proposal: add the "hidden" or "private" option for the javascript and calculation fields.
-
Masher commented
I have a Contacts database in which I'd like to hide/mask individual entries (marking them as private), which can then be revealed by entering a password. The Contacts database in my Palm had this feature and was most useful.