> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/other-help-articles/project-level-validation-and-error-messages.md). # Project-level Validation and Error Messages ## Introduction When you click the name of a project the system displays a *Validate* button on the project *Details* tab. This button is located at the bottom of the screen on the *Validate* tab. When you click this button the system reviews your project and provides a list of violations and warnings in your modeled content, which is a useful check for some common modeling errors. The system prompts you to review, ignore, or correct each issue. It also allows you to select an error and, for some of the issues, request that the system perform the error resolution. The table below contains a list of possible warnings and typical corrective actions to take for each item in the list. The system displays the error but also provides the name of the logicnet, node, and path, as appropriate, to make it easier for you to find where the error occurs. ## Project Validation Steps * The validation button is located next to the search button at the bottom of the screen. You can resize this panel by dragging the top bar up (1), and you can minimize it by using the window icons on the right (2). ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c8948cd48a517641ab1ddb87cf8c4c466d01270e%2Ffdce1d9a-d194-4c9a-9707-017d791d61db.jpg?alt=media) * Review the results using the filtering options. * Flag the items as *Resolved* or *Ignore* by clicking each individual checkbox or by clicking the checkbox next to *Type* to select all. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-81528ee1111a96f9c96024bc1af72c553b78407e%2Fcd53dfa1-251c-44be-a9b2-e61ada149490.jpg?alt=media) * Reset the list if necessary using the *Reset ignored* button. * Run the validation prior to publishing each time to verify that no additional warnings have been triggered. ## Validation Warning Table |

Code/
Resolution

| Message/Description | Action | | | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

000100
Manual

|

Message: "Could not find the linked project item: ''."
Linked project items are references to items in other projects and are created with the copy-paste-link operation. This error indicates that the system could not find the referenced item.

| Make sure that the project containing the referenced item is loaded in the same workspace as your project. | | |

000101
Manual

|

Message: "The project item link is corrupt, it is missing the: 'source'."
Linked project items are created using the copy-paste-link operation. This error indicates that link has become corrupt.

| Delete the link and recreate it using the copy-paste-link function. | | |

000102
Manual

|

Message: "The project item link is corrupt, it is missing the: 'vtype'."
Linked project items are created using the copy-paste-link operation. This error indicates that link has become corrupt.

| Delete the link and recreate it using the copy-paste-link function. | | |

000103
Manual

|

Message: "'\' cannot be found in entry."
The topic contains images or links to a file that cannot be found on the server.

| Update the topic and fix the references. | |

000104
Manual

|

Message: "A with name: '' already exists."
This warning indicates that another item with the same name already exists in the project. Duplicate names can lead to ambiguity and unexpected behavior in your application; for example, a call node may call the wrong logicnet with the same name.

| Make sure that your project items have unique names. | | |

000105
Automatic

|

Message: "Unused project resource: '' found on the server."
This warning indicates that the system can find the file on the server but that the project does not use it.

| Click ***Resolve*** to remove the unused resource from the server. | | |

000106
Manual

|

Message: "Could not find project resource: '' on the server."
This error indicates that they system cannot find the file on the server.

| Delete the project item and recreate it by uploading the resource. | | |

000107
Manual

|

Message: "Error loading logicnet: ''."
This error indicates that the LogicNets runtime could no longer read the logicnet.

| Try to restore a previous version of the logicnet or open the project's *Code* tab and fix the syntax in the code definition. | | |

000108
Manual

|

Message: "Invalid logicnet name: ''."
This error indicates that the logicnet name contains illegal characters.

| Update the name of the logicnet. | | |

000109
Manual

|

Message: "Called logicnet is not specified."
This error indicates that no logicnet has been specified in the call node.

| Specify the logicnet to call. | | |

000110
Manual

|

Message: "Call node is not using: call-by-name."
This warning indicates that the call node is still using the 'call-by-id' method to call a logicnet. Though the system still supports 'call-by-id', we recommend you use the safer 'call-by-name' method, as logicnets ids can change when logicnets they copied or moved.

|

Open the Code tab in the node editor and add the following line to the code: 'match\_name = "yes"'.
Ensure that the called logicnet is unique in the project.

| | |

000111
Manual

|

Message: "Call node uses interpolation, can't check for the existence of logicnet: ''."
This warning indicates that the system will only resolve the name of the called logicnet at runtime by interpolating a data object. Because of this, the system cannot verify if the called logicnet exists.

