Load Planview Enterprise Architecture data to Microsoft Fabric

Planview Portfolios is a project portfolio management platform that provides a REST API for accessing data regarding portfolios, projects, and work items. Everything needed to build a working Planview Enterprise Architecture → Microsoft Fabric pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Planview Enterprise Architecture to Microsoft Fabric pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Planview Enterprise Architecture API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Planview Enterprise Architecture API at a glance

These values come from the Planview Enterprise Architecture API documentation. Check them against the vendor's current reference before relying on them in production.

---

How do I authenticate with the Planview Enterprise Architecture API?

All requests require an OAuth2 access token or API token passed in the Authorization header using the format 'Bearer {token}'.

1. Get your credentials

1. Log in to your Planview Success Center or instance dashboard as an administrator. 2. Navigate to the Administration menu (often under Users or API Access sections). 3. Locate the API/OAuth settings tab (e.g., API Access, OAuth Clients, or My API Tokens). 4. Click 'Create New Token' or 'Create OAuth Client'. 5. Provide a name and assign necessary scopes/permissions. 6. Copy the generated API Token or Client ID/Secret immediately, as they are often only displayed once. Store these securely, such as in an environment variable or a vault system.

2. Add them to .dlt/secrets.toml

Copy
[sources.planview_enterprise_architecture_source]
api_key = "your_api_token_here"
# OR, if using OAuth flow:
client_id = "your_client_id_here"
client_secret = "your_client_secret_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Planview Enterprise Architecture data can I load into Microsoft Fabric?

These are the Planview Enterprise Architecture endpoints dlt can load into Microsoft Fabric:

---

How do I load only new Planview Enterprise Architecture records?

Planview Enterprise Architecture exposes offset on resources, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "resources", "endpoint": {
    "path": "resources",
    "data_selector": "data",
    "incremental": {"cursor_path": "offset", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Planview Enterprise Architecture pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading public-api/v1/work and v2.0/services/data/query from the Planview Enterprise Architecture API into Microsoft Fabric:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def planview_enterprise_architecture_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{your_account}.pvcloud.com/{your_server}/public-api/v1",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "resources", "endpoint": {"path": "resources", "data_selector": "data"}},
            {"name": "applications", "endpoint": {"path": "applications", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_planview_enterprise_architecture_to_fabric() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="planview_enterprise_architecture_pipeline",
        destination="fabric",
        dataset_name="planview_enterprise_architecture_data",
    )
    load_info = pipeline.run(planview_enterprise_architecture_source())
    print(load_info)


if __name__ == "__main__":
    load_planview_enterprise_architecture_to_fabric()

Run it with python planview_enterprise_architecture_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Planview Enterprise Architecture data in Microsoft Fabric?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("planview_enterprise_architecture_pipeline").dataset()
df = data.resources.df()
print(df.head())

SQL:

Copy
SELECT * FROM planview_enterprise_architecture_data.resources LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Planview Enterprise Architecture to Microsoft Fabric pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Planview Enterprise Architecture loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Planview Enterprise Architecture data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack