Skip to main content

Report Connector Release Notes v1

Emily Yeomans
  • Updated

Things to Know

  • Information on this page is subject to change. This page was last updated January 16, 2025.
  • New data is not available in the Report Connector until the UAT or PROD release dates.

Release Summary

Here's a quick overview of the updates in this release:

  • New view added for raw SP Form JSON.
  • Retired outdated pipelines.
  • New view for tracking account activity.
  • Improved backend for field reporting.
  • Added infrastructure for SP Classic report package.
  • New views for spreadsheet-style SP Form data.

Release Dates and Downtime

Release dates are subject to change. Release date changes will be noted in the Change Log below.

Downtime required: None

Environment

Release Time (PST) *Convert to your timezone
UAT-US Completed incrementally throughout Q4-24
UAT-SG January 15th @ 12:00am
UAT-CA January 15th @ 12:00am
UAT-AU January 15th @ 12:00am
Prod-SG January 27th @ 12:00am
Prod-CA January 27th @ 12:00am
Prod-AU January 27th @ 12:00am
Prod-US January 29th @ 12:00am

Change Log:

Jan 13: Revised the wording of several bullets below to enhance clarity and explanation.

Jan 15: Revised UAT deployment dates.

Jan 16: Removed one item from this release.

Detailed Release Notes

New: Platform and Admin

  • The Admin Module now logs activities related to user accounts, creating an audit trail for actions like account creation and deactivation. These tracked actions are accessible through a new view, PUBLISHED_ADMIN.DIM_ACCOUNT_AUDIT, in the Admin schema.

New: SP Classic/SP 3.9

  • Preliminary work was completed to extend Report Connector to SP Classic/SP3.9 customers. This will eventually be available in a new schema, PUBLISHED_SPC. This schema will contain data copied from the off-platform SPc databases. The views in this schema are designed to replicate the reports available in Data Connect, providing an alternative for off-platform SP customers to modernize their data extraction processes without immediately moving to the new platform or switching to SP4.
    • The initial set of views includes all major non-list reports and some of the most common custom SPc Data Connect reports. Additional views will be added to ensure continuity for all necessary Data Connect reports.
  • As part of the ongoing effort to replicate Data Connect in Report Connector, new views have been added to support the Standard SP Report Package add-on.

New: SP 4.0

  • A new view, PUBLISHED_SP.DIM_DATA_JSON, has been added to the SP schema as an alternative way to access the raw JSON for SP Forms (Proposal, Award, or Subaward). Previously, this data was only available in the FCT_% views, in a column labeled DOC_RAW. However, downloading the FCT views with this large JSON data can be cumbersome.
    • To improve accessibility, the DOC_RAW column will eventually be removed from the FCT views. At that point, the new view, DIM_DATA_JSON, will become the sole source for accessing the raw JSON for SP Forms. (DARE-2106)
    • This version breaks down the information into shorter, more digestible sentences while maintaining clarity and flow.

  • We’ve enhanced the backend processes of Report Connector to improve how SP Form content is managed. This mapping is now available in the DIM_FCT_MAPPING view.

  • To provide all SP Form content in a tabular-style spreadsheet format, three new views have been added to the PUBLISHED_SP schema:
      • PUBLISHED_SP.DIM_PROPOSALS_FORM_ELEMENTS
      • PUBLISHED_SP.DIM_AWARDS_FORM_ELEMENTS
      • PUBLISHED_SP.DIM_SUBAWARDS_FORM_ELEMENTS
  • These views include most of the content entered into all three Form types, whether they are tied to standard objects (questions defined in the SP4 Data Dictionary) or non-standard/custom objects. Non-standard objects are any Form items with values not aligned with the predefined values in the Data Dictionary. Previously, accessing non-standard data required parsing raw JSON. These new views offer a more user-friendly format, eliminating the need for parsing.

Please note: Multi-select Form Objects are not currently covered as their branching content cannot be contained in a tabular format in parallel with single-select objects.

(Ref ID: V2.6)

Related articles