Skip to main content
Procore

Procore Analytics: Q4 2020 Releases

This announcement represents a single point in time. Future releases may impact the information below.
Feature Released: December 22, 2020


 

Procore Analytics: Q4 2020 Releases

The following sections outline the updates included in the Q4 release for Procore Analytics.

All Reports

  • Upgraded to support the Power BI November 2020 update.
  • Updated date formats to use the Power BI default format.
     Tip
    If you are located in a country outside of the United States and would like your Procore Analytics reports to respect your local date format instead of the Power BI default format, open each Procore Analytics report file in Power BI Desktop and save the files. This will apply the date settings from your local machine to the files. You can then publish them to the Power BI Service. See Upload Updated Procore Analytics Files to the Power BI Service.

Vendor Performance Report - New!

The Procore Analytics Vendor Performance Report is designed to provide users with high-level insights into the performance of their company's vendors. This report includes report pages that provide users with an overview of their company's vendors as well as commitment cost breakdowns, analysis of commitment change events, and vendor comparison data (including vendor response times for submittals, RFIs, and punch list items).

procore-analytics-q4-2020-ann-vendor-performance-vendor-overview.png

This sample report page was created using mock data for demonstration purposes only.
 

procore-analytics-q4-2020-ann-vendor-performance-response-time.png

This sample report page was created using mock data for demonstration purposes only.
 


Financials Budget Report

  • Advanced Forecasting Report Page:
    • Report page created. This report leverages the advanced forecasting feature in Procore and allows users to analyze projected costs.
      Note: In order for the Advanced Forecasting report page to function properly, advanced forecasting must be enabled and a budget forecast view titled 'Procore Standard Forecast' must be created with the default columns. See Enable Advanced Forecasting in Procore and About the Procore Standard Forecast View.

      procore-analytics-q4-2020-ann-financials-budget-advanced-forecasting.png

This sample report page was created using mock data for demonstration purposes only.
 

  • Advanced Forecasting Over Time Report Page:
    • Report page created. This report leverages the advanced forecasting budget snapshot feature in Procore and allows users to analyze budget forecast snapshots over time.

      procore-analytics-q4-2020-ann-financials-budget-advanced-forecasting-over-time.png

This sample report page was created using mock data for demonstration purposes only.
 


Owner Report

  • Advanced Forecasting Report Page:
    • Report page created. This report leverages the advanced forecasting feature in Procore and allows users to analyze projected costs.
      Note: In order for the Advanced Forecasting report page to function properly, advanced forecasting must be enabled and a budget forecast view titled 'Procore Standard Forecast' must be created with the default columns. See Enable Advanced Forecasting in Procore and About the Procore Standard Forecast View.

      procore-analytics-q4-2020-ann-owner-advanced-forecasting.png

This sample report page was created using mock data for demonstration purposes only.
 

  • Advanced Forecasting Over Time Report Page:
    • Report page created. This report leverages the advanced forecasting budget snapshot feature in Procore and allows users to analyze budget forecast snapshots over time.

      procore-analytics-q4-2020-ann-owner-advanced-forecasting-over-time.png

 

This sample report page was created using mock data for demonstration purposes only.


Project Management Report

  • Correspondence Insights Report Page:
    • Report page created. This report leverages the Correspondence tool in Procore and allows users to analyze correspondence data.

      procore-analytics-q4-2020-ann-correspondence-insights.png

This sample report page was created using mock data for demonstration purposes only.
 


Daily Log Report

  • Visitor Report Page:
    • Custom Field Name available in filter options for Visitor Log items created in Procore's Daily Log tool.
    • Custom Field Value available in filter options for Visitor Log items created in Procore's Daily Log tool.
  • Notes Report Page:
    • Custom Field Name available in filter options for Notes Log items created in Procore's Daily Log tool.
    • Custom Field Value available in filter options for Notes Log items created in Procore's Daily Log tool.

