Release 4.6.1

Version ipolog 4.6.1 mainly contains minor bug fixes for version 4.6.0. The adjustments are listed below.

ipolog Web Views

When importing a parts data file into a planning state, errors occurred if the data formats in the Excel table differed from those expected by ipolog, for example, a number instead of a character string. We have found a solution to work around this.
When duplicating a scenario, errors occurred when duplicate planning space were opened. We have fixed this issue, so that everything that has been duplicated can now be used like a newly created scenario.
When using certain filters for a planning space, in the past, not all materials were available in the scenario part data after publication within the planning space. This issue has since been resolved, so that no parts are lost.
In rare cases, error 404 occurred when updating the part data of a scenario and a planning space. We were able to identify the cause of this and provide a solution.

In some situations, an error could occur when opening planning spaces in ipolog 4 Material Flow. This was caused by IDs not being set in some faulty planning areas. We have fixed this so that it is still possible to open and continue working.

If the part data planning state changes but the log IDs and material areas remain the same for a specific stage, we now retain as much of the fine placement from the original planning as possible. This means you can now also use other part data planning states and, for example, use your previous plan as a starting point for planning at a later date.
All facilities consisting exclusively of line elements caused a crash when saved in ipolog 4 Workspace. We have fixed this issue and it is now possible to save facilities consisting exclusively of line elements again.

No adjustments