• Civil 3D

Verify file saves to the cloud

Verify file saves to ensure successful synchronization with the Autodesk Construction Cloud.


00:03

In this session, we'll learn about the importance of verifying file saves to the cloud.

00:08

When editing and saving cloud-based files,

00:11

it's important to keep an eye on the Desktop Connector icon to ensure all saves are successful.

00:16

I say this because if Desktop Connector experiences an error, it will stop synchronizing files until a resolution is provided by the user.

00:24

When a Desktop Connector error goes unnoticed,

00:27

it's possible for one or more files to be saved multiple times throughout the course of the day without those changes making it to the cloud.

00:34

Instead, the latest versions of the files would exist in the local cache while Desktop Connector awaits a resolution.

00:41

As a result, at least until the issue is resolved, other project team members wouldn't have access to the most current design changes.

00:48

Let's look at some best practices associated with saving files to the cloud.

00:52

As you can see, I'm working in Civil 3D,

00:54

and I've opened a cloud-based drawing called xsurveyed that contains some surveyed geometry.

00:60

One best practice you can use to validate file saves

01:03

is to keep a web browser open on a second monitor viewing the cloud project in Docs.

01:08

I'm actually doing that right now.

01:10

If I drag this browser over, we can see the directory structure for the project.

01:14

I can also see the file I'm working on and the current version.

01:17

As I edit and save this file in Civil 3D, it will be easy to validate the saves by watching the changes to the version number.

01:24

Let's look at another way to validate cloud-based file saves.

01:28

I'm going to drag the web browser back over to my other screen and I'll make a quick change to the survey file.

01:33

For this example, I'll draw a rectangle and click the save button.

01:37

When I do, keep an eye on the desktop connector icon in the lower right,

01:42

notice the blue dot showing the file is being transferred to the cloud and then the icon returns to normal.

01:48

No warnings mean the file saved successfully.

01:51

I can further reinforce this by clicking the desktop connector icon where at the top of the home screen it reports a successful file transfer.

01:59

I'll click outside the home screen to close it.

02:02

Now let's flip over to this other drawing called Subdivision.

02:05

I'll make a change to this file by drawing a circle, and I'll click save.

02:09

Once again, keep an eye on the Desktop Connector icon.

02:13

It seems this time we have an error.

02:15

The red dot tells us that.

02:17

As a side note, if that red dot goes unnoticed, I could continue to work on this file.

02:22

I'll draw a rectangle, for example, and I'll click save again.

02:25

All the while I'm making changes.

02:27

Those changes are never making it to the cloud.

02:30

Once again, I'll click the home screen where I can see the update has failed due to a conflict.

02:35

I'm going to click the More button and choose Resolve.

02:38

This will give me additional information about the error, as well as some options to fix it.

02:42

In this case, I'm being told that another person has edited this file while I've been in it.

02:47

Knowing that, there are a few ways I can proceed.

02:50

I can keep mine, which will save my changes as a new cloud version.

02:54

I can keep both, essentially saving my file with a new name.

02:58

I can keep theirs basically throwing away the work I've done, or I can choose to resolve the issue later.

03:06

At this point, I should mention that I planned this error for demonstration purposes.

03:10

The other version of this file was also created by me, so there is no wrong answer when it comes to the resolution here.

03:17

For this example, I'll choose Keep Mine to push the changes I just made to the cloud.

03:21

I will then reopen the home screen to see the pending file was successfully transferred and versioned up in the cloud.

03:29

So, when you're working on a cloud-based Civil 3D project, it's important to validate your saves.

03:34

You can do that using a web browser or by keeping an eye on the Desktop Connector icon and home screen.

03:40

If you're working on large files, avoid shutting your machine down until all file transfers have completed.

03:47

If you experience unknown errors that are preventing you from syncing, stop working until you resolve the issue.

03:53

If you can't figure out the cause, contact support to help you identify the issue and get you back up and running.

03:59

If you don't have time to resolve the issue now, save the current files locally outside of Autodesk Docs to preserve your work.

04:07

Then, contact a support person as soon as possible for help consolidating the files back onto the system.

04:13

Fortunately, cloud connection and synchronization issues are rare.

04:17

That said, it's important to stay vigilant with file saves

04:20

