-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage Household Page Fails to Load If Customer Does Not Have Access to New Undeliverable Address Fields #6733
Comments
W-10135728 |
@jesslopez-sf I attempted this workaround with multiple profiles in the past few days. The workaround works for our SysAdmin profile, but does not work for our other profiles. Our SysAdmin profile has the Edit Read Only Fields permission, setting it apart from the others. As such, I believe the workaround instructions here are wrong - profiles need edit access to these fields, not just read access. |
Thanks for reporting @redmondke, I think you are right. We'll get this updated once we validate it |
Thank you so much, @redmondke ! We definitely missed that in our workaround. I've updated the description above. We did find that we could get away with just Read access on the Address object's Undeliverable field (but needed edit on both the Contact and Account fields). If you saw otherwise in your org, please let us know. |
Thanks, this fixed the neverending spinner issue for my org. In my case, I had initially granted edit access just to the Undeliverable Billing Address field on Account, not realising that Contact and Address had new fields too. That resulted in a different error message:
The error went away after granting edit access to the other fields. |
Included in beta release 3.211 (Beta 2) |
Included in production release 3.211 |
This still isn't working for me. Can someone help me understand where to look for where I might have missed a step involved in creating the permissions needed? ARGH. This hang up is creating problems down the line with my sync between SF and QBO |
@sarafigal We don't provide support via GitHub issues. Please instead create a support case with steps to reproduce and grant login access to an org affected by the issue See help article |
Summary
Customers are unable to view the Manage Households page after receiving the NPSP 3.209 update (released to sandboxes on November 4 and Production on November 16). This is due to a field access issue on 3 new fields introduced in the update. The page shows a never-ending spinner, with an Account error vaguely visible in the background.
Workaround
While we address this within the product, please grant access to the following fields:
Screenshot
The text was updated successfully, but these errors were encountered: