@add_button_type tinyint output, -- 0 = enabled, 1 = disabled, 2 = hidden.
@update_button_type tinyint output,
@delete_button_type tinyint output,
@confirm_button_type tinyint output,
@cancel_button_type tinyint output,It would be great to have a @copy_button_type.
At this time it seems it is only possible to disable the copy functionality on a whole table under Subjects > Settings > Permissions > Data manipulation.
I'd also like to be able to disable the add button, but keep the import option.
+5What is the use case for this?
At first glance, this seems logical to have, but the impact of adding this to all our layout procedures is rather big. Functionally, I doubt what you can do with this option.
I always thought that if a user could add, he could also manually copy. So why enable add, but disable the copy? Or when you can copy a user, you can also add by changing all the values. So why enable copy, but disable add? But maybe I am missing a case.
+6What is the use case for this?
At first glance, this seems logical to have, but the impact of adding this to all our layout procedures is rather big. Functionally, I doubt what you can do with this option.
I always thought that if a user could add, he could also manually copy. So why enable add, but disable the copy? Or when you can copy a user, you can also add by changing all the values. So why enable copy, but disable add? But maybe I am missing a case.
I understand that a copy is an insertion of a row with the exact same data as the selected row. On a database level, this is essentially the same as performing an insert.
However, we have cases where we don't want to allow copying and only want to permit adding data manually, and other cases where we want to allow copying but not manually add a data.
+23The idea sounds simple but requires changes to every component of the platform thus these ideas need to have solid use cases to be considered for implementation.
+6The idea sounds simple but requires changes to every component of the platform thus these ideas need to have solid use cases to be considered for implementation.
I hope I can explain this in such a way that it is understandable š
One use case we have is as follows:
A user creates an order with order rows. These order rows are added from a list of products where the user has set the quantity higher than 0. This means the order rows are added via a task/process flow and not manually added/filled by the user.
This user may only copy the selected row(s) on the order rows and not create a row manually. However, another user with a different role (order administration) must be able to add rows manually.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
