When creating a new column in an existing table it would be nice to have a task to copy the right from an already existing column to the new column. This would save time in settings all the rights for new columns which are similar to existing columns.I use columns as an example, but this could be equally useful for prefilters, tasks, task parameters, etc..
Our team is currently investigating adding our manual data conversion scripts to the SF instead of managing them manually and running a bunch of scripts before and after the 020-upgrade script.We ran into a small issue, the current option for adding manual data conversion including from version x to y or always don't exactly suffice. We are looking for a smart option in between those two, which works similarly to a smart upgrade of tables, control procedures or tasks. An example of the problem, I have version 1.1, 1.2 and 1.3 of a project. If I add a manual conversion script to the 1.2 using the ‘always’ option, this script is generated into any upgrade following the 1.2 upgrades. For example 1.1 → 1.2, 1.1 → 1.3 but also 1.3 → 1.4. And that one we find less desirable.If we chose the second manual data conversion option, x to y, and add the script to the 1.2 version we have to specify which specific version the code is generated from (the x). Most logical would be to specify this manua
https://codingsight.com/passing-data-table-as-parameter-to-stored-procedures/To pass large amounts of data to a performance sensitive stored procedures we would like to pass a table as a parameter to a stored procedure as described in the article above.For this we need to define a type/domain as a table, and we need to set the parameter of a stored procedure to read only. Those are both options currently not available to us in the SF.Could this be made possible please? The idea is described in the attached link.
https://codingsight.com/passing-data-table-as-parameter-to-stored-procedures/To pass large amounts of data to a performance sensitive stored procedures we would like to pass a table as a parameter to a stored procedure as described in the article above.For this we need to define a type/domain as a table, and we need to set the parameter of a stored procedure to read only. Those are both options currently not available to us in the SF.Could this be made possible please?We are currently using the 2020.2 version of the SF.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
