What if another user makes changes to an asset (e.g. schedule) at the same time Im accessing it?
The D3 System was specifically designed to make sure this is never an issue by preventing users from modifying assets on The D3 System server. To make changes to an asset, users must first download the asset to their local computer, make the required changes, and then re-upload the new asset through a trackable check in/check out system. The user can then either delete or replace the old version from the project, or leave it in The D3 System as part of version control.
dax|D3 was specifically designed to make sure this is never an issue by preventing users from modifying assets on the server. To make changes to an asset, users must first download the asset to their local computer, make the required changes, and then re-upload the new asset through a traceable check-in/check-out system. The user can then either delete or replace the old version from the project, or leave it as part of version control.