| Ensure that the called logicnet exists with the name identified. | | |

000112
Manual

|

Message: "Called logicnet: '', could not be found in library project: ''."
This error indicates that the system could not find the given logicnet in the referenced (library) package.

| Ensure that the referenced (library) package is installed on your system and that it has a logicnet with the given name. | | |

000113
Manual

|

Message: "Could not find the called logicnet: ''."
This error indicates that the system could not find the called logicnet in your project.

| Make sure that the called logicnet exists in your project. | | |

000114
Manual

|

Message: "'' value is incorrect \[current=,expected=]."
This warning indicates that the given parameter has an incorrect value.

| Open the part editor and click ***Save***. The system will default the parameter to a correct value. | | |

000115
Manual

|

Message: "This node is unreachable."
This warning indicates that the given node is not part of any pathway started from the start node of the logicnet.

| Verify the node is not intended to be part of logicnet pathway. If it is not intended you can suppress this error by 'accepting' the validation. Otherwise, reconnect the node. | | |

000116
Manual

|

Message: "This node does not have an ID."
This error indicates that the given node does not have an id, which means the system cannot execute it.

| Open the *Code* tab in the node editor and add the following line to the code: 'id = '. | | |

000117
Manual

|

Message: "Referenced (library) package: '' does not exist."
The error indicates that the system could not find the referenced (library) package.

| Check your library reference and ensure that the referenced (library) package is installed on your system. If you use an alias ensure that the alias is correctly configured in your project settings and pointing to the correct package. | | |

000119
Automatic

|

Message: "The logicnet named '' is orphaned."
This warning indicates that there is a logicnet in the project that has no parent folder anymore and is no longer visible in the project tree.

| Click ***Resolve*** to move the orphaned logicnet to the recycle bin. | | |

000120
Automatic

|

Message: " is replaced by parameter."
This warning indicates that LogicNets has deprecated the given parameter and replaced it with a different one as part of the evolution of the system.

| Click ***Resolve*** to replace the deprecated parameter with the new parameter. | | |

000124
Automatic

|

Message: "The parameter: '' is not valid in the current part configuration."
This warning indicates that the given parameter is not valid in the current part configuration. It may be a previous part configuration, or there may be an error in your part configuration.

| Check your part configuration. Click ***Resolve*** to remove the parameter from your part configuration. | | |

000129
Automatic

|

Message: "The caption contains $(...) which can induce XSS vulnerabilities."
This warning indicates that there is a risk that the interpolated data may allow for malicious code injection, which could permit a security breach.

|

Turn on the Escape $(..)-text option to escape the dynamic content or use $(html(...)) to whitelist the interpolated data if it can be fully trusted.
Click Resolve to turn on the Escape $(..)-text option.

| | |

000132
Automatic

|

Message: "This parameter is not used anymore and can safely be removed."
This warning indicates that LogicNets has deprecated the parameter and can safely removed from the part configuration.

| Click ***Resolve*** to remove the parameter. | | |

000136
Manual and Automatic

|

Message: "'' is not a public part \[scope='\']."
This error indicates that you are using a deprecated or internal part in your application. The system will not execute these parts.

| Remove this part. Some deprecated parts offer an automatic migration to another compatible part and you can click ***Resolve*** to migrate to the replacement part. | |

000137
Manual

|

Message: "The part: '' does not exist."
This error indicates that you are using a part that no longer exists.

| Remove this part. | | |

000138
Manual

|

Message: "Error retrieving root folder for project."
This error indicates that the project is corrupt and the system cannot open it.

| Restore a backup of your project. | | |

000139
Automatic

|

Message: "The HTML contains $(...) which can induce XSS vulnerabilities."
This warning indicates that there is a risk that the interpolated data may allow for malicious code injection, which could permit a security breach.

|

Use the Comment part, which will automatically escape your dynamic content. You can also use $(html(...)) to whitelist the interpolated data if it can be fully trusted. You can also use $(escape\_html(...)) to escape the dynamic content.
Click Resolve to have the system change to the Comment part.

| | |

000140
Automatic

|

Message: "The script contains $(...) which can induce XSS vulnerabilities."
This warning indicates that there is a risk that the interpolated data may allow for malicious code injection, which could permit a security breach.

