What's New in Lucanet Data Collection

Administrators can now restrict each form template in a reporting package to specific reporting entities. In the Form templates step of the reporting package configuration, the new Reporting entities column displays the reporting entities that receive each form template; by default, all reporting entities in the reporting package are assigned. In the Assign Reporting Entities dialog, you select the reporting entities in a searchable list with Select all and Deselect all actions. Reporting entities added to or removed from the reporting package are added to or removed from every assignment automatically.

When a data collection process is started, forms are created for each reporting entity only from its assigned form templates, and regular validation rules that reference an unassigned form template are skipped for that reporting entity. A reporting package can only be published when every reporting entity has at least one form template assigned and every form template has at least one reporting entity assigned. This way, reporting entities with different reporting obligations no longer require a separate reporting package per entity type.

For details, see Creating and Configuring Reporting Packages.

Formula rows and formula columns now treat an empty operand cell as 0 when the formula is evaluated. Previously, the result was empty as soon as one operand cell contained no value. The calculation therefore always runs and resolves correctly at every level of a row hierarchy, including superordinate rows and the Total row, even while a form is still being filled in. The empty cell itself remains empty. This also applies to operands from other tables and form templates, even if the referenced form has not yet been submitted. Division by zero still produces an empty result.

For details, see Configuring Tables in Form Templates.

When you create or edit a reporting package, the Group currency drop-down list now displays EUR, USD, GBP, and CHF at the top, separated from the alphabetical list of all ISO currencies. The four currencies are fixed, i.e. they do not depend on the currencies used in your reporting packages, and are also included in the alphabetical list. When you enter a search term, matching currencies are displayed both at the top and in the alphabetical list.

For details, see Creating and Configuring Reporting Packages.

Administrators can now control how data enters an editable column in pivot tables, CFP pivot tables, and dynamic tables. The new Entry method column option offers Manual & import — the default — Manual only, and Import only. Columns set to Manual only or Import only are marked with dedicated icons in the column header. Columns set to Import only are read-only during data collection. Columns set to Manual only cannot be selected in the column mapping step of Excel and Lucanet.Financial Warehouse imports, and CFP imports discard these columns from the import. After an import, a message lists any columns that were skipped because they are configured for manual entry only. Changes to the entry method apply only to new data collection processes.

For details, see Configuring Tables in Form Templates.

Administrators can now limit which elements of the partner, transaction type, and adjustment level dimensions are available in drill downs. In the reporting package configuration, you select the elements of each drill down dimension in a searchable list with Select all and Deselect all actions; for partners, the additional In reporting package action selects exactly the partners that match the reporting entities in the package. The package-wide selection applies to all reporting entities, and you can configure a different selection for individual reporting entities. Collectors only see the selected elements, and import rows that contain excluded elements are rejected. Changes apply only to new data collection processes.

For details, see Creating and Configuring Reporting Packages.

The intercompany validation results now display the rule description under the Details heading when you expand a rule — as in the results of regular validation rules. The description is displayed for every rule status. If a rule has no description, No description provided is displayed. The results display the description as it was when the validation was executed; changes to the rule appear only after the validation is executed again.

For details, see Entering, Validating, and Approving Data.

When a CFP pivot table is created, Data Collection records the structure of the source Consolidation & Financial Planning workspace. With the new Sync with CFP icon in the detail view of a form template, administrators can now check an existing table for structural changes in CFP. The Select Rows to Include dialog is displayed; each changed element is marked with a colored label: Added for elements added in CFP, Deleted for elements that no longer exist in CFP, and Updated for elements whose name, superordinate element, or order has changed. A message at the top of the dialog summarizes the number of detected changes per type. You adjust the row selection directly in the dialog. Already collected data is preserved, and changes to the row selection apply only to new data collection processes.

For details, see Configuring Tables in Form Templates.