Bi-directional support for Area Level fields in ADO integration

What is the challenge?

Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the settings allowing for bi-directional sync.

What is the impact?

Users can map a field bi-directionally that cannot be updated from Aha! to ADO

Describe your idea

If a user inputs an Area Level in Aha it should update to ADO. If the Area Level in input incorrectly and does not align to an existing Area, an error should be displayed in the logs.