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
UiUtility.raiseErrorMesg(iface, 'A Feature may not be updated to "Proposed"')
proposed address can not be updated. There is a flaw in the logic here. This check can simply be removed providing it is okay to switch addresse from "Current" to "Proposed"
The text was updated successfully, but these errors were encountered:
During AIMS development I asked to be able to change an address from current to proposed, but e-Spatial said that this would corrupt the data integrity.
I would have thought however that a limitation such as this would belong in the API rather than the UI.
I would like to know the impact on data of editing an address from current to proposed.
Hi @Deb-Jones. I can not recall why this check was added, so your comment helps makes some sense of this bug. I knew there had to be a reason for the above check. It is the sort of thing we tried to avoid hard coding into the ui many times.
To get an answer to your question you will need to direct this at eSpatial
as per
QGIS-AIMS-Plugin/AimsUI/AimsClient/Gui/UiUtility.py
Line 382 in dd04fe1
proposed address can not be updated. There is a flaw in the logic here. This check can simply be removed providing it is okay to switch addresse from "Current" to "Proposed"
The text was updated successfully, but these errors were encountered: