Hi,

I don't use the DDT and let SF's standard CRUD processing do the heavy lifting. So, when I change a column in a row and save the change every column in the BO is included in the update irrespective of if they have been changed or not. What I would prefer is for the Update command to only include in the Update the column(s) that have changed. I know I can achieve what I want by adding entries in the ExcludeFromUpdate list or using my own stored proc to do the update but I was hoping there may be a 'magic property' somewhere that can turn this facility on.

Cheers, Peter

Hi Greg, Peter

On the same topic, what would be the advantage of using SP for the CRUD?

Edhy Rijo

I don't know why Peter is wanting to use sprocs, but here are a couple of common reasons:



1. Security. Often DBAs will disallow any access to tables. All access must be via views and sprocs.



2. Complexity. If you need to do additional processing during a CRUD action, then a sproc is a fast server side option. E.g. a complex trigger needs to be executed when a record is added, complex enough that a normal trigger won't do it.



I'll be interested in other reasons...

Thanks Greg,

So unless there is special need, having the CRUD without SP would be acceptable for any application?

Just want to be on the safe side, since I do have the DDT, but the tables where designed using xCase with not SP for CRUDs.

Edhy Rijo