Steps to Reproduce
- Create a metadata record, such as a sensor, scoped to a workspace.
- Create a global metadata record of the same type.
- Switch to a second workspace and view the sensor table.
Expected Behavior
The system metadata table should only display system metadata. Any metadata records scoped to a workspace should not appear.
Actual Behavior
The table currently displays all metadata the user has read access too, including metadata scoped to other workspaces.
Any additional comments?
This doesn't seem to affect dropdowns in forms, just the system metadata table. HydroServer's API will filter out any metadata scoped to a workspace using workspace_id=null, so it could be an issue with that parameter not getting set in the API call, or the metadata being stored locally on the browser from another API call and not being filtered from the local store.
Steps to Reproduce
Expected Behavior
The system metadata table should only display system metadata. Any metadata records scoped to a workspace should not appear.
Actual Behavior
The table currently displays all metadata the user has read access too, including metadata scoped to other workspaces.
Any additional comments?
This doesn't seem to affect dropdowns in forms, just the system metadata table. HydroServer's API will filter out any metadata scoped to a workspace using workspace_id=null, so it could be an issue with that parameter not getting set in the API call, or the metadata being stored locally on the browser from another API call and not being filtered from the local store.