About Procore Analytics 2.0
- Last updated
- Save as PDF
Table of Contents
Overview
Details
Common Questions
Answer
Below is a list of general FAQs for Analytics 2.0.
- Why is my data still not showing after generating a token and making a connection?
- How frequent is the data refresh?
- Why isn't my budget snapshot table getting updated?
- How do I connect to Procore Analytics 2.0?
- Will customers on Data Extract only today have to migrate to 2.0?
- Do I still need Power BI licenses to access PA 2.0?
- How do I update the custom reports that were developed in-house?
- How will the process for copying data to my data warehouse be affected by Procore Analytics 2.0?
- How will Procore built customer reports get migrated to 2.0?
- What is the plan for deprecating Procore Analytics 1.0?
- Can I keep using 2.0 after the open beta period ends?
Why is my data still not showing after generating a token and making a connection?
Your data can take up to 24 hours to show for the first time.
How frequent is the data refresh?
Data refreshes for most tables throughout the day on an hourly basis. The Budget Snapshot table refreshes data daily at 8:30 a.m. (CST).
Why isn't my Budget Snapshot table getting updated?
The Budget Snapshot table currently updates on a daily basis at 8:30 a.m. (CST). In the future, updates will happen hourly like the other tables.
How do I connect to Procore Analytics 2.0?
Analytics 2.0 can be accessed in several ways. The most common way would be to connect in Power BI. See Getting Started With Procore Analytics 2.0.
Will customers on Data Extract have to migrate to Procore Analytics 2.0?
Yes, customers on Data Extract will need to move over to Procore Analytics 2.0, now called Cloud Connector (powered by Delta Share). Procore Analytics 2.0 will also include PowerBI reports as a feature that customers are not required to use, but they will be available for all customers with Procore Analytics 2.0.
Do I still need Power BI licenses to access Procore Analytics 2.0?
No, you do not need Power BI to use Procore Analytics. Power BI licenses will still be required to share out-of-the-box Power BI reports, however, you can still connect to Procore Analytics with nearly any application or data store.
How do I update the custom reports that were developed in-house?
Any existing connections to Analytics 1.0 (Azure SQL) must be changed. Several report tables and columns have been renamed. To view field mapping between Analytics 1.0 and 2.0, review the 'Data Exploration' tab within the Procore Analytics 2.0 tool menu.
How will the process for copying data to my data warehouse be affected by 2.0?
Procore Analytics 2.0 now uses Databricks Delta Sharing for data access. You can find out more about delta sharing here.
How will Procore-built customer reports get migrated to 2.0?
Existing custom reports will not be affected before 1.0 depreciation. Guidance for report migration services will be provided closer to GA. Report migration services will not be available prior to GA. Customers looking to self-migrate reports sooner can refer to Getting Started with Procore Analytics 2.0.
What is the plan for deprecating Procore Analytics 1.0?
Customers have 12 months after 2.0 goes GA to migrate off of 1.0 and onto Analytics 2.0. Analytics 1.0 has a tentative deprecation near the end of Q3 2025.
Partner Considerations
Please review the following partner considerations below:
Consulting Partners
- Permissions: When using Procore Analytics 2.0, the token you generate will pull data from all companies that your Procore login has access to. If you work with multiple customers, you need to create a separate Procore login for each customer to avoid inadvertently sharing data across customers. Do not use the same login (token) for different customers.
- Support: The partner must provide support related to their datasets and reports.
App Partners
- Bulk access: Whether you expose your data via API or a Power BI custom connector, you’ll need a security model that returns data across all projects with each endpoint. Power BI is geared towards bulk data ingestion and will not be able to scale if it needs to iterate datasets by a project or other unique identifier.
- Multiple datasets: It's common to expose separate datasets for each reportable data entity. Each of these should support the same security model and return data in bulk.
- Security: You’ll need to implement a solution that enables bulk reading of the data with a single set of secure credentials.
- Power BI template: Your Power BI template should work out of the box with any customer who uses it. The Power BI template is loaded into the client’s Power BI tenant. They will configure the datasets with the credentials you provide them.
More