Creating a data model using the Litmus Production Record Data Model Configurator

the solution litmus production record data model configurator is designed to provide a guided experience to assist the user with where to start and where to go the sheet instructions provides a basic workflow, showing which sheets to go first and how to progress it also does provide a link to this documentation factory reset the configurator users can factory reset the configurator tool, for example if you want to create a new data model on a different sql server, with the reset configurator button in the sheet instructions reset an individual sheet most sheets have a dedicated clear sheet button in tool guides and help the sheets nodestructure and items both have a section designed to provide in sheet assistance and also show examples to help users to fill in the sheet the sheet nodeoptions shows some examples of what the hierarchy concept means with regards to a litmus production record data model this can be used together with the chapter core concept behind recording production record data via data model docid\ ffsctesqgb9gj7wy5kymo to define the base structure of your data model help button most sheets provide a help ? button in the right upper corner of the sheet this button opens a help window with three tabs the first tab gives a high level how to guide restrictions on ascii characters allowed to be used the second tab shows which characters are allowed (green) and not allowed (red) when setting up a node name, level name or item name this is necessary, as certain ascii characters can cause the transact sql used by the litmus production record database to not work correctly, especially when retrieving data the third tab shows which characters are allowed (green) and not allowed (red) when setting up a node descriptions, level descriptions or item descriptions this is necessary, as certain ascii characters can cause the transact sql used by the litmus production record database to not work correctly as descriptions are only contextual data and only stored in the configuration section of the database and not the live data, they are not available to be specifically queried against and are therefore allowing some additional ascii characters to be used