|

Turn on the Escape $(..)-script option to escape the dynamic content, or use $(html(...)) to whitelist the interpolated data when it can be fully trusted. You can also use $(escape\_html(...)) or $(encode\_js(...)) to escape/encode the interpolated data.
Click Resolve to turn on the Escape $(..)-script option.

| | |

000142
Manual

|

Message: "Referenced package: '%s' does not exist."
It is possible to give a called logicnet the name of a package or alias. This error indicates that the system cannot find the package.

| Check the package name or alias. Make sure that you have the package with the correct package name installed in your environment. | | |

000143
Manual

|

Message: "The package-alias: '' can only be resolved at run-time, not able to check for the existence of the called logicnet."
It is possible to give a logicnet a package alias. This message indicates that the system can only resolve the alias at runtime, which means it is not possible to verify that the called logicnet exists.

| Test the *Call* node by running the application. | | |

000144
Automatic

|

Message: "The parameters: 'app' and 'db' are deprecated, you should use the @-notation instead."
This warning indicates that you are using deprecated 'app' and/or 'db' parameters in your part configuration to reference logicnets in other packages. Use the library references or @-notation instead; for example, "package-name\@logicnet-name".

| Click ***Resolve*** to change to the *@-notation*. | | |

000145
Manual

|

Message: "A path or collection name cannot start with '\_in.' or '\_out.'."
This error indicates that you are using '\_\_in' and '\_\_out' in the path or collection name. These are names reserved for function parameters and cannot be used in regular paths or collection names.
Note: Each function has its own '\_\_in' and '\_\_out' data objects, which can only be used within the function scope itself. The system will not pass them to subsequently called logicnets. If you need to pass the '\_\_in' and/or '\_\_out' data objects to a subsequently called logicnet, use the "Set Data Object value" part with "Data object type" set to "container" to create a copy.

| Change the path or collection name. | | |

000146
Automatic

|

Message: "The script contains redirect code that can induce XSS vulnerabilities."
This warning indicates that there is a risk that the interpolated data may allow users to insert malicious code to redirect your users to an unsafe location.

|

Use the Redirect session part to perform redirections. This part ensures that redirects are only made to whitelisted locations. Click Resolve to change to the Redirect session part.
Note: This automatic resolution is only possible when the redirect code is the only code in the script, otherwise you must manually add the Redirect session part.

| | |

000148
Automatic

|

Message: "Unsupported self-closing HTML5 tags found."
This warning indicates that there are self-closing tags in the project content that will not render correctly at runtime.

| Click ***Resolve*** to convert these tags to a regular HTML tag pair. | | |

000149
Automatic

|

Message: "Avoid hardcoding package names; use library aliases instead.."
This warning indicates that a call node uses the \[library-name]@\[logicnet-name] construction. While this will work in situ, this approach is not supported in conjunction with the Deployment Manager that can update library names for versioning purposes.

|

Select a library alias via the ‘Library project’ field.
If necessary, navigate to project settings and add the library package and alias info to the project.

| | |

000160
Manual

|

Message: "Local content resource | KnowledgeCenter topic not found (# - )."
This warning indicates that the reference to the content resource or knowledge center article could not be resolved by the system. Consequently, the content resource or knowledge center article will not show when the user hovers over the help icon of the question.

| Look for the referenced content resource or knowledge center article. Try to remove and add the resource link again when the resource and articles are available. | |

000161
Manual

|

Message: "No KnowledgeCenter-topic resource found for with tag-category (and tag-value )."
This warning indicates that referenced knowledge center article has been selected by tags and that there are no articles with the given tag in the knowledge center.

| Look for the articles in the knowledge center and ensure that they have the correct tags associated with them. | | |

000162
Manual

|

Message: "The -part is not available \[reason=]."
This error indicates that you are using a part that is not available in your setup. Please check the reason text for more details.

| Remove this part. | | |

000170
Manual

|

Message: "This type of validation ('') does not support conditions set using the Rule editor."
This error indicates that you are trying to use a feature that is not available for the selected validation type.

| Switch back to the Condition editor to type in the condition manually. | | |

000171
Manual

|

Message: "This type of validation '' does not support conditions."
This error indicates that you are trying to use a feature that is not available for the selected validation type.

| Remove the condition for this type of validation. | | |

000201
Manual

|

