You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 4, 2023. It is now read-only.
Yesterday I ran into something while adding a new region in the NSS Client. I added a comment to the review doc, but I'll mention it here as well. Once we are fully done with the Access version of the database, how will we know what RegionCode (GC number) to assign to new regions? Yesterday I inadvertently assigned an already-used RegionCode to a new region I added. I didn't know anything was wrong until it wouldn't let me add a scenario to the new region because the other region already had a scenario for that flowstat. It seems like maybe NSS should trigger an error/warning if an existing RegionCode is assigned to a new region. Or alternately, (once we are done with the Access version) maybe NSS should automatically assign the RegionCode value for new regions?
Disallow adding of a region with an existing region code, give error message
If no region code given, assign the region code as the next value
From Ryan: