10.01.00.23 January 2020

Known issues

• There is no upgrade path for user data.
  • New product versions do not support data from previous versions and no upgrade path is possible.
• Multi-users conflict resolution is not supported.
  • Cost code assignment and slicing operation conflicts are not handled and can result in incorrect data and geometry.
• No design change management.
• Cost code configuration updates are not supported.
• Volume is not calculated for some Earthworks and Fill elements.
• Performance decline on bulk operations (above 1000) or when total assignments count is above 5000.
• Instant crashes possible especially on decent machines with huge models and intensive usage.
• Calculated volume of sliced components is different compared to the volume of the same components before the slice. It is usually smaller than 0.001% and should never be greater than 0.01%. Volume calculated before the slice is the correct one.
• Sometimes volume value is not calculated for one or two pieces of the sliced component, when the slice is performed on a curved or bent component.
• Sometimes the application freezes when long road components are being split into two big parts. This does not happen when these road components are being split into smaller pieces.
• Unit of measurement abbreviation in column "UOM" (in "Reporting" grid) does not change when calculated quantity is converted to another UOM using "Convert to" functionality. This issue is seen also in the exported CSV file.
• Order of assigned components is different in the "Reporting" grid and exported CSV file:
  • in the "Reporting" grid, components are not listed alphabetically .
  • in the exported CSV file, components are listed alphabetically.
• Order of assigned work-steps is different as well:
  • in the "Reporting" grid, work-steps are listed alphabetically. 
  • in the exported CSV file, work-steps are listed according to work step code.