Inspections: Difference between revisions

Resco Inspections utilizes the data-driven architecture rather than the metadata-driven approach. It means that the Resco Inspections data model (entities, fields, relationships) is already created, and when building a new custom questionnaire template you are not altering the data model – instead, you’re adding the entity records. As a consequence, the user who manages the questionnaire templates does not have to be a backend administrator since this user is not changing the data model.

All questionnaire data is saved as records on your backend server (Resco Cloud/Dynamics/Salesforce), in multiple custom entities:

* '''Questionnaire''' (resco_questionnaire) stores information about the questionnaire templates, snippets, and answered questionnaires.

* '''Question Group''' (resco_questiongroup) stores information about the question groups. Each question group can contain multiple questions.

* '''Question''' (resco_question) stores all the questions created for the questionnaire, as well as answers.

* '''Questionnaire Folder''' (resco_questionnairefolder) stores information about the folder structure that organizes questionnaire templates in the designer.

See also: [https://blog.resco.net/2020/06/02/resco-inpections-for-dynamics-365-data/ Dynamics 365 – how is the data stored?] {{Badge|Blog}}

When an app user starts a questionnaire in the app, a new copy of the template is created. For an answered questionnaire, we store both questions and answers. When you enable template dependency, the answered questionnaire is no longer self-contained (it refers to the template) but each answer needs less data (faster sync and less database storage). How self-contained should answers be is configured on the questionnaire template's '''Properties''' pane, in the '''Template Dependency''' field.