Security considerations

• The canUseLineage capability must be granted for the caller and for the package.
• The caller must have read access to the authoredReport or package.
• If object security has been specified in the published Framework Manager model specification, then users will not see objects in the response for which they are not granted access.

Also note the following limitations before using lineage.

• Evaluation of macros contained within expressions is not currently supported.
• The metadataService implementation reports lineage back to the data source in the Framework Manager model but no further.
• The caller must resolve any required model prompts, and data source connection and signon parameters that may be encountered beforehand and specify them in the parameters section of the request.
• The response is returned by default in base64 encoding, although support for MIME and MIME Compressed encodings are available.
• The response does not preserve the namespace hierarchy from the originating Framework Manager model in the context hierarchy of the lineage objects. Essentially, the namespaces are flattened.