Anaplan functions#

The Anaplan connector contributes a single worksheet function, ANAPLANINPUT, which marks a cell as a write-back input so its value is posted to the matching Anaplan module cell during contribution processing.

Unlike the rest of the function surface, ANAPLANINPUT has no dotted canonical alias. There is no RW.Anaplan.* name in the current build; ANAPLANINPUT is the function's only registered name.

ANAPLANINPUT#

Signature

=ANAPLANINPUT(inputCell, [tuplePart1], [tuplePart2], ...)

How the write-back actually finds its target#

This is the part worth understanding, because it explains every failure mode.

1. The formula marks the cell as an input, so it is processed during input submission, not during the report-output pass.
2. During report generation, Reportworq resolves the Anaplan tuple behind the input cell, which is the workspace, model, module, dimensions and members that make up that intersection, and stores it as a worksheet custom property named ANAPLANINPUT_{row}_{col}. This is the "breadcrumb".
3. At submission, the breadcrumb is what Reportworq posts against. Inputs are grouped by their workspace | model | module key, and each group is posted as a single mutation request.
4. On success the formula cell is cleared.

The breadcrumb is only written when the input cell sits on a cell that an Anaplan view generated. If the cell does not point at an Anaplan cell, report generation logs an error for that input, and there will be nothing to post later.

The trailing tuple arguments are a trap#

The optional tuplePart arguments do not do what their name suggests.

They are recorded, and their presence suppresses automatic breadcrumb generation for that cell. But in the current implementation the write-back vector is built only from the breadcrumb. The arguments are never used to construct it.

The result is that supplying them turns off the only mechanism that would have found the target, and the input then has no tuple to post against. Omit them unless you know a breadcrumb already exists for the cell.

This differs from the Workday Adaptive equivalent, RW.Adaptive.Input, where explicit tuple parts are used to build the vector.

Examples#

=ANAPLANINPUT(B5)
=ANAPLANINPUT(D12)

The simple form is the correct form.

When an argument is wrong#

Placement#

Place ANAPLANINPUT on a cell that a refreshed Anaplan view produced, so Reportworq can capture the tuple behind it. The formula relies on the workbook being a recognized Anaplan report.

Keep related inputs in the same report run: multiple input cells targeting the same workspace, model and module are batched into one post.

Keep write-back formulas in hidden rows or columns. Like the other write-back families, they render as #NAME in a contributor's form, so their rows and columns are hidden by design.

Notes and limits#

• The function is inert in desktop Excel.
• It ships with the Anaplan connector plugin. A specific introducing version is not determinable from the current source.

Related pages#

• Functions overview: which one do I use
• Contribution functions for the input form the write-back sits behind.
• Workday Adaptive functions for the equivalent tuple-based write-back, which behaves differently.
• Connector catalog for the Anaplan connection setup.