PayPal Transactions to Yellowfin Integration

How Datrise loads PayPal Transactions into Yellowfin

Datrise syncs PayPal Transactions's transactions, payers, balances, fees, refunds, and currency conversions into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

PayPal Transactions: PayPal transaction history and settlement detail.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How PayPal Transactions entities map to Yellowfin

PayPal Transactions entity	Yellowfin object	Notes
transactions	`paypal_transaction_transactions`	id PK · custom fields → flattened columns
payers	`paypal_transaction_payers`	id PK · linked to paypal_transaction_transactions
balances	`paypal_transaction_balances`	id PK · linked to paypal_transaction_transactions
fees	`paypal_transaction_fees`	id PK · linked to paypal_transaction_transactions

FAQ

How does Datrise handle PayPal Transactions's custom fields in Yellowfin?

Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Yellowfin types.

How does the PayPal Transactions to Yellowfin sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect PayPal Transactions to Yellowfin the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.