Skip to content
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

Proposed addresses can not be updated #213

Open
SPlanzer opened this issue Nov 22, 2017 · 2 comments
Open

Proposed addresses can not be updated #213

SPlanzer opened this issue Nov 22, 2017 · 2 comments
Assignees
Labels

Comments

@SPlanzer
Copy link

as per

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"

@Deb-Jones
Copy link
Contributor

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.

@SPlanzer
Copy link
Author

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

@SPlanzer SPlanzer changed the title Proposed addressed can not be updated Proposed addresses can not be updated Mar 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants