Table of Contents
HubSpot lets you archive properties (hide from the UI but keep stored values) and, separately, delete them (remove definitively). Both can affect a data source that referenced the property.
Archived property #
- The property still exists in HubSpot, so the OData feed still returns its values for existing records.
- If you open the connector after archiving, the property still shows in your data source’s selection — it’s grayed out but Power BI refresh continues to work.
- New records don’t have a value for the property. They return null for the column.
Deleted property #
- The HubSpot API stops returning the property entirely.
- The connector detects this on the next refresh attempt and returns an error referencing the missing property.
- Fix: open the data source in the connector, uncheck the deleted property in the object’s property checklist, save, and re-run the Power BI refresh.
Custom properties tied to integrations or workflows may be deleted unexpectedly when those integrations are removed. If a refresh starts failing after an unrelated HubSpot change, archived/deleted properties are a likely first culprit.
