The inability to filter activities and trace logic where the next activity would show in your visual is a major issue that affects our reporting of critical paths. Those paths can be coded but should be traced rather than simply relying on a code field to be accurate in a live environment. Identifying the predecessor and successor in some cases was difficult or impossible to the lack of a clear (visible) indication of a driver. In P6 there is a check box that populates if an activity is a driver. This is an efficient process and not available in synchro to our knowledge
Implemented, this would be available in 6.5.
I might have missed the part "Identifying the predecessor and successor in some cases was difficult or impossible to the lack of a clear (visible) indication of a driver. In P6 there is a check box that populates if an activity is a driver. This is an efficient process and not available in synchro to our knowledge." Can it be explained further?
Is this what you meant and where you want it to be?
If the below screenshot (see the column that says "Driving") is not satisfactory, submit a separate idea.