Feature Requests

Currently a defined list of tables and fields can be added in the import mapping. We have a use case to integrate several systems and need to map normal text or numeric fields of e.g. material to other values in the database. Please enhance the import mappings to allow more use cases for "normal" fields

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.

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.

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

It should be possible to update the Stock Qty via import (in the background InventoryDate and InventoryQty should be set)