Autodesk Construction Cloud Data Connector is an extraction service, not a live transactional mirror. It packages supported hub and project data into downloadable files that can feed business-intelligence tools, executive reporting, operational audits, and controlled downstream processes.
Access and scope change what the extract represents. Autodesk permits project administrators to extract data for a project they administer, while members with executive overview access can work at hub or project level. The request can include selected tools and an optional activity-data period, so two files created on the same day may still contain different business populations.
Reliable reporting requires an evidence chain from ACC through the completed extraction, downloaded package, transformation, semantic model, and published dashboard. Without that chain, a delayed schedule or stale Power BI refresh can present an old project condition with the visual confidence of current data.
Key decisions at a glance
- Choose project-level or hub-level Data Connector access according to the approved reporting scope, and limit executive overview access to accountable users.
- Record the included tools and activity-data window for every recurring extract because activity data is not included by default and its normal requested range is constrained.
- Design a consumer process for daily, weekly, or monthly schedules because Autodesk can pause schedules whose generated data is not downloaded within the documented period.
- Label Power BI reports with extract freshness because the Autodesk connector reads the last completed Data Connector extract rather than live ACC records.
- Troubleshoot extraction, download, transformation, refresh, and reconciliation as separate stages while preserving request IDs, timestamps, scope, schema, and row-count evidence.
Define the Extraction Scope, Owner, and Retention Need
Start with the decision the data must support. Name the hub or project, reporting owner, Data Connector operator, approved audience, included tools, activity-data requirement, storage location, retention period, and downstream model. Avoid extracting every available dataset simply because the default selection includes all tools.
Autodesk lists hub-level information such as users, roles, companies, projects, business units, and activated services, along with project-level data from supported construction tools. Maintain a schema inventory for the exact files and keys the reporting model consumes so an unused table does not expand exposure without a business purpose.
Activity data requires explicit selection. Autodesk's current help limits a normal requested activity window to 31 days within the last 12 months; if no specific period is supplied, the past day is used. Requests for older historical activity follow a separate Autodesk Support process and a time-limited extraction window.
- Document the business question, hub or project scope, included tools, audience, owner, and destination before running an extract.
- Limit executive overview access to people accountable for approved hub-wide reporting.
- Track each consumed file, table, key, and relationship against the current Autodesk data-schema documentation.
- State the requested activity-data window explicitly and keep historical requests separate from the recurring operational schedule.
Operate Scheduled Extractions as a Monitored Service
The Data Connector interface supports daily, weekly, and monthly schedules with a run cadence, time, start and end dates, selected tools, and activity-data scope. Create one owner for the request and another accountable consumer who confirms that completed data was collected and used.
Autodesk says completed extraction packages are available to download for 30 days. It can also pause daily or weekly schedules when generated data has not been downloaded in the prior 14 days, pause monthly schedules after two months without download, or pause a schedule after its original expiration date.
Monitor schedule state, last successful completion, next expected run, download confirmation, package checksum, and downstream load result. If higher-frequency or end-to-end automation is required, Autodesk points to the Data Connector Autodesk Platform Services API rather than implying that the browser schedule runs multiple times each day.
- Assign an extraction operator, business consumer, data owner, and technical escalation contact.
- Record schedule frequency, time zone, included datasets, activity period, start date, expiration date, and expected delivery time.
- Download or collect completed packages within the Autodesk availability window and verify the file before processing.
- Alert on paused schedules, missed completions, uncollected packages, checksum changes, and downstream load failures.
Make Power BI Freshness Visible to Report Consumers
Autodesk's Power BI guidance states that the Autodesk Construction Cloud connector reads the last Data Connector extract, not live hub or project data. Every report should display the source extract's completion time, downstream model refresh time, hub or project scope, and any known partial-load condition.
The documented prerequisites include executive overview access and either a manual Data Connector extraction within the last 30 days or a scheduled daily, weekly, or monthly extraction. The operator must also select the correct Autodesk server region before authenticating and choosing the account and tables in Power BI.
Sequence the schedules rather than setting them to the same minute. Autodesk recommends allowing several hours between the Data Connector scheduled extraction and the Power BI service refresh. Add a validation gate that compares a controlled set of ACC counts or record IDs with the report after each model change.
- Display source-extract and report-refresh timestamps where a decision-maker can see them.
- Confirm the correct region, hub or account, tables, credentials, workspace, and dataset before enabling scheduled refresh.
- Leave a deliberate buffer between Data Connector completion and the Power BI refresh window.
- Validate representative projects, issues, members, and other consumed records after transformations or schema changes.
Troubleshoot the Pipeline Without Confusing Its Stages
Classify the failure before retrying. Determine whether the request did not run, the schedule paused, processing has not completed, the package expired, download failed, the archive is incomplete, transformation rejected a schema or value, credentials blocked Power BI, the semantic model failed, or the dashboard loaded successfully but contains stale or mismatched scope.
Preserve the evidence for each stage: operator, access level, hub or project, request or job identifier, selected tools, activity window, schedule definition, status, timestamps, notification, package name and hash, schema version or change, row counts, transformation log, Power BI refresh history, and a sample of stable source identifiers.
ALLMSP can help construction organizations document Data Connector access, build monitoring and retention procedures, review transformations, expose freshness, preserve diagnostics, and coordinate Autodesk and Power BI escalation. Data ownership and the interpretation of project and financial results remain with the contractor's accountable leaders.
- Resume a paused schedule only after confirming its owner, expiration, download behavior, and continuing business purpose.
- Compare the current schema and included datasets before changing transformations to accommodate an unexpected file or column.
- Reconcile stable ACC identifiers and counts through the extract, model, and report instead of comparing only labels or totals.
- Close the incident after a fresh successful extraction and downstream refresh have both passed the documented validation sample.
Vendor documentation and ALLMSP resources
- Autodesk: Data Connector
- Autodesk: Data Connector Activity Data Schema
- Autodesk: ACC Data Schema
- Autodesk: Request Full Historical Activity Data
- Autodesk: Connect to Microsoft Power BI Desktop
- Autodesk Platform Services: Data Connector API
- ALLMSP Software Support
- ALLMSP Cybersecurity
- ALLMSP Construction and Contracting
- ALLMSP Autodesk Construction Cloud Support
- Contact ALLMSP
Frequently Asked Questions
What does Autodesk Construction Cloud Data Connector do?
It creates downloadable extracts of supported hub and project data for analysis in business-intelligence and other controlled downstream tools. It is an extraction workflow, not a live transactional replica of ACC.
Who can run an ACC Data Connector extraction?
Autodesk allows project administrators to extract data for a project they administer. Members with executive overview access can extract at hub or project level, so assign that wider access only to accountable reporting users.
Is activity data included in every Autodesk Data Connector extract?
No. Autodesk says activity data is not included by default. Select it explicitly and state the required period; the normal range cannot exceed 31 days and is limited to the most recent 12 months.
How long can a completed Data Connector package be downloaded?
Autodesk documents a 30-day download window for generated extraction files. Collect, validate, and store approved packages before expiration when the organization's retention or audit process requires them.
Why did an Autodesk Data Connector schedule pause?
Autodesk may pause daily or weekly schedules when generated data was not downloaded for 14 days, monthly schedules after two months without download, or any schedule after its original expiration date. Review the cause and owner before resuming.
Can the Data Connector browser schedule run several times per day?
The interface documents daily, weekly, and monthly schedules. Autodesk directs users to the Data Connector Autodesk Platform Services API when multiple daily runs or end-to-end automation are required.
Does the Autodesk Power BI connector read live ACC data?
No. Autodesk states that it pulls from the last completed Data Connector extract. The dashboard should show both the extract completion time and the Power BI model refresh time.
How should Data Connector and Power BI schedules be sequenced?
Run the ACC extraction first and leave a deliberate buffer before the Power BI refresh. Autodesk advises allowing several hours between them so the reporting service does not refresh against the previous extract.
What evidence should be captured for a failed ACC data refresh?
Capture access scope, hub or project, request ID, selected datasets, activity window, schedule, status and times, package name and hash, schema, row counts, transformation logs, Power BI credentials and refresh history, and sample source IDs.
How can ALLMSP support Autodesk Data Connector reporting?
ALLMSP can document access and scope, schedule and monitor extracts, design secure storage and retention, review schema-aware transformations, expose freshness in reports, build validation samples, and coordinate Autodesk or Power BI escalation.
