Comprehensive and Detailed Explanation From Exact Extract:
To import a Workday custom report into the Prism Analytics Data Catalog, specific configurations are required to ensure the report is accessible and usable. According to the official Workday Prism Analytics study path documents, in addition to enabling the report as a web service and enabling it for Prism Analytics, the report must be shared with or owned by the user who is performing the import. This security requirement ensures that only authorized users can access and import the report into the Data Catalog, aligning with Workday's configurable security model. The user must either be the owner of the report or have it shared with them through appropriate security permissions (e.g., via a security group or direct sharing).
The other options are incorrect:
* A. It must be imported via sFTP: Custom reports are imported directly through Workday's web service integration, not via sFTP, which is typically used for file-based data sources.
* B. It must be built as a matrix report: There is no requirement for the report to be a matrix report; Prism Analytics supports various report types, including advanced and simple reports, as long as they are properly configured.
* D. It must be tagged with a Prism Analytics report tag: Tagging is not a mandatory step for importing a report into the Data Catalog, though it may be used for organizational purposes.
Ensuring that the report is shared with or owned by the importing user is a critical step to maintain security and governance during the integration process.
References:
Workday Prism Analytics Study Path Documents, Section: Integrating Prism with Workday Reports, Topic:
Importing Custom Reports into the Data Catalog
Workday Prism Analytics Training Guide, Module: Datasets and Data Sources, Subtopic: Security Requirements for Report Integration