Jump to content

Search the Community

Showing results for tags 'data tag'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
    • Forum Feedback
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Energos
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • AI Visualizer
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
    • Data Tags
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design


  • In-Person Training - US
  • In-Person Training - UK
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups


  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs


  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start








  1. Another data tag related question today: I have already placed in annotation space few data tags of same style with one user-defined text field in it. Whenever I do some changes to that data tag style, data tags present in drawing are reset to default value...bug maybe?
  2. Hi there, I am using more and more data tags to display information from plug-in objects (trusses, hoists, lights...). Therefore ALL or SELECTED eligible mode is the one I use - because I want to tag hundreds of items with one click. F.e. a custom hoist tag or a tag for truss length etc. But this is the same for any tag or any plug-in object. I color this tags with data visualization depending on their tagged information or I use them in marionette. To be able to do this you have to set a "link to data source" (a record) inside the tag field and attach this record to the tag itself. Then the information from the tag field is not only displayed in the tag - it is also written into the record field. And this record field is used within data viz, marionette and so on... The record must not be used for the objects you are tagging. No comes the problem: With a record attached to the tag but not to the object ALL or SELECTED eligible mode is not possible Why is this the case? For making it short I quote @Nikolay Zhelyazkov who was really helpful about this topic: I can understand why the modes aren't allowed, but for my work there is actually no other way around and I think I am not the only one. So what could be a solution? I don't know if this is possible, but maybe this could be one: Only in the ALL or SELECTED mode: If it is detected, that a record is required at the objects for the tag to work 1. display the dialog as you get in SINGLE or LABEL mode 2. but don't give the option to "don't show this dialog again. Always do the selected action." for the dialog. 3. display the dialog with every use of the tool only once - not for every conflict it goes through 4. For every conflict do the same choice like you decided in the dialog PROS: + nothing will change for the currently working modes + ALL/SELECTED will work for this scenario CONS: - no possibility to hide the dialog completely - different choices within a tagging is not possible -> select the ones you want to have the same choice and run SELECTED mode. If you also want to have this to work please vote this up! --------------------------------------------------------------- Setting up the data link: The error message you are given in ALL/SELECTED mode: The dialog you get in SINGLE eligible mode: Original thread with more background information : How to set up a data tag for use in data visualization: Thank you @Tom W. @Nikolay Zhelyazkov for helping me out
  3. The Data Tag tool is doing my head in. I'm trying to tag walls using the default Wall Tag w Leader definition but no matter which mode I use it says 'no eligible object is selected' when I click on the wall. I've added a my text to the Mark field in the Data tab of my Wall Style. Is there something else I'm meant to be doing?
  4. Hi there! I am playing around with tagging truss objects. I wonder if there is an option to place the tag to the object center. By default it is always placed to the object insert point. I use "All Eligible Objects Mode" As trusses differ in size it is not an option to enter values to the "Auto-placement" -> "X offset" or "Y offset". I just want to have the tags placed to the center of the truss. Second I wonder if it is possible to have the tags to be orientated as the assigned object. They are always orientated as in the layout, no matter what the object is orientated. I don''t use leaders. In my screenshot I moved all the tags to the center by hand. Am I missing something? Thank You!
  5. Alright VW Friends, we need some help troubleshooting a particular workflow that has become problematic. The challenge... How do you create a legend that is specific to the items being identified by Data Tags within a given viewport using Records and Data Tags? Because this is a technical question, I'm going to have to get into the weeds a little with our particular challenge. We have grown particularly fond of using specific custom record formats, coupled with data tags, to more easily manage callouts/keynotes in a drawing. It is very easy to create "Master" legends that summarize specific information in a variety of ways for all "similar" objects across a drawing/file using isolation techniques like class, record format, layer, etc. The difficulty lies in using the same record information to query a subset of those objects that appear in specific viewports, and exclude those that do not appear. In the landscape architecture world, it is not uncommon to have projects where improvements span multiple sheets and/or viewports. These are typically separated by match lines. In the image below, we have a simplified scenario where improvements are divided into (4) different viewports... Notice that there are (7) objects in the drawing, each attached with the same record format and identified using the fields ID# and DESCRIPTION. The large circle, which is actually clipped into two objects by the serpentine "sidewalk", exists in all (4) of the viewports. In the attachments to this post are exports of each sheet layer as an individual image where it is possible to see that data tags, placed in the annotations of each viewport, can easily identify the objects by their ID#. I've also attached the VW file used to create this example. QUESTION: Now...how do you populate each of the unique worksheets with the items identified by the data tags (or even those that are clearly visible in the viewport)? The goal, given this example, is to provide legends (worksheets) that should include items as follows: Sheet 1 P-1 P-2 P-3 Sheet 2 P-1 P-2 P-3 Sheet 3 P-1 P-2 P-4 Sheet 4 P-1 P-3 P-4 You will also notice that the legends (actually worksheets in VW) do not correctly indicate the objects that are visible...or even those that have Data Tags. Sheet 3 doesn't include any...this is because our methodology, up until now, has been to use the Location...is within criteria in each unique worksheet to query the objects that fall within shapes that represent each viewport (gray dashed squares). For example, Schedule - Sheet 1, is querying ALL objects with 1) Record attached, and 2) Location is within Shape 01 Schedule - Sheet 2, is querying ALL objects with 1) Record attached, and 2) Location is within Shape 02 Schedule - Sheet 3, is querying ALL objects with 1) Record attached, and 2) Location is within Shape 03 Schedule - Sheet 4, is querying ALL objects with 1) Record attached, and 2) Location is within Shape 04 The problem arises because the Location...is within criteria only successfully queries objects where the Center Point falls within the identified Object. This is why Sheet 3 doesn't return anything but should include P-1, P-2, and P-4. There are technically two P-1s in this viewport because the large circle is being clipped by the serpentine path, but both of their respective center points fall outside of the Shape 03. Similarly the center of P-2, the serpentine sidewalk, is in Shape 02; and the center of P-4, the rectangular deck is in Shape 04. We have various workarounds to try and remedy this situation using this "Location Based" workflow, but they are needlessly complicated and result in errors that are difficult to track down and timely to troubleshoot. They are not worth mentioning and the goal of this post is to try and find another, better way. It seams to me that a solution might already exist, but as someone who knows VW quite well, I have struggled for a long time to figure out what it could be. A solution that does work, but we want to avoid at ALL costs is...clipping the objects by their specific viewports so that each object is firmly located "within" each specific viewport. This is a terrible method because it destroys all sense of greater geometry, creates more opportunity for error, and does not facilitate easy revisions if geometries require editing. I could think of two solutions, but both are NOT CURRENT functionality within VW that I am aware of: Query Data Tags and Report Their Linkage - The problem with our workflow is that it is querying the objects...not the data tags. It is possible to place the correct data tags on each sheet, regardless of where the object's center is, and it is possible to build a query/report of specific data tags on a given sheet layer. What IS NOT possible is to link the query of a data tag to the data of the object it is tagging. Intersection Criteria - If, instead of the only location based criteria being available being either "Is Within" or "Is Not Within", potentially adding an "Intersects With" option could mitigate the issue of an objects center point driving the query results. This is functionality common to many GIS software programs and it is one that I think could benefit a lot of use cases... Calling all helpful users to help figure out the best workflow for this @Eric Gilbey, PLA @bgoff @rowbear97 @Tony Kostreski @Vlado @Pat Stanford VW Sheet Legends and Data Tags.vwx
  6. With only limited experience, trying to bend a data tag to my will. Goal is to multiply or divide value in a calculated field by the value in a User Entered field elsewhere in the same data tag. Associated objects are just basic polygons with no record formats. Is this possible? The "items" in attached image do not need to be present in the drawing. I just input an area value of my choice in Field #2 of the Data Tag. Any comment welcome. -B
  7. Please make it so that when we input the value in the pop-up of the data tag that this info gets changed in the associated space.
  8. With Vectorworks 2022 I have about 10 data tag styles that are working. Now I want to create one that displays the wall width. I am close. In the Define Tag Field window: Data Source : Record Format Format Name : #Wall Record# Field Name : #Width# With this Tag Field Definition #Wall Record#.#Width# Result : 0.458 My guess was that it was the number of feet. After a little searching I edited the definition #Wall Record#.#Width# * 12.0 Result : 5.500 I ignored the extra zeroes and added a quote mark at the end to indicate feet #Wall Record#.#Width# * 12' Result : 5.4999960000000e00' I inserted a space before the quote #Wall Record#.#Width# * 12 ' Result : 5.500 ' My last step was to remove the last 2 zeroes, i.e. have a precision of 1. However, in the Define Tag Field window, the Units, Precision and Show unit/mark fields are greyed out. Question 1: What has to be added to the tag field definition to control the precision, in my case I want the result to be 5.5 I read the help here :https://app-help.vectorworks.net/2022/eng/VW2022_Guide/Annotation2/Creating data_tag_styles.htm?rhmapfs=true#CSH_2476 In the "Editing a data tag style" section, step 8 describes the "Current Tag Field Definition" and gives some examples but doesn't point to the "language reference". Question 2: Where can I find the "language reference", i.e. the syntax for the expressions that can be entered in the Tag Field Definition area? Thanks, Bill
  9. Correct me if I'm wrong, I don't use the data tag that much, when you press the reshape tool when selecting a data tag nothing happens. The reshape tool gets activated but you can not reshape the data tag. Why don't make it so that the reshape tool gets activated for the object associated with the data tag? This can be a space, but also a wall or window or whatever. So bringing back the reshape possibility when selecting the space label (like VW 2022 and below). And also improving the workflow for other objects.
  10. A big thank you to whomever engineered the Data Tag in Vectorworks 2022. Sitting in a tutorial today and the dreaded question... how do we tag Window Symbols when we have modelled a custom window? It's easy with the data tag! Create a custom 2D/3D Symbol, assign IFC catagory to the Symbol via the Resource Manager, and use the 'IFC Classification' Data Tag - symbol variant. A couple of tweaks and the Data Tag is picking up the 'Tag' value entered into the IfcWindow property set; the same one used by window styles. To demonstrate how the Data Manager works, we then map the 'tag' to 'reference' in Pset_WindowCommon, using a concatentation to floor level (layer) and window tag, via the data manager, set up a data sheet to see only the fields we are interested in in the ifc data structure, thereby streamlining the whole process, and export an IFC to show where the value ends up in an IFC via BIM Collab. The way the Data Manager now helps you define custom values is extraordinarily useful. The fact it tells you off when you get an 'invalid expression' is great! =concat(substring(L,'-'4),'-',IFC.'IfcWindow'.'Tag') ellicites a response of 'Comma expected'! =concat(substring(L,-,4),'-',IFC.'IfcWindow'.'Tag') and it says 'Invalid factor'! With wrist slapped, I try again. Bingo! =concat(substring(L,'-',4),'-',IFC.'IfcWindow'.'Tag') results in '00-W1' and is automatically entered into the 'Reference' field now visible in our 'Window Data Sheet'. All our data is now driven through IFC. Amazing! Things like this makes me happy.
  11. Hi All - I'm new to tags and trying to use them to display info about two things - 1) Finishes. If I've created a wall and given it a material there are finishes embedded. I'd like to be able to create a label or call out with leader line with finish info for that wall generated by the material. Is this possible? It would save so much typing and ensure accuracy. 2) Steel Members. I'd like to have a label as a call out and leader line that will draw from the type of profile used to create the 3D steel unit, such as W27x94. thanks!
  12. When tagging an object using a data tag, a connection between the two is established. I'd like to find a way to get the handle of the objects that was tagged by a certain data tag. In my mind a command could look like this hTaggedObj = vs.DT_GetAssociatedObj( hDT ) The only commands about data tags I could find in the developer wiki are these two: https://developer.vectorworks.net/index.php/VS:DT_AssociateWithObj https://developer.vectorworks.net/index.php/VS:DT_UpdateTagsOfTagged The List View Ex dialog of the debug mode wasn't much help either.
  13. Hello, Do we have possibility to have bidirectional workflow when using data tags with worksheets? I want to edit data tag text field from within worksheet and I thought that we can do it using DATATAGFIELD('fieldname')...but content of the text field is locked in worksheet... Is there maybe other option to achieve this?
  14. Hi, are there any possibilities to implement a substring and a count function in a VW 2022 Data Tag? Both are worksheet functions, however I didn't find them both in the data tag functions. (I suppose, because the "data tag" Plugin doesn't support them there) typing a substring command manually still didn't work.
  15. Is the recommended workflow to place Data Tags on a Design Layer or in SLVP Annotations? It works both ways, but I get a very long 'spinning beach ball' lag when I place it in an SLVP Annotation that I do not get when I place it on a DL. Once I get it successfully placed in a SLVP Annotation, selecting the Data Tag again to move it triggers another long spinning beach ball. I have also found out that Data Tags (at least the Door Dims one found in THIS thread) when placed on a DL do not scale properly with differently scaled SLVPs. So a Data Tag designed with a 10pt font placed on a 1:48 DL becomes 20pt when viewed in a 1:24 SLVP; in other words, it is 2x too large. Is this the expected behavior? Additionally -- using the Door Dims Data Tag from that other thread as my example -- I would like my door dimensions to show up as 36x80 (not as 3'0"6'8"), so I change the Units in the 'Define Tag Field' to Inches, Click OK, but when I reopen the Define Tag Field dialogue box, it has reverted back to Document Default Units. Thanks.
  16. I'm experiencing a bug where some of the Data Tags in my Section Viewports go blank. I've noticed if I drag the handle with the yellow exclamation mark slightly it will regenerate the text. Has anyone experienced this and figured out a way to regenerate the text to all Data Tags at once? VB-167804
  17. Hello, Am I missing something obvious... when trying to data tag objects (with record format attached) on annotation layer of viewport with 3D view I see highlighted eligible objects absolutely off rendered ones. You can see in background all three posts and other parts of structure scaled down and forming some kind of different view... My viewport use hidden line renderer and is up to date. Any clue?
  18. There used to be a ton (damn these puns) of control with hoist 2D display / label legends... Where did all of that move to in v2021? Are we supposed to use Data Tags now?
  19. When playing with data tags recently, I came across the fact that logical statements can be used in the tag field definition. The Vectorworks Help gives two syntax examples for a logical IF statement: VW2021 Help - Data Tag Page I can't seem to make the first syntax work. I have two circles that are exactly the same (with a record attached that has an INT "Number" field), and have replicated the first syntax in the top data tag and the second syntax in the bottom tag: The first syntax is a little more intuitive (for me, at least) which is why I'd like to use it, but if it isn't a valid statement I'll go with the second syntax. I did try removing the single quotes from around the numbers, figuring this might change the variables to INTs instead of strings, but to no avail...Can anyone replicate this? Is this syntax invalid?
  20. I would be a big time saver if it was possible to get the names of the object attributes in a data tag. A - The names of the fill styles: solid > color name hatch > hatch name pattern > pattern name and foreground and background color names tile > tile name gradient > gradient name image > image name when the fill style is set by class then then specified name in the class fill style B - The names of the pen styles: solid > color name pattern > pattern name and foreground and background color names line type > name of line type and name of color when the pen style is set by class then then specified name in the class pen style C - The line thickness D -The number of the marker Usercases: part B of this discussion: https://forum.vectorworks.net/index.php?/topic/79632-renderworks-textures-in-worksheet-name-of-color-in-a-data-tag/#comment-379286
  21. Data tag is not accessing all available stair object parameters. It would be great to have stair data displayed at he right size in different scale viewports (just like window and door tags). It is strange though that for instance in simple stair I can get R&T size and fl to fl, not the number of risers though, in new stair tool only fl to fl and a lot of other parameters which I doubt anyone uses. Seems like an unfinished project with stair tool (again).
  22. Data tag is not accessing all available object parameters, in this case stair. 2020 has some and 2021 has even less parameters listed, is this on purpose? or should all stair parameters be accessible in the data tag?
  23. Hello Folks, I hope this is possible. I am trying to populate text within a data-tag with information drawn from a database. I have created a database and associated it with a record format. In the data tag, I have selected the text that I want to populate with the information from the database and it seems like it should work but it doesn't. It just displays the placeholder text. I've attached screen grabs of the settings. Any help would be appreciated! -Dylan I'm on VW 2020 SP1 (but updating to SP5 as I type) Please ignore the actual values, I was experimenting with how to enter information.
  24. When tagging windows in elevation I don't want to tag all eligible windows in the model. I just want to tag windows visible in my elevation (and I don't want to have to take every single window separately either, which is currently the only other option).
  • Create New...