December 2017

Sun Mon Tue Wed Thu Fri Sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31            
Blog powered by Typepad

Become a Fan

« Civil 3D 2018 New Feature: Introducing Section View Drafting Buffers! | Main | Tool for Tuesday:  ADEDEFDATA »

04/28/2017

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Anthony Bayadi

This is great, but what happens when you take this info into NavisWorks, does it maintane the data sets or is this info lost once brought into Navisworks?

Des

Can the process also be done in reverse, i.e. can data entered into the extended data tab, be exported out to an Excel spreadsheet.

Kevin Spear

Great tip! I'm guessing one selection does not force the other values to auto populate? We would have to manually pick each value?

I suppose i am asking if we can do a "record" merge with property sets, is that possible?

Alan Gilbert

The attribute data should go to Navisworks fine. However, the link to the external file will not make it I'm sure.
-Alan

Alan Gilbert

Hi Des, check out my blog post tomorrow as I'll be showing a method for this.
-Alan

Alan Gilbert

Hi Kevin,
Not that I'm aware of. However, I'm a novice at ACAD Architecture (where property set data originated), so I wouldn't be the best authority on this.
-Alan

The comments to this entry are closed.