Analytics 2.0 General FAQ
In Beta
Answer
Below is a list of general FAQs for the Open Beta release of Analytics 2.0.
- How do I join the open beta if I accidentally declined the invitation?
- As an open beta participant, what is Procore expecting of me?
- How frequent is the data refresh?
- 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 joining the open beta impact Procore Analytics 1.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?
How do I join the open beta if I accidentally declined the invitation?
Reach out to your Customer Success Manager to get reactivated in the next week's release, typically on a Tuesday or Wednesday.
As an open beta participant, what is Procore expecting of me?
Your optional feedback is welcome. Please share your experience with Analytics 2.0 within the Analytics 2.0 Beta Community Group.
How frequent is the data refresh?
Data refreshes throughout the day on an hourly basis.
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 Analytics2.0?
Power BI licenses will still be required to share Power BI reports.
How do I update the custom reports that were developed in-house?
Procore Analytics 2.0 now uses Databricks Delta Sharing. Any existing connections to Analytics 1.0 (Azure SQL) must be changed. Several report tables and columns have been renamed. The basic changes you will need to make include updating reports to use the new Delta Sharing connector, updating table and column names, and updating visuals that may have been broken after you made the changes mentioned above. Depending on how your report was built, there may be additional considerations. See Getting Started With Procore Analytics 2.0.
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 joining the open beta impact Procore Analytics 1.0?
Procore Analytics 1.0 and 2.0 are completely independent of each other. Your participation in the 2.0 beta will not impact 1.0 in any way.
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.
Can I keep using 2.0 after the open beta period ends?
Yes, if you would like to continue using 2.0 after open beta ends, you will have 90 days to sign an agreement for the new product (to replace your existing agreement for 1.0).
For any further questions or concerns regarding Procore Analytics 2.0, please reach out to the Analytics 2.0 Beta Community Group.