| Summary | atesio calculation does not provide a link between street centerlines and possible trenches |
| Description | When calculating networks with NET Design and atesio, information from the street centerlines is not transferred to the possible trenches. The error occurs with atesio version 2021. Here, after the preprocessing and the creation of the possible trenches, no relations to the original street centerlines are returned. |
| Workaround | Currently there is no way to work around the problem, but atesio is already working on a solution, which is expected to be available with atesio version 2022. |
| Affected versions | 12.3.4 |
| Status | OPEN |
| Summary | Project validation error in NET Design |
| Description | During project validation in NET Design, after calculation with Comsof Fiber Designer, sometimes an error occurs when project validation is run again after the selected optimizer has been changed. |
| Workaround | In project validation, do not select all validations, but only those that are really relevant. |
| Affected versions | |
| Status | OPEN |
| Summary | The list of cluster types in the NET options is loaded only once when the project is opened. |
| Description | If a new cluster type is created after the NET options are first displayed, then the list will not be updated until the next time the project is opened. |
| Workaround | Close the project and open it again. |
| Affected versions | 12.3 |
| Status | OPEN |
| Summary | Fiber optic connection editor creates connectors with multiple outgoing connections |
| Description | If an action "Connector to technic port" is created first for an unconnected connector and then another action "Connector to fibre", then a connector with 2 outgoing but no incoming connection is created. As a result, overviews and reports are created incorrectly. |
| Workaround | The problem can be solved by removing all patches between the faulty connectors and thier ports. Afterwards, these patches must be recreated in the fiber optic connection editor using the "connector to port" action. To identify the relevant connectors, the following SQL filter can be used in the FO Connectors form: Fid in (select c.fid from tc_fo_connector c join tc_point p ON p.fid_attr = c.fid join tc_conn c1 ON c1.fid_to = p.fid join tc_conn c2 ON c2.fid_from = p.fid where c1.flow != c2.flow) |
| Affected versions | 12.3.4, 12.3.5 |
| Status | OPEN - solution expected for version 13.0 |
| Summary | The CO Overview output is incompletely if no switching point has been set. |
| Description | The CO overview gives incomplete results if there is no switching point in the network path. This is needed to determine the "CO side" of the network path. Net paths are still output, but individual net paths are omitted. Unfortunately is it not obvious to the user that network paths are missing. |
| Workaround | An additional switching point must be added. The link between the termination from which the CO Overview is started and this switching point must be established. |
| Affected versions | 12.2.1 |
| Status | OPEN - solution expected for version 12.4.1 |
| Summary | Flat Feature Search in Autodesk Infrastructure Administrator does not work with all data types under PostgreSQL. |
| Description | During the Flat Feature Search in Autodesk Infrastructure Administrator, an error occurs under PostgreSQL when searching for a number, for example. |
| Workaround | Use the Sequential Search instead of the Flat Search. |
| Affected versions | 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 2.0.0, 2.0.1, 2.1.0, 2.2.0, 3.0.0, 3.0.1, 3.1.0, 3.1.1, 4.0.0 |
| Status | OPEN - solution expected for version 5.0.0 |
NET Help Center