Eric Kintzer
Eric Kintzer
Currently, `fflib_IDGenerator.generate(ContactHistory.SObjectType)` returns `null000000000000` for any xxxHistory object because getDescribe().getKeyPrefix() returns null for these SObjects Extend the class's `generate` method to look like this: public static Id generate(Schema.SObjectType sobjectType) {...
**use case:** Mocking `xxxHistorySelector` result records (e.g. `AccountHistory`, `CaseHistory`, `customObj__History`) fflib_IdGenerator.generate(AccountHistory.SObjectType); current behavior: null pointer exception PR: returns `017xxxxxxxxxxxxxxx` **Notes:** OpportunityHistory returns `008xxxxxxxxxxxxxxx` (as this object has a keyPrefix available...
the method `throwException` currently displays Expected n, Actual m -- Wanted by not invoked which can lead to head scratching when one tries to figure out why the `verify` fails....
## Summary We have enabled Platform Encryption on Account.Name; unfortunately, the apex test methods use SOQL that violates Platform Encryption rules: - LIKE operators ``` SELECT id FROM Account WHERE...
A handy enhancement would be a new fluent method on fflib_QueryFactory that supports the `For Update` clause .addForUpdate() the `addForUdpate` would do a `getOrderings().clear()` as you can't `Order By` with...
[Issue](https://github.com/financialforcedev/fflib-apex-common/issues/237) - Platform Encryption does not allow Order By or LIKE on encrypted fields. - Account.Name and Opportunity.Name are used in testmethods with LIKE and/or Order By; both are potentially...
This error fflib_QueryFactory.InvalidFieldException: Invalid field 'FieldHistoryType' for object 'FieldHistoryArchive' is thrown in method `getFieldPath()` - Error does not occur when running user has `Admin` profile - Error does occur when...
In `fflib_SObjectSelector` we have a useful method to add lookup fields from a selector instance to an existing queryFactory ``` public void configureQueryFactoryFields(fflib_QueryFactory queryFactory, String relationshipFieldPath) { // Add fields...
In Shield Platform Encryption, you can't use Order By on an encrypted field. This can't be detected at analysis time by Shield Platform Encryption if one is using the fflib_SObjectSelector...
lines in the testmethods that look like this: qf.selectField('name').selectField('Id').setCondition( 'name like \'%test%\'' )... do not work if the org has enabled Shield Platform Encryption (deterministic) on `Contact.Name`. Why? - You...