When the user attempts to edit any details of a proposed address, and leave the address as proposed, an error pops up stating 'A feature may not be updated to "proposed"'.
The cause of this will be that the message the UI sends to the API has the Life Cycle field populated so it is attempting to update the Life Cycle, but there is a validation rule that prevents the life cycle being updated to proposed.
I don't know whether we amend the UI or the API to resolve this.
The work-around is to delete the addresses and recreate them with the required details.
I'd like to add this to a back-log of AIMS fixes, but low priority because it's the first time we've had this problem since AIMS went live. We don't often update proposed addresses without amending their life cycle to current.
SPlanzer
commented
6 years ago
When the user attempts to edit any details of a proposed address, and leave the address as proposed, an error pops up stating 'A feature may not be updated to "proposed"'.
The cause of this will be that the message the UI sends to the API has the Life Cycle field populated so it is attempting to update the Life Cycle, but there is a validation rule that prevents the life cycle being updated to proposed.
I don't know whether we amend the UI or the API to resolve this.
The work-around is to delete the addresses and recreate them with the required details.
I'd like to add this to a back-log of AIMS fixes, but low priority because it's the first time we've had this problem since AIMS went live. We don't often update proposed addresses without amending their life cycle to current.