Skip to content
CPQ DevKit™
Back to blog

Sync Oracle CPQ into a clean local project structure

The fastest way to work on Oracle CPQ is to treat your CPQ configuration like a normal codebase: sync it locally, version it in Git, and review changes with diffs.

CPQ DevKit™ for Oracle gives you exactly that workflow with “GET ALL …” commands that pull CPQ objects into a predictable folder layout.

Your folder structure is configurable

project.config.jsonc controls where each CPQ object type lands locally:

Once your folders match your team’s conventions, the sync commands write into those locations consistently.

Open the Command Palette (Cmd/Ctrl+Shift+P) and run:

  • CPQ DevKit™ for Oracle: Get all Data and Metadata (metadata catalog used by the extension for smarter editing)
  • CPQ DevKit™ for Oracle: GET ALL Tables (writes tables to your tables folder and a small index file under .cpqdevkit/)
  • CPQ DevKit™ for Oracle: GET ALL BML (writes util/commerce functions into your functions folders)
  • CPQ DevKit™ for Oracle: GET ALL Files (downloads File Manager assets into your files folder)

Many of these are also available from the Explorer context menu when you right‑click your workspace folder.

What “GET ALL Tables” produces (and why it matters)

When you download Data Tables, CPQ DevKit writes:

  • Table JSON files under your tables folder (example: _tables/<folderVar>/<TableName>.json)
  • A Data Table index at .cpqdevkit/ocpq/data-tables.json

That index is used by navigation features (like “Go to Definition” from BMQL strings inside BML).

Keep secrets out of Git

Your Oracle CPQ credentials live in .cpqdevkit/developer.config.jsonc. CPQ DevKit’s setup command adds .cpqdevkit/** to .gitignore automatically—keep it that way and commit only project.config.jsonc (and your downloaded CPQ assets) to version control.