Passer au contenu principal


Adaptive Insights French


2019.1 Release Notes for integration.

Account and Attribute Metadata Loaders

New Account Metadata Loader and Attribute Metadata Loader for creating or updating GL accounts and attributes. Like other loaders, you map source columns to planning properties. 

See Create a Planning Account Loader and Create a Planning Attribute Loader.

Metadata Bulk APIs

You can synchronize metadata defined in an external system to Adaptive Planning on a regular, scheduled basis:

  • updateAccounts API: GL accounts only
  • updateAttributes API: Attributes and attribute values

See updateAccounts and updateAttributes.

These single-entity APIs are no longer available with the release of API v20:

  • createDimension
  • updateDimension
  • createDimensionValue
  • updateDimensionValue
  • createLevel
  • updateLevel

They will continue to function with previous API versions. For single-entity creation or update in API v20 and beyond, use the metadata bulk APIs of updateDimensions and updateLevels

See API Changes By Release.

Auto Map New Data Elements

You can set options in the Planning Data Loader to automatically map new Account, Level, and Dimension data elements detected at loader run time. Your options vary depending on if you made selections in the Source Display Name Column in the Data Mapping tab.

See Create a Planning Data Loader.

Functions for Replacing Text 

When you write expressions for custom SQL columns in a data source staging table, you can now use:

  • REPLACE: Replaces all instances of [text_expr_1] in [text_expr_3] with the value [text_expr_2].
  • REGEX_REPLACE: Replaces all instances that match the regular expression [text_expr_1] in [text_expr_3] with [text_expr_2].
  • TO_ACCOUNT_CODE: Transforms text and ensures a value is compatible with the planning Account Code field. Removes all spaces and then replaces any non-alphanumeric characters with underscores and truncates values over 2048 characters long.

You can only use these functions in a custom SQL column for a data source staging table.

See SQL Expression Reference.

Support for NetSuite Token-Based Authentication 

For enhanced security, the NetSuite 2018.1 release requires two-factor authentication (2FA) for all highly-privileged roles in NetSuite production, sandbox, development, and Release Preview accounts. In the NetSuite 2019.1 release, 2FA becomes mandatory for API and integration access. NetSuite recommends using token-based authentication (TBA) to implement 2FA for API and integration access.

With the Adaptive Planning 2019.1 release, you can upgrade to NetSuite 2018.1 and leverage TBA for data integration between Adaptive Planning and NetSuite. This enhanced security supports these data integration approaches:

  • NetSuite Basic integration
  • NetSuite Enhanced (advanced) integration

See Prepare for Netsuite 2018.1 Two-Factor Authentication for more. 

  • Cet article vous a été utile ?