Cascading Reference Question

[grassick]

This is similar to #162 but is referencing a custom table in a tableset.

Forms can then depend on custom tablesets, which means:

• [x] Adding a form to a schema (responses:xyz) requires adding the custom tablesets that are referenced by the form also
• [x] Referenced tables could be cached (updated by form cleaning) or determined on-the-fly
• [x] Form builder needs custom tablesets passed in to create/edit questions
• [x] Form builder needs to be able to generate custom tableset schema, which implies Customtableset schema builder moves to mawter-forms
• [x] createSchema needs to be sure to add custom tablesets for forms that are added
• [x] form context needs method to get complete custom table contents
• [x] ResponseRow needs to be able to reference and generate custom tableset row
• [x] Update response row and entity row to promise-based expr evaluator at same time

[Autio]

Muthi reports that the Comment box doesn't show in the Portal or App.

Has a comment visible in Detailed view but not in the response pop-up.

See this form: https://portal.mwater.co/#/forms/32bc71d1a2b5452f8211561c552fe6c5/responses

Can we add the comment box to show in the app response view and Portal response view?

Separately, when trying to view the responses in Detailed view for all deployments for that survey, it just gives an error:

And finally, when trying to view a response in edit mode in the Portal I don't see all the questions where the questions have conditionality set on the basis of being part of a specific deployment. Presumably that's not easy to change? Not a priority.

[grassick]

• Fixed the comment display
• Fixed the conditional on deploy bug (can you double check when you get a sec?)

The invalid point is Sebastian Gavera-89JVE5 who has a point with -1813938° 30249°. He entered it manually like that for some reason. I'm resetting to 0, 0 for this case and then putting in code to block it from happening again.

Muthi might want to clarify with the enumerator what happened.