Workbook Data Mapping

Every Source Field
Lands in the Right Column.

RenderDraw Workbook data mapping connects fields from Excel uploads, Salesforce objects, SAP tables, and REST API responses to structured workbook columns — with transform rules, format conversion, and conditional logic applied at mapping time.

How It Works

Source Fields
→ Workbook Columns.

A data mapping definition is attached to a source connection. Every time the source delivers data — whether via Excel upload, scheduled ERP pull, or event-triggered Salesforce query — the mapping runs and writes the transformed values into the correct workbook columns.

Source Data Arrives

Excel upload, ERP sync, Salesforce trigger, REST response

Input

Field Extraction

Source headers or JSON keys are resolved to field list

Extract

Transform Rules Applied

Format conversion, calculation, conditional logic

Transform

Validation

Schema rules checked before write

Validate

Write to Workbook Column

Row created or updated with source attribution

Write
Supported Sources

Connect Any
Data Source You Use.

Excel Upload (.xlsx / .csv)

Upload a spreadsheet directly. RenderDraw reads all columns from the first sheet and presents a visual mapping UI. Subsequent uploads to the same source connection use the saved mapping automatically — no re-mapping required.

.xlsx .csv Auto-header detection

Salesforce Fields

Query any Salesforce object (Opportunity, Quote, Product, Account, Contact, custom objects) and map fields directly. Supports SOQL-style field path expressions for nested fields, e.g. Account.Name or PricebookEntry.UnitPrice.

Opportunity Quote Custom objects

SAP Tables

Connect to SAP via RFC or OData. Map table fields (MARA, EKPO, VBAP, etc.) to workbook columns. SAP field technical names are resolved to their human-readable labels automatically for the mapping UI.

RFC OData BAPI

REST API Responses

Map fields from any JSON REST endpoint. Use JSONPath expressions to extract nested values, array elements, or computed paths from the API response body. Authenticated endpoints supported via Bearer token or API key header.

JSONPath Bearer auth Any JSON API

AI Block Output

AI blocks return structured JSON from Claude, OpenAI, Gemini, or custom endpoints. Map the output fields — extracted quantities, identified materials, generated text — directly to workbook columns. The AI block's schema definition drives the field list in the mapping UI.

Claude OpenAI Structured output

SharePoint Lists

Read from SharePoint Lists or document library metadata. Map list columns to workbook columns. Supports lookup columns and person/group fields (resolved to display name + email).

Lists Document metadata Lookup columns
Transform Rules

Data Arrives Messy.
It Lands Structured.

Source data rarely arrives in the exact format your workbook schema expects. Transform rules let you reshape, reformat, and conditionally assign values at mapping time — without writing code.

Format Conversion

Convert between types. Parse a string like "$1,234.56" to a currency value. Convert a date string "01/15/2025" to ISO 8601. Strip currency symbols, commas, and whitespace automatically.

Calculation

Derive a workbook column from multiple source fields. Example: unit_cost = list_price * (1 - discount_pct / 100). Arithmetic, round, floor, ceil, and abs operators supported.

Conditional Mapping

Map to different workbook columns based on source field values. If item_type == "labor", write to the labor cost column; otherwise write to materials cost. Visual if/then rule builder, no SOQL or SQL required.

Lookup & Substitution

Replace source codes with human-readable labels using an inline lookup table or a reference to another workbook. Example: convert SAP material codes to product catalog names.

Validation

Bad Data Stops
At the Door.

Validation rules run after transforms, before any value is written to the workbook. Failed validations generate a mapping error event — logged in the audit trail, surfaced in the workflow run log, and optionally sent as a Teams or email alert.

Required Fields

Mark workbook columns as required. If a mapped source field arrives empty or null, the validation fails and the row is not created — instead, an error row is written to the Mapping Errors log for review.

Range Checks

Enforce numeric bounds on quantity and cost columns. A takeoff quantity of 0 or a unit cost of $0 can be flagged as suspicious and routed to an estimator for review before the workbook row is committed.

Cross-Field Rules

Validate relationships between columns. Example: if submission_date is populated, submitted_by must also be populated. Cross-field rules prevent partial records that break downstream reporting.

Connect Your First
Data Source Today.

Open RenderDraw, create a workbook, and configure your first data mapping in minutes.