Option - Select Members On Code





IDEA
Currently in Board the following object use internal member UIDs to memorized the member to use :
- Screen selection
- selection step procedure
- References in Layouts
My idea is to have the options to memorized the code of the member instead.
Ideally it should be an option enable by entities and a default set by database.
Otherwise by database for backward compatibility.
Why:
If you ever have cleared an entity and reload it because bad value where loaded you should know why 🤣
PS: An options seems to have a similar name in the configuration file server_config_v2.xml (onpremise) but I never tested it :
Comments
-
+ 1 on this idea, I seem to remember it was discussed a long time ago.
I agree everybody having to clear entities really knows the value of that option. I know that every structuring selection should be governed by flexible objectifs (like a selection based on cube where you can refresh / update selections) but it is simply not doable for each and every selection everywhere.
It's also a topic when moving procedures from development to production databases : if you had some testing data in dev, your selection will need to be updated manually in production after transport, which is creating usually a lot of trouble in production.
1