Planning & Budgeting Sync Datasets Now Support Date Filters, Hierarchy Controls, and Sorting

NetSuite has expanded the customization surface for Planning and Budgeting Sync datasets (accessed via NetSuite EPM > Planning and Budgeting > Manage Datasets). These changes affect both transactional and metadata datasets and control how data is filtered, structured, and exported to your Planning and Budgeting application.

Note: The source page reads as feature documentation rather than a versioned release note. Oracle does not specify which release introduced these capabilities. Verify availability in your account's release notes or EPM feature list.

What changed

Add-On Filters for transactional datasets

• New date-based filters on transactional datasets let you scope sync execution to records created or modified within a rolling window: Created or Updated Since N Days Ago and Created Since N Days Ago.
• These filters do not alter the dataset configuration itself — they only restrict the result set at execution time.

Hierarchy Settings for metadata datasets

• Top Level Parent Value — overrides the default top-level parent name in the exported hierarchy.
• Exclude Upper Level Hierarchy Members — omits upper-level members from the hierarchy. Applies only to Accounts and Item metadata datasets.
• Return Hierarchy Based Only on Data in This Search — restricts the hierarchy output to records present in the customized dataset. Checked by default and non-clearable for metadata datasets; unavailable for transactional datasets.
• Category Prefix — sets a custom prefix per metadata dataset. Must be unique across datasets.

Parent-Level Data Storage

The Data Storage for Parent Record setting controls the Data Storage column value on exported parent records. Options:

• Never Share — parent is set to Never Share.
• Dynamic Calc — parent is set to Dynamic Calc.
• Store — parent is set to Store.
• Store/Never Share — if the parent has only one child, the value is Never Share; otherwise Store.

All child records default to Store regardless of this setting.

Member Name and Alias Affixes

• Custom prefix or suffix for member names via Member Name Affix Value and Custom Affix for Member Name. Default is the P_ prefix.
• Custom prefix or suffix for the alias column via Alias Affix Value and Custom Affix for Alias. Default is the Total_ prefix.

Sorting

Metadata can now be sorted per hierarchy level by one of:

• Alias (alphabetical)
• Member Internal ID (numeric — also the default if no selection is made)
• Member Name (alphabetical)

Hide Filters in Data Exchange

• Filters configured in Data Exchange can be selectively hidden. Hidden filters still execute with their default values.
• Certain filter types (e.g., is not empty) may not appear in this section due to how NetSuite handles them internally.

What to do

1. Confirm availability. Oracle does not specify the release version for this page. Check your account's release notes or enable the EPM feature bundle to verify these options exist in your environment.
2. Review existing dataset configurations. Navigate to NetSuite EPM > Planning and Budgeting > Manage Datasets and click Customize (or Edit if previously customized) on each dataset.
3. Set date filters on transactional datasets if you want to limit sync volume to a rolling window rather than the full dataset.
4. Audit Data Storage settings. If you rely on specific aggregation behavior in Planning and Budgeting, verify that the parent-level Data Storage value (Never Share, Dynamic Calc, Store, or Store/Never Share) matches your calculation model.
5. Ensure unique category prefixes. If you have multiple metadata datasets, confirm each has a distinct Category Prefix to avoid collisions.
6. Review hidden filters in Data Exchange. Hidden filters still run with defaults — make sure the default values produce the expected results in your Planning and Budgeting application.