Message: "The configuration of this part contains one or more invalid settings."
This error indicates that there are invalid settings with the part configuration that potentially can lead to unexpected behaviour of your application.

| Open the part configuration to resolve the errors. | | |

100001
Manual

|

Message: "The 'Highcharts (Maps)' package is not installed."
The 'Chart' part requires you to have Highcharts (Maps) installed on the system to run. This warning indicates that the Highcharts (Maps) package is not installed on the system.

| Acquire and install the Highcharts (Maps) package. | | |

100002
Manual

|

Message: "The map cannot be presented as the 'Highcharts (Maps)' package is not installed."
The 'Chart' part requires you to have Highcharts (Maps) installed on the system to display a map. This warning indicates that the Highcharts (Maps) package is not installed on the system.

| Acquire and install the Highcharts (Maps) package. | | |

200001
Automatic

|

Message: "The input type: 'text' is deprecated. Data object type: 'number' only supports the input types: 'formatted number' or 'number'."
In older versions of LogicNets it was possible to use a text input as the input for a number object. This warning indicates that the system now only supports 'formatted number' or 'number' inputs for number object types.

| Click ***Resolve*** to change the input type to 'Formatted number'. | | |

300001
Manual

|

Message: "Column: already has an Alias."
This warning indicates that the column has both an alias and an 'AS ' part in the SQL expression. This would lead to an SQL error while retrieving the data from the database.

| Remove the alias (the AS part) from the column's SQL expression. | | |

300002
Manual

|

"Message: No Alias specified for aggregate column: ."
When a column uses an aggregate function it must have an alias. This warning indicates that no alias has been specified for the column, which may cause functionality like sorting and row totals to fail.

| Specify the alias for the column. | | |

300003
Manual

|

Message: "No Alias specified for SQL-expression column: ."
When a column is an SQL expression you should define an alias. This warning indicates that no alias has been specified for the column, which may cause functionality like sorting or row totals to fail.

| Specify the alias for the column. | | |

300004
Manual

|

Message: "Totals row requires Alias for column: ."
When the totals row is configured, number and currency columns with a '.' in the column name must have an alias for the totals to work.

| Specify the alias for the column. | | |

400001
Automatic

|

Message: "The parameter: 'data\_type' must be set to 'collection'. Use 'item\_type' to specify the data type."
In older versions of the checklist part the data\_type was set to 'text' or 'number'. LogicNets has introduced a new parameter, called 'item\_type', to store the item type as 'text' or 'number'.

| Click ***Resolve*** to convert the parameter. | | |

500001
Manual

|

Message: "The Lua script contains errors or warnings."
With v7.4.6+ the system triggers this validation error when a server-side script part or a custom part built with Lua has an error or warning. By selecting this validation error, you can go to respective part and execute the check code functionality. For more information, see the server-side script documentation: Server-side Script.

| Go to the respective part and execute the *check code* functionality. | | |

500002
Manual

|

Message: "Missing parentheses which may alter boolean precedence."
With v8+, the system triggers this validation warning when there is potential ambiguity in the desired processing of a rule.
In v8, the system has been updated to LUA5 where the AND and OR operators have updated precedence, now following generally accepted mathematical best practice:
Simplified example: A or B and (C or D)
- In Lua 4: Both operators have the same precedence
The rule is processed left to right as (A or B) and (C or D)
- In Lua 5: The precedence of or is smaller than the precedence of and while still honoring the parentheses
The rule is processed as A, or (B and either C or D)

| Go to the respective rule and add additional parentheses to insure the rule clauses are assessed in the correct order. | | |

500003
Manual

|

Message: "Cannot parse expression to check for Boolean precedence \[reason = X]"
With v8+, the system triggers this validation warning when a manual condition cannot be assessed or re-written for the change in Boolean precedence (see 500002 above).
Possible reasons are:
- Operator expected: check your condition for a missing = ,+, >, <, \~= etc.
- Operand expected: check correct entries before and after the operator
- Unknown operator found: check this article for valid operators
- Missing closing parenthesis: verify all parentheses are opened and closed
- Missing closing quotation mark: verify all text operands are within 'quotes'

| Go to the respective manual condition, verify and correct, as necessary. | | |

500004
Manual

|

