Data Load Limitations and Error Resolution

Limitations when Loading Data

• GL Data and Transaction data load through the Planful Data Load Rules interface (copy / paste option) - 15K records with Across Columns in Select Sample Input File page

• GL Data and Transaction data load through the Planful Data Load Rules interface (File Load) – suggested limit is a file size of 10 MB (approximately 110K records)

• Data load through Web Services

  • GL Data load through Web Services – suggested limit is approximately 500K records

  • Transaction Data load through Web Services – suggested limit is approximately 1M records

• Employee compensation type data loads – suggested limit is approximately 15K records

• Data load through NetSuite Saved Search-based integrations - suggested limit is approximately 400K records

• Data load through cloud services such as Box and GDrive - suggested limit is a file size of 30 MB

• GL data, translations, and transaction data load through the Data Load Rules interface from the FTP/SFTP server - suggested limit is 20 files to the DLR folder, with each file having a maximum size of 1GB.

• Data Load through Power BI for Dynamic Planning Analytical Model

  Deep Hierarchy Type: Recommended limit is up to 2M records.

  Shallow Hierarchy Type: Recommended limit is up to 3M records.

  Note:

  If you have requirements that exceed the limitations listed above, please contact Planful Support.

Troubleshooting Data Load Errors

Data Load Error : Loaded Time 'Jan-19' is not matching with the scenario '2019 1+11 Forecast Fiscal Year '2019'

This data load error occurs when a user attempts to load data sourced from the wrong scenario. In this case, the user is loading data to

Planful via a Data Load Rule to a forecast scenario where the first period is Jan-19. And, the user has set the Forecast to begin with Feb19.

The Jan-19 period is being sourced from another scenario (Actuals by default) and no longer allow data to be loaded to this period in this scenario. If the user wants to load data to this period, it will have to be done in the source scenario. Then, actuals should be refreshed in the forecast to move that data into the scenario.

This will be the case with future scenarios as the user moves the forecast period forward.