Describe the problem you are trying to solve
When a user chooses "View All Fields", this option will create new records (either placeholder records or real records)
As of #1513, we introduced a short term fix and an ability for a user to recover by reloading all records. But ideally we would handle all of this on behalf of the user.
If the user is changing the value of ViewAllFields then the UX experience isn't great as salesforce changes records behind the scenes and the UI state does not match Salesforce state - causing save issues.
Ideal outcome
User can save View All Fields object permission and field permissions at the same time
This requires that we re-fetch permissions and re-calculate the save/update/delete for field permissions prior to attempting to save those ones
After a user saves View All Fields
We need to automatically re-fetch the permissions records, recalculate which fields are dirty (e.g. read is required - so that should not be dirty) and retain any potential error messages if there are any
Maybe - not sure about this:
Somehow tie the field permission value to the object permission value - basically let the user know that their desired field permission change will require view all records permission to be disabled or something.
Not sure what the flow could/should be - but there is probably something we can do here to make it better.
Unrelated - but could consider (maybe break into a new ticket)
a better confirmation modal where we show the user exactly what permissions are changing (maybe a tree like structure, so we show summary first and they can expand by object or expand all)
Describe the problem you are trying to solve
When a user chooses "View All Fields", this option will create new records (either placeholder records or real records)
As of #1513, we introduced a short term fix and an ability for a user to recover by reloading all records. But ideally we would handle all of this on behalf of the user.
If the user is changing the value of
ViewAllFieldsthen the UX experience isn't great as salesforce changes records behind the scenes and the UI state does not match Salesforce state - causing save issues.Ideal outcome
User can save View All Fields object permission and field permissions at the same time
This requires that we re-fetch permissions and re-calculate the save/update/delete for field permissions prior to attempting to save those ones
After a user saves View All Fields
We need to automatically re-fetch the permissions records, recalculate which fields are dirty (e.g. read is required - so that should not be dirty) and retain any potential error messages if there are any
Maybe - not sure about this:
Somehow tie the field permission value to the object permission value - basically let the user know that their desired field permission change will require view all records permission to be disabled or something.
Not sure what the flow could/should be - but there is probably something we can do here to make it better.
Unrelated - but could consider (maybe break into a new ticket)
a better confirmation modal where we show the user exactly what permissions are changing (maybe a tree like structure, so we show summary first and they can expand by object or expand all)