Eric Kintzer

I agree with Andy -- if you want a specific Selector to return only updateable fields, then the usage would be `AccountsSelector.newInstance().selectAllUpdateableById(someIdSet)` and let the selector method itself resolve from...

the bigger issue is that xxxHistory objects can't be mocked, even using json.deserialize technique

this is related to https://github.com/financialforcedev/fflib-apex-common/issues/215

@foxcreation - I know that my org's implementation calls `registerDirty` multiple times on same sobject in memory for some use cases -- would that be broken by this PR?

so, currentmethod registerDirty(Sobject) is unchanged? e.g. ``` Account a = new Account(Id = x, Website = 'w'); registerDirty(a); a.Rating = 'foo'; commitWork(); ``` will update the Account id=x with Website='w'...

@foxcreation - I don't understand your example code. What is `a0`? Did you mean `acc`? If I follow, the essence of this is that if one uses the new second...

Isn't this resolved as [per Stackexchange answer](https://salesforce.stackexchange.com/questions/340504/apex-mocks-test-error-for-domain-class/340554#340554) ??

Andrew - Thank you for following up. YES, this is confirmed. - I took a Trailhead DE org, - enabled Encryption on `Opportunity.Name` (couldn't enable encryption on `Account.Name` because DreamHouse...

No problem; as I stated to Doug Ayers, I've come to the conclusion that ISVs or open source GitHub repos should enable Shield encryption for every OOTB standard field that...

There's an additional issue that prevents install for (some) Shield customers (v3.2) ```Send_Better_Email_Testflow: Get_Contacts (Get Records) - Flow filters can't reference encrypted fields. Remove the reference to field "Name" on...