4. Verifying the data model and uploading it

to upload a tag configuration to litmus production record database or, if in offline mode, create a sql file, the configurator will always verify the configuration done by the user first to make sure that on a technical level all values are correctly formatted note the configurator will not verify if the tag configuration makes sense or configured correctly according to what the user wanted to define verifying the configuration the configurator will always verify the configuration first before publishing users can run the verification also as a stand alone operation without publishing the data model using the verify configuration button in online modus, t he user can be prompted multiple times, throughout the verification, to provide the sql authenticated login user name and password test for invalid ascii characters the verification process will verify in the sheets tags items if any entry has invalid ascii characters to learn more about which ascii characters are allowed, review the section restrictions on ascii characters allowed to be used in the case that invalid characters are found, a prompt is shown to the user to inform them about the fact and request from the user to select the next action users can either stop the verification using the no option or replace all invalid characters with and underscore " " trim long strings the configurator also will auto trim all strings which exceed the allowed maximum length sheet string maximum length tags device name 50 tags tag name 50 items item name 50 items item description 256 items initial value (if value type is isstring ) 256 verify every item has a value type set the configurator will verify that every item has a value type set if an item does have a missing value type, the user will be shown a prompt the user can define if they want to stop the verification using the yes option or set the default value type of isstring using the no option verify every item has an meta data setting the configurator will verify that every item has a value in the column labeled is meta data? if an item has no meta data setting, the user will be shown a prompt the user can define if they want to stop the verification using the yes option or set the default value of no using the no option verify that initial value is correct for its value type the configurator will verify that if an initial value is set, is correctly set for its value type if an item has an initial value which does not correspond with its value type, the user will be shown a prompt the user can define if they want to stop the verification using the yes option or set the default value of not setting an initial value using the no option uploading the tag configuration to litmus production record database to upload the configuration for new tags or update an existing tags, the user will need to have a connection to the sql server as well as the databases le productionrecord in place to upload the configuration, the user does press the button verify and upload throughout the process, the user can be prompted multiple times, throughout the verification, to provide the sql authenticated login user name and password the configurator will first run the verification process which was explained in the previous section progress is shown by a progress bar only if the verification has found no errors or was stopped, will the configurator upload the configuration to litmus production record database up on completing the upload, the user will be shown a summary of the sql logs to be able to review if all items where correctly added to litmus production record database or if any errors occurred on the sql side this log extract can be saved as a file using the save output to file button the file will be stored in the same folder, where the file litmus production record tag configurator v1 0 0 xlsm is located the name includes the name of the user as well as the date and time of the upload close sql out put window to finish the configuration creating a sql file in offline mode in offline mode, the user can create a sql file which can be later executed using applications like sql management studio to create a new tags or update an existing tags in litmus production record database to create the sql file, the user does press the button verify and upload the configurator will first run the verification process which was explained in the previous section only if the verification has found no errors or was stopped, will the configurator create the content of the file the user is then prompted to select the path where the file is stored as well as being able to modify the file name before saving it the result is a file with the ending " sql " which can be executed using applications like sql server management studio