Quality and Safety Report

  • Incidents and Incident Details Report Page:
    • Custom Field Name available in filter options for incidents created in Procore's Incidents tool.
    • Custom Field Value available in filter options for incidents created in Procore's Incidents tool.
  • Inspection Insights, Inspection Quality, Inspection Compliance, Inspection Closeout, and Inspections Report Pages:
    • Custom Field Name available in filter options for inspections created in Procore's Inspections tool.
    • Custom Field Value available in filter options for inspections created in Procore's Inspections tool.

Database Changes with Procore Data Extract

See all database changes to Procore Data Extract in the 'Change Log' tab here.  

New Reportable Field from Procore's Daily Log Tool
  • Added: New reportable field in the DailyLogNote table based on user-defined custom fields for the Notes Log in the project's Daily Log tool:
    • custom_fields
New SQL View for Procore's Daily Log Tool
  • Added: New SQL view called vwDailyLogNoteCustomField that reports on custom field data for the Notes Log in the project's Daily Log tool in the following columns:
    • DailyLogNoteID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
New Tables and Reportable Fields from Procore's Correspondence Tool

Note: Reportable data from correspondence items that are marked 'Private' (where private = 'true') excludes identifiable information.

  • Added: New Correspondence table and reportable fields:
    • id
    • generic_tool_id
    • CompanyID
    • ProjectID
    • closed_at
    • created_at
    • updated_at
    • description
    • due_date
    • issued_at
    • position
    • full_position
    • private
    • schedule_impact_status
    • schedule_impact_value
    • cost_impact_status
    • cost_impact_value
    • status
    • title
    • created_by_name
    • created_by_company_id
    • created_by_contacts_company_name
    • created_by_login
    • received_from_name
    • received_from_company_id
    • received_from_contacts_company_name
    • received_from_login
    • location_id
    • location_name
    • location_node_name
    • location_parent_id
    • location_created_at
    • location_updated_at
    • cost_code_id
    • cost_code_full_code
    • cost_code_name
    • specification_section_id
    • specification_section_number
    • specification_section_description
    • specification_section_label
    • specification_section_current_revision_id
    • trade_id
    • trade_name
    • trade_active
    • trade_updated_at
    • generic_tool_abbreviation
    • DateUpdated
  • Added: New CorrespondenceAssignee table and reportable fields:
    • id
    • CorrespondenceID
    • CompanyID
    • ProjectID
    • created_at
    • updated_at
    • login
    • name
    • contacts_company_id
    • contacts_company_name
    • DateUpdated
  • Added: New CorrespondenceAttachment table and reportable fields:
    • id
    • CorrespondenceID
    • CompanyID
    • ProjectID
    • filename
    • created_at
    • updated_at
    • DateUpdated
  • Added: New CorrespondenceDistributionMember table and reportable fields:
    • id
    • CorrespondenceID
    • CompanyID
    • ProjectID
    • created_at
    • updated_at
    • login
    • name
    • contacts_company_id
    • contacts_company_name
    • DateUpdated
  • Added: New CorrespondenceResponse table and reportable fields:
    • id
    • CorrespondenceID
    • CompanyID
    • ProjectID
    • notes
    • created_at
    • updated_at
    • official
    • position
    • status
    • created_by_name
    • created_by_company_id
    • created_by_contacts_company_name
    • created_by_login
    • DateUpdated
  • Added: New CorrespondenceResponseAttachment table and reportable fields:
    • id
    • CorrespondenceID
    • CompanyID
    • ProjectID
    • CorrespondenceResponseID
    • filename
    • created_at
    • updated_at
    • DateUpdated
New Reportable Field from Procore's Inspections Tool
  • Added: New reportable field in the Checklist table based on user-defined custom fields for the project's Inspections tool:
    • custom_fields
New SQL View for Procore's Inspections Tool
  • Added: New SQL view called vwChecklistCustomField that reports on custom field data for the project's Inspections tool in the following columns:
    • ChecklistID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
New Reportable Field from Procore's Punch List Tool
  • Added: New reportable field in the PunchItem table based on user-defined custom fields for the project's Punch List tool:
    • custom_fields
New SQL View for Procore's Punch List Tool
  • Added: New SQL view called vwPunchItemCustomField that reports on custom field data for the project's Punch List tool in the following columns:
    • PunchItemID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
