Feature Requests

I would like to have an additional column in the import overview that displays the affected data field. Additionally, splitting the description into three columns—data field name, old value, and new value—would make it easier for me to review the data. Currently, I have to copy the data into a small Excel tool to generate these columns.

It should be possible to make an automated import of project lists via Excel Template.

Extend the import process so that Tasks can be created automatically from predefined Task Templates whenever new objects (Packages, Shipments, ...) are imported. What will change? • Administrators can configure a Task Template for each supported import type. • During an import, the system will check whether a Task Template has been configured. (Single selection only) • If a matching template exists, the system will automatically create the corresponding Tasks for every newly created object. • Existing objects will not be affected; Task Templates are only applied to newly created items during import. Configuration • A new configuration option will be available for all supported import entities that allow Tasks. • Users can specify the name of the Task Template to be used during import. • The system validates that the referenced Task Template exists before applying it.

In our projects, we use the Project Documents module to store essential documents. We've agreed on a standard folder structure, but creating this structure for each project is time-consuming. It would be beneficial to expand the import function to allow folder creation through import, streamlining the process.

Support the import function for Material Request and Material Issue module. Thoughts: Material Request and Issue imports need to check all available quantities against the Package Items and respond with an error, if too many quantities are requested/issued. A Material Issue import in relation to a Material Request is very complicated to configure and implement with getting all validations correctly, so this would be out of the scope.

When creating our goods receipts via the Consolidator Inbound interface, we save the goods receipt number from SAP at the package item level. However, when package items are fully moved using Move Material via Import, the assignment to the original package is lost, making it difficult to find the associated information. We need a configuration option to copy the package item during the move.

Currently I need two imports for creating projects: Companies and projects. The project import can then reference a company, created with the first company import. I would like to have only one import, and automatically create the Customer and Site address from this one import.

I am looking for a way to create an import mapping for Supplier No in the PO Import. This would be useful in cases where the supplier number is outdated and should no longer be used, or in similar scenarios. Unfortunately, I couldn't find this feature in the current system.

Add a setting on import, to read a Task Template. If a new Site Progress Item (or any other object with tasks) is created via the import, a list of predefined Tasks from the provided Task Template will also be created. Limitation comment: If the Site Progress Item already exists, the import will not create Tasks- It is difficult to check if specific tasks from a specific task template have already been created or not. And we should avoid creating duplicate Tasks when importing the same file multiple times.

We need a notification message when a packing import file arrives to Insite LMS via Public API. Currently, the 'Package added' notification sends too many emails. We suggest a separate notification type for Excel imports, such as 'Excel import: packages added', to clearly separate Excel-based package data from manually generated entries.