Feature Requests

Here we have again a case where we need to create two exact companies only for the type. The supplier is needed for the PO or is more or less created out of the PO Import, from another ERP-System. Then we need to create a subcontractor when he operates on site. Process Packages in Pending Packages needs to consider this new functionality and allow manual adjustments of the target module.

LMS should store documents directly in designated SharePoint folders, linking them through metadata for traceability and enabling easy access to project documentation. This request could be another option in the export functionality, where Blob, Public API and Mail are available today.

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

I understand there is a technical limit to editing more than 1000 elements, but it would be beneficial if this limit could be increased. Having the ability to edit more elements would greatly enhance my workflow and efficiency. A limit of 5000 would already be very helpful.

Feedback: We’ve observed that for large text fields in the DailyLogs, users who are not proficient in German often type their text directly in the LMS, then copy it into ChatGPT, and finally back into the LMS. They do this to correct umlauts, spelling mistakes, and punctuation. Suggestion: It might be helpful to offer an integrated text correction or language assistance feature directly in the LMS to simplify this workflow

Description: We’ve noticed with several customers that the current DailyLog fields for Temperature and Weather Condition are often insufficient. These fields are frequently hidden and replaced by custom ones. Proposed Idea: Introduce a dedicated WeatherLog module that can be configured per project, using its own data object. Suggested fields include: -Timestamp (date and time) -Temperature -Condition -Humidity -Rain Amount -Wind … (depending on what the weather service provides) Example API: https://api.openweathermap.org/data/2.5/weather?lat=48.4511&lon=14.0853&units=metric&APPID=c3c0913a9e74ac15c76097f08fb77e4d Automation Idea: The WeatherLog module should allow configuration of automated entries — e.g., 1 to 3 times per day at defined times. A scheduled job would call the weather service and store the current data automatically. Prerequisite: Project GPS location must be defined. This would allow weather data to be automatically logged (e.g., morning, noon, evening) for each project. In the DailyLog Report, the relevant WeatherLog entries could then be joined in for the day (as a list of weather logs). Additional Improvements: -Add a weather condition icon that can be displayed in reports and dashboards (predefined set). Include translations for all weather conditions in all supported languages, also in reports For new systems, show the WeatherLog module by default and hide the existing temperature/weather fields on DailyLog.