"Demote" Data Shortcuts

[scott.jeffers]

I have a file with about 18 data ref'd alignments. When I opened it up this morning, ALL of the data refs had been promoted and nobody in the office will fess up. This file has alignment labels up the wazoo, so deleting, re-referencing, and re-labeling is pretty much out of the question. Is there any way to force the alignments to call back to their source drawing?

[BlackBox]

I have a file with about 18 data ref'd alignments. When I opened it up this morning, ALL of the data refs had been promoted and nobody in the office will fess up. This file has alignment labels up the wazoo, so deleting, re-referencing, and re-labeling is pretty much out of the question. Is there any way to force the alignments to call back to their source drawing?

Well, the quickest way is to simply restore the drawing from yesterday's (or prior) backup, no?



[Insert reference to cadtag's AU course here]

[scott.jeffers]

I just walked through 20 day's worth of backups. It's been like this for quite a while. Don't blame me; I was on vacation!!

[BlackBox]

I just walked through 20 day's worth of backups. It's been like this for quite a while. Don't blame me; I was on vacation!!

Without the ability to restore a copy from backup, I'm afraid that what little I know of C3D .NET API does not suggest this is possible; perhaps someone smarter than I can educate us both.

Cheers

[scott.jeffers]

Update: Problem solved (a while ago). Half of the office was on 2013 and the other half was on 2014. Although they are technically the same generation file format, data shortcuts, once opened with 2014, will show as promoted in 2013. This is a known Civ 3D bug. I guess it's on of those UPGRADE, OR ELSE deals.

[BlackBox]

Update: Problem solved (a while ago). Half of the office was on 2013 and the other half was on 2014. Although they are technically the same generation file format, data shortcuts, once opened with 2014, will show as promoted in 2013. This is a known Civ 3D bug. I guess it's on of those UPGRADE, OR ELSE deals.

Glad you got it sorted, and thanks for posting the cause - I also hope you're not responsible for rolling out the mixed-version environment, without first testing the cross-version functionality. Haha *yikes*

Cheers