Data Profiles Screen

Last verified with: 10.8.6.0

Overview #

Data profiles define how source data is interpreted and prepared before it is imported into LogiSense Billing. A data profile identifies the target resource, the source file type, the source-field structure, and any layout, mapping, or callout behavior needed to process the data correctly.

In practice, data profiles are used to standardize repeatable import scenarios. Once a profile is configured, it can be selected during a data import so the incoming file or payload is processed using the expected field definitions and mapping rules.

Prerequisites #

Data profiles can be configured as needed. There are no prerequisite configuration steps, although the target resource and source-data structure should be understood before the profile is created.

Data Profiles Panel #

The Data Profiles panel on the left lists the configured profiles. Select a profile to view or edit its details in the panel on the right.

Actions #

Icon	Description
	Imports a json file that contains a data profile configuration
	Exports the data profile configuration of the selected data profile to a json file
	Deletes the selected data profile if not in use
	Adds a new data profile
	Updates an older data profile configuration when the selected profile version differs from the current application version

Edit Data Profile Panel #

The Edit Data Profile panel displays the configuration for the selected data profile

Core Fields #

• Name: Identifies the data profile.
• Category: Organizes the data profile into a category when category grouping is used.
• Sample File: Stores a sample input file for the profile.
• Target: Defines the resource or entity the incoming data will populate.
• API Version: Displays the API version associated with the selected target.
• Include Child Target: Indicates whether child targets should be included when that target structure supports them.
• File Type: Defines the format of the incoming data.
• First Row Has Labels: Indicates that the first row in the source file contains field labels.
• Ignore Records Starting With: Identifies record prefixes that should be ignored during processing when applicable.
• Delimiter: Defines the delimiter used by delimited file types.
• Envelopes Per Request: Controls the number of envelopes included per request when envelope-based processing is used.
• Patches Per Envelope: Controls the number of patch operations included in each envelope when that processing model is used.
• Stop On Error: Determines whether processing stops when an error is encountered.
• Lock Settings: Prevents the data-profile settings from being changed during later import use.
• Line Length: Defines the expected line length when fixed-length file processing is used.

Sample And Review Actions #

The right side of the screen includes actions used to work with sample data and profile validation:

• Upload Sample File: Uploads a sample input file to the profile.
• View Input Sample: Displays the interpreted sample input data.
• View Target Sample: Displays the target-side result after the configured profile logic is applied.

These actions are helpful when validating that the profile is configured correctly before it is used in a live import.

Layout Tab #

The Layout tab is used to manage the layouts defined for the profile. This is especially important when the selected file type supports multiple layouts or record structures.

Use Add Layout to define a new layout. Existing layouts can be reviewed, edited, or removed from the list.

Each layout typically represents a record structure or section of the incoming data. This is useful when one inbound file can contain more than one kind of record, or when the import logic needs to distinguish one layout from another during processing.

Administrators usually work in this tab first when the source file is not a simple single-layout import, because the layouts defined here become the basis for the schema and mapping work that follows.

Schema Tab #

The Schema tab is used to define the source fields for the selected layout.

This tab is where administrators add the schema entities or fields that describe the incoming data structure. Each field can then be maintained through the schema workflow, including editing and removal.

In practice, the schema defines how LogiSense Billing interprets the inbound data. This includes the source-field names, field types, and layout-specific field structure that the import process should expect.

The schema is the foundation for the rest of the data profile. Once the source fields are defined correctly here, they can be mapped more accurately in the later tabs.

Layout Design Tab #

The profile also includes a layout-design area where the selected field can be reviewed in a sample-oriented layout view.

This area supports field positioning, field selection, and record navigation so administrators can understand how the incoming layout is being interpreted.

This view is especially helpful when working with structured or positional data, because it allows the administrator to inspect how fields are arranged and to confirm that the inbound layout is being interpreted as intended.

It is also useful during troubleshooting, since it gives a more visual way to review field placement than the schema list alone.

Visual Map Tab #

The Visual Map tab is used to map source fields to target fields. This is where the relationship between inbound data and destination fields is maintained.

This area is also used when map-level transforms are needed between source and target values.

The visual map helps administrators verify that the right source values are being written to the right target fields. It is also the area where more advanced mapping behavior can be configured, such as combining values, applying formulas, or setting literal values before the data is written to the target.

Because this tab shows both the source side and the target side together, it is often the best place to confirm the overall logic of the profile before a live import is run.

Call Outs Tab #

The Call Outs tab is used to define plugin callouts that should run at supported stages of the import process.

Callouts are typically used when profile behavior needs to be extended beyond basic mapping.

This tab is most useful when the import process needs custom logic that cannot be handled through standard field definitions and mapping alone. For example, an organization may use callouts when extra transformation, enrichment, or conditional handling is required as part of the import workflow.

Because callouts rely on custom plugin behavior, they are typically configured as part of a more advanced implementation or integration scenario.

Guides #

Adding Data Profiles #

1. In the Data Profiles panel, click Add.
2. Enter the basic profile information, including Name, Target, and File Type.
3. Upload a Sample File, if available.
4. If the file structure requires layouts, configure them on the Layout tab.
5. Define the source fields on the Schema tab.
6. Configure the source-to-target mapping on the Visual Map tab.
7. Add any required callouts on the Call Outs tab.
8. Use View Input Sample and View Target Sample to review the result.
9. Click Save.

Editing Data Profiles #

1. In the Data Profiles panel, select the profile you want to update.
2. Update the profile settings, schema, layouts, maps, or callouts as needed.
3. Review sample input and target output if needed.
4. Click Save.

Deleting Data Profiles #

1. In the Data Profiles panel, select the profile you want to delete.
2. Confirm that the profile is no longer in use.
3. Click Delete.
4. In the confirmation dialog, click Yes.

Importing And Exporting Data Profiles #

• Use Export to save the selected data profile as a JSON configuration file.
• Use Import to load a data profile from a JSON configuration file.
• Use Upgrade when an imported or existing profile needs to be updated to the current supported format.