such that you can identify and resolve any rogue challenges with minimal impact to production.

Video transcript

00:03

In this session, we'll learn about the importance of verifying file saves to the cloud.

00:08

When editing and saving cloud-based files,

00:11

it's important to keep an eye on the Desktop Connector icon to ensure all saves are successful.

00:16

I say this because if Desktop Connector experiences an error, it will stop synchronizing files until a resolution is provided by the user.

00:24

When a Desktop Connector error goes unnoticed,

00:27

it's possible for one or more files to be saved multiple times throughout the course of the day without those changes making it to the cloud.

00:34

Instead, the latest versions of the files would exist in the local cache while Desktop Connector awaits a resolution.

00:41

As a result, at least until the issue is resolved, other project team members wouldn't have access to the most current design changes.

00:48

Let's look at some best practices associated with saving files to the cloud.

00:52

As you can see, I'm working in Civil 3D,

00:54

and I've opened a cloud-based drawing called xsurveyed that contains some surveyed geometry.

00:60

One best practice you can use to validate file saves

01:03

is to keep a web browser open on a second monitor viewing the cloud project in Docs.

01:08

I'm actually doing that right now.

01:10

If I drag this browser over, we can see the directory structure for the project.

01:14

I can also see the file I'm working on and the current version.

01:17

As I edit and save this file in Civil 3D, it will be easy to validate the saves by watching the changes to the version number.

01:24

Let's look at another way to validate cloud-based file saves.

01:28

I'm going to drag the web browser back over to my other screen and I'll make a quick change to the survey file.

01:33

For this example, I'll draw a rectangle and click the save button.

01:37

When I do, keep an eye on the desktop connector icon in the lower right,

01:42

notice the blue dot showing the file is being transferred to the cloud and then the icon returns to normal.

01:48

No warnings mean the file saved successfully.

01:51

I can further reinforce this by clicking the desktop connector icon where at the top of the home screen it reports a successful file transfer.

01:59

I'll click outside the home screen to close it.

02:02

Now let's flip over to this other drawing called Subdivision.

02:05

I'll make a change to this file by drawing a circle, and I'll click save.

02:09

Once again, keep an eye on the Desktop Connector icon.

02:13

It seems this time we have an error.

02:15

The red dot tells us that.

02:17

As a side note, if that red dot goes unnoticed, I could continue to work on this file.

02:22

I'll draw a rectangle, for example, and I'll click save again.

02:25

All the while I'm making changes.

02:27

Those changes are never making it to the cloud.

02:30

Once again, I'll click the home screen where I can see the update has failed due to a conflict.

02:35

I'm going to click the More button and choose Resolve.

02:38

This will give me additional information about the error, as well as some options to fix it.

02:42

In this case, I'm being told that another person has edited this file while I've been in it.

02:47

Knowing that, there are a few ways I can proceed.

02:50

I can keep mine, which will save my changes as a new cloud version.

02:54

I can keep both, essentially saving my file with a new name.

02:58

I can keep theirs basically throwing away the work I've done, or I can choose to resolve the issue later.

03:06

At this point, I should mention that I planned this error for demonstration purposes.

03:10

The other version of this file was also created by me, so there is no wrong answer when it comes to the resolution here.

03:17

For this example, I'll choose Keep Mine to push the changes I just made to the cloud.

03:21

I will then reopen the home screen to see the pending file was successfully transferred and versioned up in the cloud.

03:29

So, when you're working on a cloud-based Civil 3D project, it's important to validate your saves.

03:34

You can do that using a web browser or by keeping an eye on the Desktop Connector icon and home screen.

03:40

If you're working on large files, avoid shutting your machine down until all file transfers have completed.

03:47

If you experience unknown errors that are preventing you from syncing, stop working until you resolve the issue.

03:53

If you can't figure out the cause, contact support to help you identify the issue and get you back up and running.

03:59

If you don't have time to resolve the issue now, save the current files locally outside of Autodesk Docs to preserve your work.

04:07

Then, contact a support person as soon as possible for help consolidating the files back onto the system.

04:13

Fortunately, cloud connection and synchronization issues are rare.

04:17

That said, it's important to stay vigilant with file saves

04:20

such that you can identify and resolve any rogue challenges with minimal impact to production.

Was this information helpful?