Some fields are valid to supply when inserting, but are not allowed to be updated. about salesforcemagic HOT 5 OPEN

I have been thinking about consolidating the attributes into a single configurable attribute. The individual attributes would still be supported but deprecated.

from salesforcemagic.

+1

It becomes difficult with the SalesforceIgnore attribute also affecting the reads.

from salesforcemagic.

Yeah I was setting it to null but that broke cuz then the null handling got fixed (setting the salesforce field to null when you pass null) which is obviously good actually.

So I just use different objects for read and write for now.

from salesforcemagic.

Currently there is a SalesforceReadonly attribute that might help, but I am currently working on a single attribute that will have configurable options, also making objects cleaner.

from salesforcemagic.

is SalesforceIgnore working in the current release? I'm using it, but it isn't ignoring..

from salesforcemagic.