Skip to content
PlaidCloud

Anaplan: Read View

Description

Section titled “Description”

Reads data from a saved Anaplan view over your Anaplan connection, through Anaplan’s large-volume read-request path. The view is read exactly as it was saved — there’s no ad-hoc row, column, or page selection on this step. To read a different slice, save a different view in Anaplan.

This step appears in the step menu under Anaplan.

The step reaches Anaplan cloud-direct over its Integration API — there is no on-premises agent path.

Configuration

Section titled “Configuration”

Source and Target

Section titled “Source and Target”
Field Required Notes
Anaplan Connection Yes The Anaplan connection to read through.
Environment Yes The connection’s environment.
Workspace No Overrides the workspace ID saved on the connection. Discovered live from the connection, or typed by hand.
Model No Overrides the model ID saved on the connection. Discovered live once a workspace is chosen, or typed by hand.
View Yes The saved Anaplan view to read. Discovered live once a model is chosen, or typed by hand.
Poll Attempts Yes Default 120. How many times to poll the read request for completion before the step refuses, naming the request ID. It never silently submits a second request.
Poll Interval (seconds) Yes Default 5. Seconds to wait between polls.
Target Table Yes The table the returned view lands in.

What This Step Cannot Represent

Section titled “What This Step Cannot Represent”
Limitation What it means
No slice control The view is read exactly as saved — no row, column, or page selection. Anaplan’s page selector is documented only on its synchronous preview endpoint; the large-volume read-request body this step posts takes an export type and nothing else. Build a different saved view — commonly a Boolean line item plus a filter — to read a different slice.
Declared types land only when Line Items is on Columns With Line Items on the view’s columns axis, each data column lands typed from its line item’s declared Anaplan format (Number, Text, Boolean, Date, Time Period, or List). With Line Items on rows (an ordinary P&L layout) or absent from the view entirely, every data column lands as text instead, with a named warning — a data column would otherwise span many line items, and therefore many formats, while a table column holds exactly one type.
Page-selector values aren’t landed as columns A view’s saved page-selector members ride along in the CSV header and are consumed there — they don’t appear as columns in the target table.
Ambiguous numbers refuse rather than guess A Number-declared value carrying thousands separators, or one that reads equally as a plain decimal or a European-style rendering (for example 1.234), is refused by name rather than parsed — unless another value in the same column settles which reading is right. This read path has no locale field to resolve the ambiguity against. A value that does parse lands at full precision, with no rounding error, and a blank cell always lands as an empty value.
Empty view lands empty, with a warning A saved view whose filter matches nothing replaces the target table with an empty one and warns — that’s an ordinary outcome, not a failure. The exception is a view with no dimension on its rows axis: there’s no row-label corner to verify an empty result against, so the step refuses rather than risk emptying the table on a misread header.
Read-only Nothing is ever written back to Anaplan.
Section titled “Related”