10,730
edits
Line 200: | Line 200: | ||
* '''Questionnaire Folder''' (resco_questionnairefolder) stores information about the folder structure that organizes questionnaire templates in the designer. | * '''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}} | |||
=== Saving questionnaire data === | |||
* | |||
* | 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. | ||
Questionnaire data can be saved in three different formats: | |||
* Record-based model (default): Each answer in a questionnaire is a record. | |||
* JSON / compressed JSON: Answers are stored in JSON format that might be compressed. JSON requires fewer records and may result in faster synchronization. However, analyzing the answers may require additional effort. | |||
<!-- * Hybrid model (planned for a future release): Combination of the previous two models. For each question, you can configure what you prefer. --> | |||
The data model can be configured on the questionnaire template's '''Properties''' pane, in the '''Answer Storage''' field. | |||
See also: [[Resco Inspections data model]] | |||
=== Permissions === | === Permissions === | ||
Line 225: | Line 235: | ||
It is also possible to manage permissions by assigning ownership of Questionnaires to teams in the backend server. | It is also possible to manage permissions by assigning ownership of Questionnaires to teams in the backend server. | ||
=== Completion status === | === Completion status === |