Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I've attached a drawing that shows an explanation of what I'm trying to accomplish.
1234P1 1/4 Plate Qty 2
The "1234" is an example job number that would update using fields under drawing properties. The "P" is the part number. Ideally the P# would self count as the block is copied across the drawing. The plate thickness and quantity would be manually updated in attributes. Plate thicknesses would include- 1/8, 1/4, 3/8, 1/2, 3/4
My goal is to make a block out of the text that can make identifying parts quicker, easier and more error free. Can someone please make me a block that I can use to accomplish this and maybe I can reverse engineer how to make this work on my own? I've been trying to figure this out for awhile and have been struggling to understand how to make it work. Thanks in advance!
As far as I know, there is not any way to make separate insertions of a block automatically number themselves differently, at least not without custom coding. In ACA (and probably other verticals) schedule tags have that ability, but not dynamic blocks.
Are you having difficulty getting the job number field working?
The rest would be manually updated, so they seem easy enough.
The job number field is easy enough, and I’m able to get that. I’m pretty sure there is a way for it to count itself. I’m just not familiar with attributes enough to make that part work.
Any block with visibility states will always insert on the same default state. You would then need to manually switch the state (or use custom code), so that is just a more complicated method that is no more automatic than just manually changing an attribute value.
