What's New in Lucanet Data Collection

A new element type, Dynamic table, lets data collectors add, duplicate, and remove rows themselves during data collection, up to a maximum that Data Collection administrators configure. This is useful for variable-length data — for example, fixed asset lists, intercompany loan schedules, or provision schedules — where the number of rows differs from one reporting entity to another.

Data Collection administrators define the column structure once in the form template, and each data collector enters as many rows as they need during data collection.

For details on configuring Dynamic tables, see Creating and Configuring Form Templates. For the collector workflow, see Entering, Validating, and Approving Data.

You can now duplicate any element directly from the detail view of a form template. The duplicate inherits the configuration, mappings, required-field status, and all language labels of the original, so you do not have to rebuild similar elements from scratch.

You can now change the display order of rows and columns in a Pivot table or CFP Pivot table by drag-and-drop. Rows can also be moved under a different superordinate row to restructure the hierarchy. Collected data, drill-down configurations, and aggregations are not affected by reordering — values stay bound to their row and column identifiers.

When you add a CFP Pivot table element, you can now choose which rows to include from the source Consolidation & Financial Planning workspace before the table is created, instead of pulling all eligible rows in automatically. Three selection modes are available — Select all, Show items only, and Custom selection — and the original hierarchy is preserved in the resulting table.

You can now group validation rules by category using free-form tags, then filter the rules list by one or more tags. Tags apply equally to Regular and Intercompany validation rules and have no effect on rule logic or execution.

Tags can be assigned to a single rule directly in the rule's configuration, or to several rules at once from the validation rules list using the new Assign tags and Remove tags bulk actions.

When configuring a Regular validation rule, you can now reference superordinate rows directly, not just the lowest-level rows. The rule uses the aggregated value of the superordinate row — the same value displayed for it in the form. This makes it easier to write rules that compare subtotals without listing each subordinate row individually.

The Select items and/or accounts drop-down list in the Intercompany rule configuration now hides form templates and pivot tables that have no partner-related configuration, so only elements that are actually eligible for intercompany validation appear.

In the same drop-down, you can now select a superordinate row to automatically include all of its eligible subordinate rows.

The Data Collection list now shows the result of the last intercompany validation execution in a dedicated IC Validation result column, separate from the existing Validation results column. Process-level and form-level rows show the IC status; entity-level rows are empty. Point at an indicator to see the exact error and warning counts.