Whenever data functions, IronPython scripts, JavaScripts, or custom queries are trusted in an analysis file, the file gets a "TrustedScripts" property assigned. But the same scripts and data functions can be present in multiple analysis files. A script or data function may be trusted in one analysis file explicitly, and if the exact same script or data function is not explicitly trusted in another analysis file, they are still considered to be trusted in the library since the script hash matches the trust hash generated for the file where the script of data function is trusted.
Sometimes the script or data function trust is lost for such .dxp copies and users get script ordata function untrusted warnings when:
- The script in the original file (where the script was trusted) changes
- The original file is deleted
- The user no longer has access to the original file (where the script was trusted, and where the script trust property is found). For example, if library permissions for the folder where the original file is saved are changed or the original file is moved to other location where users do not have access.
In such cases, there is a need to identify such dependent analysis and their scripts and data functions need to be trusted by an authorized user in order to generate the trustedscripts property for those analysis files.