Tweet
Hi,
Previously we had requested for lookup database tables as alternatives to enums but things may be difficult considering major needs to be addressed. It is acceptable and we will wait.
In consideration, it would be great if we can have the ability to duplicate an entity field. We surely need this as we tend to define multiple fields with the same enum values, conditions etc. Example:
(1) We have a field call "User Roles for Billing" and has an enum defining the roles (like "admin, editor" etc).
(2) Then we define other similar fields for other "roles" with the same enum values.
If the above is needed for just 2, we could do a manual job. But when the more than 2, it becomes cumbersome and prone to errors in the enum values as frequently get batch job crashes due typo errors in the enum values.
Appreciate the developer's considerations.
Previously we had requested for lookup database tables as alternatives to enums but things may be difficult considering major needs to be addressed. It is acceptable and we will wait.
In consideration, it would be great if we can have the ability to duplicate an entity field. We surely need this as we tend to define multiple fields with the same enum values, conditions etc. Example:
(1) We have a field call "User Roles for Billing" and has an enum defining the roles (like "admin, editor" etc).
(2) Then we define other similar fields for other "roles" with the same enum values.
If the above is needed for just 2, we could do a manual job. But when the more than 2, it becomes cumbersome and prone to errors in the enum values as frequently get batch job crashes due typo errors in the enum values.
Appreciate the developer's considerations.
Comment