The current handling of derived fields in Autodesk Fusion Manage is not sufficiently robust or manageable. When a derived field is linked to a source field, I would expect this dependency to remain technically consistent throughout the lifecycle of both fields. Currently, changes to properties of the source field, such as its data type or decimal precision, can require corresponding manual changes to the derived fields. In an environment with many workspaces and numerous derived fields, manually identifying and correcting every affected dependency is not a realistic or scalable solution. The primary requirement should therefore be automatic synchronization. If a relevant property of the source field changes, all dependent derived fields should automatically be updated accordingly. For example: If the decimal precision of a source field changes, its derived fields should automatically inherit the new precision. If the data type of a source field changes, the corresponding derived fields should automatically be updated to a compatible data type. Existing derived-field configurations should remain synchronized with their source fields instead of becoming inconsistent over time. Ideally, this synchronization should happen completely automatically. As an alternative or additional approach, Fusion Manage could provide a semi-automatic synchronization mechanism. An administrator could trigger a synchronization for a workspace or database, allowing the system to check all source/derived-field relationships and update the derived-field configurations accordingly. Only where automatic synchronization is technically not possible should the system fall back to manual intervention. In that case, it should: clearly identify the affected source field, list all dependent derived fields and their locations, explain which properties are inconsistent, and allow the administrator to resolve or synchronize these dependencies in a controlled way. However, such a dependency list should be considered a fallback mechanism, not the primary solution. Administrators should not have to know or remember where dozens of derived fields are located, nor should they have to wait for incorrect values or errors before discovering inconsistent field definitions. If Fusion Manage manages the dependency between a source field and its derived fields, it should also manage the technical consistency of that dependency.
Show More