Improvement in the error handling for excel schema imports

[saharshkhicha18]

Problem description

While digitising the policy, I came across a few issues that occur when importing excel file in guardian. For example:

• If i make the field type -> Auto-Calculate and Visibility -> No in the excel sheet then the schema field type after import in guardian becomes hidden but in the VC document the field can be seen when conducting a dry-run. Since "field type -> Auto-Calculate and Visibility -> No" is a conflicting configuration, we can have a validation on this?

• When I leave the "Visibility" empty for an enum field in excel, it is optional automatically in guardian schema but when left empty while filling the document during dry-run, it returns error (One of the options should be chosen)

Error: {"type":"JSON_SCHEMA_VALIDATION_ERROR","details":[{"instancePath":"/G5/G30","schemaPath":"#/properties/G30/enum","keyword":"enum","params":{"allowedValues":["Afforestation and Reforestation","Agriculture","Mangroves"]},"message":"must be equal to one of the allowed values"}]}

• For field type -> Help Text, if Required -> Yes then in that case, when submitting the document in dry-run, the submit button is disabled even after filling out all the information since the Help Text field is required behind the scenes and there is no way to move forward in this case.

Expected behavior

To have better validation when excel is imported into guardian which will help prevent all the points I mentioned above and some more that I probably missed while working on methodology digitisation