Message: "Empty object path (reference) in rule."
For a rule to work it needs a data object on which to perform the evaluation. This warning indicates that the rule is missing that data object. Navigate to the rule by clicking on the validation warning and update the indicated rule. You may need to switch to the tab where the actual rule is configured.

| Go to the rule and specify the object path. | | |

500005
Manual

|

Message: "Empty value(s) in answer options table"
This warning indicates that the answer option list contains a null entry.
Radiolists, checklists and dropdowns should not have empty answer option values as this will cause a flaw in the UI at runtime, or a logical error with FHIR Questionnaire-based content.

|

Remove row, or enter value/caption and save.
Navigate to the location by clicking on the validation warning and edit or delete from there.

| | |

500006
Manual

| Message: "Empty translatable text found." | Check the text. | | |

500007
Manual

| Message: "Choice value contains leading/trailing spaces or multiple consecutive spaces." | Remove leading, trailing, or extra spaces in the answer options list and save. | | |

500008
Manual

|

Message: "Unlinked answer option found"
This warning indicates that an answer does not have an active path to the next node, and usually results in an unexpected stop in the logic flow at runtime. Any options without routing are presumed to route to the stop node. If this is the desired logic outcome, the validation warning is a false positive.

| Verify all answers have a legitimate output by right-clicking on the node, choosing "add link" and adding any connections for unlinked answers. | | |

500009
Automatic

|

Message: "The node doesn't have all expected links"
This warning indicates that a node does not have the correct output parameters expected for the node type. Note that these parameters are not displayed as part of the part editor in the Designer. The occurrence of this issue is rare.

| Click ***Resolve*** to update the underlying node parameters, or recreate the node starting with the template on the Node Toolbox. | | |

500010
Manual

|

Message: "Reference meta data is missing. The link text is: '(provided)'"
This warning indicates that a content reference cannot be displayed due to error relating to the unique identifier.

| Remove and recreate the reference from scratch. | | |

500011
Manual

|

Message: "The content reference has been renamed (# and name)"
This warning indicates that a content reference is now listed under a different name and the original content reference is not available to display.

| Click ***Resolve*** to update the reference link. | | |

500012
Manual

|

Message: "The referenced node (# provided) is not found because the logicnet (name and # provided) has been removed. \[linktext: '(provided)']"
This warning indicates that a content reference includes linktext that points to a node that no longer exists in the logicnet.

|

Update or remove the reference to the logicnet and node
AND/OR
Review the changelog to see when the logicnet was removed

| | |

500013
Manual

|

Message: "The referenced logicnet (# and name provided) has been removed. \[linktext: '(provided)']"
This warning indicates that a content reference includes linktext that points to a logicnet that no longer exists in the project, most likely removed by a Designer User in an earlier session.

|

Update or remove the reference to the logicnet
AND/OR
Review the changelog to see when the logicnet was removed

| | |

500014
Manual

|

Message: "The referenced logicnet (# and name provided) has been renamed to (name provided). \[linktext: '(provided)']"
This warning indicates that a content reference includes linktext pointing to a logicnet that has been renamed, most likely done by a Designer User in an earlier session.

| Update or remove the reference to the logicnet | | |

500015
Manual

|

Message: "The referenced node (# provided) is not found in the logicnet (# and name provided). \[linktext: (provided)]"
This warning indicates that a content reference points to a node (using the linktext provided) that no longer exists in the logicnet, most likely due to its removal by a Designer User in an earlier session.

| Update or remove the reference to the node. | | |

500016
Manual

|

Message: "The linked reference '(name and ID provided)' no longer exists."
This warning indicates that a content reference has been removed, most likely by a Designer User in an earlier session.td>

| Update or remove the reference to the node. | | |

500017
Manual

|

Message: "Multiple form-parts with the same full path are present"
This warning indicates that the form-part shown generates a full path during runtime that is duplicated elsewhere in the model.
"Full path" is the combination of any context path (usually set in a call node) and the data object field of the part.
When using FHIR Questionnaire-based frameworks, full paths and their auto-generated linkIds must be unique.
In other types of projects, duplicate paths can also lead to logic errors on screen, but there are some scenarios where this warning can be ignored.

|

Ensure each form-part has a unique value for its full path generated at runtime.
Use the context path field in a call-node to create unique full paths for questions in re-used logicnets.

| | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/platform-documentation/other-help-articles/project-level-validation-and-error-messages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.