Modify Model(s) in Digital Twin for multiple Litmus Edge

to modify model(s) with litmus excel add ins, you should be familiar with how models work in digital twins docid\ xlj3gvozyg 52ue4pb5u7 on litmus edge before you begin you have installed the litmus excel add ins extension see install litmus excel add ins docid\ gzdhbj1xzznddthyocuuu for details you have prepared a prepare a new tool file to manage digital twin models docid\ ov8snxemrb3nvzjjk6duh model(s) have been add model(s) to digital twin for multiple litmus edge docid\ fjdc7dwaspwvuwgnwoblc to digital twins initial preparation open a new dt model management tool file in excel if prompted, enable content to allow the code to run make sure the the tool is for the connect to option set to multiple le modify models(s) import model(s) import the model settings for model(s) defined on litmus edge using the import model(s) wizard docid 6b2rmrjg50mf gtidwt8w users can set a filter to reduce the number of module(s) shown as selection to the user le device ip select or enter the ipv4 of the litmus edge you want to import model(s) from notes you may need to provide the api key if the litmus edge has not been used with the tool search option select what type of filter is to be used model name mask set the filter to be applied will be ignored if search option is set to all the wizard will show what filter will be applied press the search button to pull the filtered list of model(s) from litmus edge the user will be shown the filtered list of model(s) matching their filter select the model(s) to import and press the import button notes users can choose between press new search to set another filter and search again if the list doesn't show the model(s) the user wanted to import select all model(s) using the checkbox in the header row select a group of model(s) by selecting their respective check box select one model by selecting the respective check box select no model and close the wizard pressing the close button instead the selected model(s) with their settings are imported into the sheet once finished, the user can either p erform another search using the new search button finsih the import using the close button the action for each imported tag is set to m for modify mandatory model settings users can modify these mandatory settings for a model(s) model name the name of an existing model can be changed important this will change the topic for the instances of this model and will cause other services like analytics, integrations or flows not be able to read the data model definition properties are a mandatory set of model settings, which are required for defining the digital twin model data structure static attributes create and import models docid\ zpadx1lmme0f44v7r6v6q allow to m anage the metadata for the model this column combines all of these as a single json object it is recommended to use the static attributes wizard docid\ sgcuuahdbpogmkt6m6ck when setting your specific values for static attributes transformations create and import models docid\ zpadx1lmme0f44v7r6v6q allow to define how to transform the data collected in instances by converting raw json data to a desired format by defining the json based schema by the model this column combines all of these as a single json object it is recommended to use the transformations wizard docid\ szgnxuppussqogr75xu0n when setting your specific values for transformations dynamic attributes create and import models docid\ zpadx1lmme0f44v7r6v6q allow to m anage variable data in the model this column combines all of these as a single json object it is recommended to use the dynamic attributes wizard docid\ pm4mpwmlpyltf5lqro8g6 when setting your specific values for dynamic attributes model schema create and import models docid\ zpadx1lmme0f44v7r6v6q allows to create a custom data structure for the model this column combines all of these as a single json object it is recommended to use the model schema wizard docid\ swqiuan 1cmi7eg qofle when setting your specific model schema not mandatory model settings model description enter a short description of the model in the description field uns enabled select if you want to enable litmus uns for the model uns connector if litmus uns connector(s) are defined for the litmus edge, select which litmus uns connector to use to populate the static attributes with the litmus uns hierarchy notes selecting an uns connector will automatically modify the respective static attributes associated with the uns connector as well as adding them to the model schema under the metadata folder by default before changing uns connector after changing uns connector notes you can repeat modifying modify model(s) in digital twin for multiple litmus edge /#mandatory model settings and modify model(s) in digital twin for multiple litmus edge /#not mandatory model settings model settings for every model you need to modify before modify model(s) in digital twin for multiple litmus edge /#executing actions executing actions when all modify model(s) in digital twin for multiple litmus edge /#mandatory model settings and modify model(s) in digital twin for multiple litmus edge /#not mandatory model settings settings for all model(s) are set they are ready to be modified it is recommended but not mandatory to verify the configuration first without executing the action by pressing the verify only button this will check that all required model settings are provided and logically correct and provide any finding to the user example below the user not select a uns connector despite having enabled uns in column uns enabled important the tool can not verify if all provided model settings are factually correct for example it can not verify that the value of a static attribute is correct for what the user want to achieve the model(s) can be modified to litmus edge by pressing the verify + execute button the tool will group all the model(s) based on the litmus edge(s) defined in column target litmus edge ip for each litmus edge this will check that all required model settings are provided and logically correct and provide any finding to the user if no issues have been identified, the tool will verify that the user wants to execute all the actions from the action column a add model(s) m modify model (s) d delete model (s) i ignore model (s) > do nothing to perform all actions, press the yes button the tool will perform all actions row by row for the litmus edge when finished, a result summary is shown close the result summary by pressing the x close button the tool will ask if the user wants to re compare the model(s) against litmus edge to re compare, press the yes button to not re compare, press the no button if the user selected to press the yes button from aboves messagebox, the tool will pull all the model settings from litmus edge again including the modelid and also change the action to m for each model with a modelid or a formodel with no modelid troubleshooting the tool will perform several checks throughout the proces of defining the model settings if they do not pass successfully, the user will be notified the checks include model name uniqueness on a litmus edge level the tool checks if a model name already exist for a specific litmus edge in the tool allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for model names and descriptions the user is shown a message box as notification the character(s) are highlighted in red and also shown in a note see allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for a full list for both names and descriptions correct json formating for static attributes, trasnformations, dynamic attributes and model schema example for an invalid json formatting of the static attributes while it is possible to not define entries for the columns static attributes, trasnformations, dynamic attributes and model schema , the tool verifieds if any of these columns are empty as this will cause instances of this model to not return data or not return expected data while it is possible to leave some values for static attributes and dynamic attributes empty, the tool checks for such empty values as this will cause instances of this model to not return data or not return expected data example no schemaid defined for dynamic attribute