NETSUITE and ADAPTIVE INSIGHTS – BETTER TOGETHER


The latest release of the Adaptive Insights software suite (2017.1) contains many significant updates, but none could be more impactful to NetSuite users than the recent changes in Adaptive Integration.

Currently, NetSuite Financial Planning/Adaptive Insights users benefit from an integrated system with drill-through capabilities into GL actuals by the core NetSuite segments – subsidiary, department, class, location, item and customer.  Since financial planning and forecasting involve more than just GL accounts, many NetSuite users have also invested in the more robust connector which allows for additional data transfer types.  The challenge, however, is that the connection was not always successful in bringing over exactly what the customer needed, a great deal of extra effort was needed to make the integrations work, and the customer would need to maintain two separate integration setups if they wanted drill-through and non-GL data transfers.

The integration product team at Adaptive Insights have addressed many of these challenges, and the product is now up-to-date and mapped to NetSuite’s 2016.2 SuiteTalk Web Services.  This means that it can now access newer account and transaction types to bring into Adaptive models, resulting in more data for integration.  In addition, the same drill-through capabilities that are in place with the basic integration can now be incorporated into the enhanced integration, which eliminates the need for multiple integration points or additional imports of transaction data in order to support a user base hungry for details.

The most exciting update to the integration platform is the option to bring saved search results directly into an Adaptive model.  This is huge news for NetSuite customers working with custom segments, fields and records.  For many customers, the only way to get detailed or multi-dimensional planning data into an Adaptive model has been to:  write a saved search, export to Excel, manipulate the columns to match an import template, and then import the data into the Adaptive model.  Time-consuming, cumbersome, and error prone.  With the new Adaptive connection in place, however, those same saved search results can be integrated and mapped once into the Adaptive model, and then the data transfers with no data manipulation necessary.  Why used a saved search as a data source?  It is the easiest way to bring in custom elements, create specific and filtered data subsets, and more importantly – the most direct way to control what data is being integrated into your Adaptive model.  (Caveat – this freedom is both a positive and negative so you will want to make sure to pay attention to your saved search fields and parameters.  It is considered a best practice to create saved searches specifically for use in Adaptive Integration and to name them so that they are not modified or deleted by other NetSuite users.)  This is just the first step in working with saved searches in Adaptive Integration, and I personally look forward to seeing what the product team will come up with next.

Having worked through the challenges of data integration for many NetSuite and Adaptive customers, the Red Barn Partners team is truly excited about the updates within Adaptive’s 2017.1 release.  Data integration may not be as eye-catching as colorful scorecards, or as dynamic as a well-designed scenario planning model, but it can make or break a successful systems implementation.

To learn more about implementing any of the Adaptive Insights software suite, check out our website at www.redbarnpartners.com.

Leave a comment

Your email address will not be published. Required fields are marked *