Impact Condition | Cause |
Configuration Error | The configuration of the resource is no longer valid, or its validity is uncertain. For example, when you import a data source, it might be impacted if it is unclear that the resources within the data source still exist. A reintrospection can resolve that uncertainty. |
Missing Resource | A resource depends on another resource that no longer exists or is unavailable. For example, if a view references a table that was deleted, the view becomes impacted. |
Mismatched Resources | A resource depends on another resource that has changed and no longer matches—for example, if the number of input variables changes for a procedure referenced in a view. |
Mismatched Implementation vs. Interface | If the interface and implementation do not match, the resource is impacted—for example, if you design an interface using Design Mode in the view editor Columns panel and you add or delete columns. |
Security Issue | A resource refers to another resource that you no longer have permission to access—for example, if the permission on a referenced data source is made more restrictive and you no longer have the required level of permission. |
Syntax Error | A syntax error is introduced in the resource—for example, if you type an invalid SQL statement and save it. |