New Reportable Field from Procore's Daily Log Tool
  • Added: New reportable field in the DailyLogVisitor table based on user-defined custom fields for the Visitor's Log in the project's Daily Log tool:
    • custom_fields
New SQL View for Procore's Daily Log Tool
  • Added: New SQL view called vwDailyLogVisitorCustomField that reports on custom field data for the Visitor's Log in the project's Daily Log tool in the following columns:
    • DailyLogVisitorID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
New Tables and Reportable Fields from Procore's Incidents Tool
  • Added: New reportable field in the Incident table:
    • custom_fields
  • Added: New reportable fields in the IncidentEnvironmental table:
    • custom_fields
    • recordable
  • Added: New reportable fields in the IncidentInjury table:
    • custom_fields
    • affliction_type_id
    • affliction_type_name
    • affliction_type_active
    • affliction_type_global
    • affliction_type_created_at
    • affliction_type_updated_at
  • Added: New reportable fields in the IncidentInjuryAffliction table:
    • affliction_type_active
    • affliction_type_created_at
    • affliction_type_updated_at
  • Added: New reportable fields in the IncidentNearMiss table:
    • custom_fields
    • affected_party_id
    • affected_party_name
    • recordable
    • updated_at
  • Added: New reportable fields in the IncidentPropertyDamage table:
    • custom_fields
    • recordable
  • Added: New reportable fields in the IncidentWitnessStatement table:
    • custom_fields
    • incident_id
  • Added: New IncidentAction table and reportable fields:
    • id
    • incident_id
    • action_type_id
    • action_type_name
    • action_type_active
    • action_type_global
    • action_type_created_at
    • action_type_updated_at
    • description
    • description_plain_text
    • created_at
    • deleted_at
    • updated_at
    • observation_id
    • custom_fields
    • IncidentID
    • ProjectID
    • CompanyID
    • DateUpdated
  • Added: New IncidentActionAttachment table and reportable fields:
    • id
    • url
    • thumbnail_url
    • name
    • content_type
    • IncidentActionID
    • IncidentID
    • ProjectID
    • CompanyID
    • DateUpdated
  • Added: New IncidentAttachment table and reportable fields:
    • id
    • url
    • thumbnail_url
    • name
    • content_type
    • IncidentID
    • ProjectID
    • CompanyID
    • DateUpdated
  • Added: New IncidentInjuryBodyPart table and reportable fields:
    • id
    • name
    • selectable
    • created_at
    • updated_at
    • parent_id
    • IncidentInjuryID
    • IncidentID
    • ProjectID
    • CompanyID
    • DateUpdated
  • Added: New IncidentWitnessStatementAttachment table and reportable fields:
    • id
    • url
    • thumbnail_url
    • name
    • content_type
    • IncidentWitnessID
    • IncidentID
    • ProjectID
    • CompanyID
    • DateUpdated
New SQL Views for Procore's Incidents Tool
  • Added: New SQL view called vwIncidentActionCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentActionID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
  • Added: New SQL view called vwIncidentCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
  • Added: New SQL view called vwIncidentEnvironmentalCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentEnvironmentalID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
  • Added: New SQL view called vwIncidentInjuryCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentInjuryID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
  • Added: New SQL view called vwIncidentNearMissCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentNearMissID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
  • Added: New SQL view called vwIncidentPropertyDamageCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentPropertyDamageID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
  • Added: New SQL view called vwIncidentWitnessStatementCustomField that reports on custom field data for the project's Incidents tool in the following columns:
    • IncidentWitnessStatementID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id
New Reportable Field from Procore's Submittals Tool
  • Added: New reportable field in the Submittal table based on user-defined custom fields for the project's Submittals tool:
    • custom_fields
New SQL Views for Procore's Submittals Tool
  • Added: New SQL view called vwSubmittalCustomField that reports on custom field data for the project's Submittals tool in the following columns:
    • SubmittalID
    • ProjectID
    • company_id
    • custom_field_key
    • custom_field_key_label
    • custom_field_id
    • custom_field_data_type
    • custom_field_value
    • custom_field_option_id

 

If you would like to ask questions or share any feedback, please contact analyticssupport@procore.com.