Report Generator Import and Edit 

ERPLY Books Report Generator allows you to not only edit data within the system but also import, edit and delete data from ERPLY back office (inventory side). This tutorial covers how to work with ERPLY backoffice data through Report Generator.

Two Methods to Get Data

 

Method 1: Import Preview (File Upload)

  1. Open the Report Generator (Reports → Report Generator)
  2. Go to Import Preview
  3. Click Select File
  4. Upload a file (Excel, CSV)
  5. Make changes in the Other Options (if needed)
  6. Click Done

Method 2: Direct API Call

  1. Open the Report Generator (Reports → Report Generator)
  2. Go to Import Preview
  3. Enter the API call directly (ERPLY API) (e.g., “getBillingStatements”)
  4. Click Done
  5. System retrieves data directly from ERPLY API

Basic editing workflow

Note: This tutorial uses Method 2 (Direct API Call) to retrieve data.

Making Changes

Once data is loaded, you can:

  • Edit values – Click directly in cells to modify data
  • Add new rows – Click the down arrow to add a new record
  • Copy – Paste data directly from spreadsheets
  • Delete rows – Use the delete option at the end of columns

Saving Changes

When you click Save, you need to configure three operations:

  1. POST (API request for creating new entries) 
  2. PUT (API request for modifying records) 
  3. DELETE (API request for removing records) 

Important: For ERPLY back office, adding new records and updating existing records use the same API request.

Required Configuration

You also need to add ID field (Required) – always specify the ID field for your data type:

  • E.g., (billingStatementID)

The system uses this to identify which records to update or delete.

Additional Mappers (When Needed) Some fields need mapping to specify the target API field:

  • E.g., “productCategoryName”:”nameENG” 
  • E.g., “productCategoryName”:“nameLAT” 

Saving Custom Reports

You can also save your Report Generator configurations for reuse.

Saving a Configuration

  1. Configure all your settings (API requests, ID field, Additional Mapper)
  2. Click Save report 
  3. Give your report a name (e.g., “Billing Statement”) and type
  4. All settings are saved for future use

Using Saved Reports

  1. Open the Custom Reports (Reports → Custom Reports)
  2. Select your saved report (e.g., “Billing Statement”)
  3. Click to load the report with all pre-configured settings
  4. Make your edits
  5. Click Save to process changes

Advanced Features

ID Mapping

System IDs (like customer IDs) are often meaningless numbers to you, as they use a different format. ID Mapping lets you add an editor for System ID, where the system automatically handles the technical IDs behind the scenes.

Example: Customer ID (editor for customerID)

Problem: customerIDs are (other) system-generated numbers that don’t mean anything to you. The solution is to create an ID Mapping that links the customer’s registration code to the customerID, so that searches are based on the registration code while the system continues to use the correct ID in the background.

Steps:

  1. Click More → Other Options
  2. Select “Map where and how to get ID-s”
  3. Add values: (e.g., customerID:ENTITY.REGISTRATION_CODE:ENTITY.PARTNER_CUSTOMER_ID)
  4. Also, if you want to add an editor not just for a single customer ID but for two or more IDs at the same time (for example, customerID and productID), you can set it up as follows: e.g., customerID:ENTITY.REGISTRATION_CODE:ENTITY.PARTNER_CUSTOMER_ID|productID:ARTICLE.CODE:ARTICLE.PARTNER_ARTICLE_ID|
  5. Click Search

Result: You can now search and select customers by their registration code, but the system saves the correct customer ID to ERPLY backoffice.

Selection Boxes for Enum Values

Some fields have specific allowed values (enums/dictionary values). You can configure these as dropdown selection boxes instead of free text, which reduces errors, ensures only valid values are entered, and helps save tim. To accomplish this, you can similarly use ID Mapping.

Example: Billing statement time

Available Values:

  • When period starts
  • When period ends
  • Based on metered readings

You can add values as follows: e.g., billingStatementTime:CUSTOM,1=WHEN_PERIOD_STARTS,2=WHEN_PERIOD_ENDS,3=BASED_ON_METERED_READINGS