The demand records should be created in Avni with - address-level related fields, voiding status, last modified date time, and external id. For the remaining fields use the mapping metadata approach.
Since there are very few fields in demand, the metadata mapping should also be done along with this story.
Store AccountID as we may need it rather than AccountName while sending data back to SF
Support handling “DeletedDemands"
Save error records for missing mapping for a field and its coded answers.
The sync should resume from the previous point if an uncaught exception occurs.
Define two scheduled jobs. One to run demand sync and the second to process all demand errors.
Make it ready for QA
Deploy to Staging
Acceptance criteria
All the demands should be visible in the data entry app in Avni for any user who has the privilege.
Acceptance criteria