If more than one Table is placed in a DGN model, it's difficult to tell them apart. It would be so much easier if a Table had a name, like a cell, for identification.
Named Tables would also make it easier to implement AddIns that need to find a particular Table in a multi-Table model.
Thank you very much for the great content Jon! We will make sure to replicate it over wikis and learning material.
Best regards,
Eduardo L
Now that Tables can have a name & description (Update 16), it's possible to create a meaningful report about tables. I've written a step-by-step description on how to write a report about tables.
I'm pleased to say that Table name & description are in Update 16.
Hello Jon, we are actively working on this idea and it is likely to be part of our Update 16 release. As soon as that is out we will share details here. You will also receive an automatic communication regarding the closure of this idea as "shipped". I am really sorry for omitting the link you shared regarding Update 16 last Friday, that is working by mistake and should not be public yet.
MaryB 6 months ago
Ooh - I like that. I mean, it makes perfect sense to me, especially in a sheet with more than one table.
Barry Lothian 6 months ago
Whilst I don’t use Connect the suggestion is entirely logical and I fully agree that such a feature should be implemented so I’ve added my vote
Jon Summers 6 months ago
Probably name + description would be better still. Example:
Table Name = Materials
Description = Use this table to create a schedule of materials
Cory Churchill 6 months ago
I very much like this idea. I know in the agency I work for we use so many tables in our plans for things like Stationing, Curve Data, Reinforcement Bar lists, Pier and Bearing pad elevations, girder schedules and so much more. it would be nice to have them referenced in a tables database within the workset or something, kind of like the sheet index in a way.
Jon Summers 5 months ago in reply to Cory Churchill
Cory Churchill We use so many tables in our plans for things like Stationing, Curve Data, Reinforcement Bar lists, Pier and Bearing pad elevations, girder schedules and so much more. it would be nice to have them referenced in a tables database within the workset
Post that suggestion as a new Idea!
Cory Churchill 5 months ago in reply to Jon Summers
done. posted it here
Table Names and Database
stuartw 5 months ago
With the possibility of multiple tables then a table Manager seems the logical step.