Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

A data profile maps fields from a source file to properties of LogiSense objects. They allow you to validate and transform input data before it is imported. Data profiles can be used by the data import process to:

  • import orders from CRM/CPQ

  • consolidate invoices from disparate billing systems

  • process move/add/changes for devices/device states

  • quickly import data from a legacy billing system

Automatic Field Detection

The platform is capable of auto-detecting source file fields and datatypes. If the first row of the import file contains field labels then LogiSense Billing will automatically detect and name the field. It will also determine the datatype using a sample from the file. This greatly speeds up the implementation of import processes.

Transactional Control Using Envelopes

Data profiles allow you to define how much of the import process is included in a single transaction. It is possible to import each row separately as its own transaction, the entire file as a single transaction, or divide the file into chunks. This can be used to prevent partial import as the rows wrapped in a single envelope will roll back if there is a failure anywhere in the process.

Visual Map

The visual map provides a graphical representation of the process of the data import process. It allows you to visually map and transform input fields to LogiSense Billing objects. For more information seeĀ Mapping.

  • No labels