Assigning a property to a user requesting access does not save the property assignment
Chris-Boe opened this issue · 2 comments
Describe the bug
When you assign a property to a new user requesting access (and set them to Property Manager), the property selection is not saved in the database.
To Reproduce
Steps to reproduce the behavior:
- Go to the dashboard and click "Add" on a user requesting access
- Set them to PROPERTY_MANAGER role
- Select a property to assign to them
- Click on Save (have network tab open to see the property ID getting sent to the backend
- Look up this user on the Property Manager list page
- Click on the user from the list
- Notice the property selected in step 3 is not shown on the page nor returned from the network request
Expected behavior
New Property Manager should have property assigned
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.
@NickSchimek Looks like you might be looking at an old version of the app, when you select Property_Manager it should show a SearchPanel for Properties I think I was able to fix the Search Panel not showing up on my current branch and that's when I noticed the backend wasn't saving the update we're sending it. I'm almost done with my branch so once it's merged we can repro this and investigate!