Is there a complete list of commands you can use in Auto-text?

I’ve been putting 2023.1 to task and can see a huge improvement in Layout’s performance! Well done!

Looking at many of the new commands in auto-text enabled scrapbook entities I’m wondering if someone has compiled a full list; they don’t appear on the website Auto-Text Tags. I see more included with this update such as: <Coordinates(z)> and in the previous update: etc. I’m looking for a complete list that can be inserted.

Thank you in Advance
Randy

Interesting ‘SceneDescription’ within <> disappeared when I hit enter yet ‘Coordinates(z)’ didn’t.

I don’t know of a complete list. It’s probably endless for label Auto Text since any text fields for components can be used. This includes fields added as Dynamic Component properties which can be custom fields. You can also create an endless list of Auto Text entries for regular text boxes in Document Setup.

I don’t see SceneDescription going blank. I could induce it to go blank if I put a space in the Scene Description field in the SketchUp file. I did that for the scene used in the top left corner but I didn’t put anything in the description for the one at the lower right.
label3

Please update your forum profile. It says you’re using SketchUp 20.

Without getting into dynamic components… I think these are the remaining ones not referenced in the Auto-Text Tags link:

SceneName, SceneDescription, Scale, Ratio, ComponentDefinition, ComponentDescription, ComponentInstance, ComponentDefinitionAttribute(Price), ComponentDefinitionAttribute(Size), ComponentDefinitionAttribute(Url), GroupName, Volume, FaceArea, EdgeLength, Coordinates(x,y,z), Coordinates(x), Coordinates(y), <Coordinates(z)>

1 Like

Oh and SectionName, SectionSymbol

Thanks, Dave

I was looking into the component attributes before I made this post to match some of the new ones there; now I think you confirmed what I was suspecting. Thank you. The second ‘Reply’ I made was about adding the brackets, <>, in this (forum) text box. 2 sets of text disappeared when I hit publish, which was odd. Didn’t happen in SU. N Mason posted a great list below. (above)

Thank you! This is a great help.

Was looking at the SU Functions and I think I’ll check if (“materialName”) will return the Material; ie Paint colour on a wall and in a Table FACEAREA(“materialName”) for the total area in the model. Could be useful for take-offs, have to play…

Thx again.

Hi all, here is a complete list of our AutoText tags.

I will work to get the help center articale updated with them as well.

Default Non-mandatory ones

  • Author
  • Company
  • Address
  • PageNumber
  • PageName
  • FileName
  • CurrentDate
  • DateCreated
  • DateModified
  • DatePublished
  • PageCount

Mandatory ones

  • GroupName
  • ComponentInstance
  • ComponentDefinition
  • ComponentDescription
  • Volume
  • FaceArea
  • FaceLength
  • Coordinates
  • DynamicComponent
  • Classifier
  • ComponentInstanceAttribute
  • ComponentDefinitionAttribute
  • SceneName
  • SceneDescription
  • Scale
  • SectionName
  • SectionSymbol
  • Ratio
3 Likes

Thank you very much!

Hi all!
…I’m very interested into this topic, since I developed a huge library of DCs for my company.
My aim would be to prepare a scrapbook with pre-designed labels drawing the DC attributes NAME and ITEMCODE. I can’t get them to work, since it seems that layout isn’t able to recognize WHICH nesting level it must scan to find those two attributes. In my case, it’s always the first nesting level.

In the cases I tested, I see that if I use the preset autotext labels coming in the standard SKP installation, I get the information (we have ComponentDefinition and ComponentDescription, fields which I don’t have the need to report), but instead if I manually create a label with <DynamicComponent(name)> autotext, it reports nothing.

After a quick investigation, it seems that “AutoTex labels” look for Dynamic Component attributes in the first nesting level over the geometry, so:

  • If a DC has nesting level 1,2,3 and then the face, Layout searches for the attibute in Nesting level 3
  • If a DC has nesting level 1,2 and then the object face, Layout searches for the attibute in Nesting level 2

Is there a way to tell layout to look for the Attribute through all the nesting levels? In my case, Itemcode would be present always and only in nesting level 1