Bug Wbloc, Field, custom properties

Bug Wbloc, Field, custom properties

didier_lourdelle
Collaborator Collaborator
1,401 Views
10 Replies
Message 1 of 11

Bug Wbloc, Field, custom properties

didier_lourdelle
Collaborator
Collaborator

Hello


The use of custom properties 'DWGPROPS' with fields in a Text, Mtext, Attribute this in a WBLOCK are not resumed in the file!


The custom properties and their values are lost.

 

Didier Lourdelle

Didier Lourdelle EESignature

Industrialisation AutoCAD / AutoCAD LT – 2D / 3D
Architectures AutoLISP & .NET maintenables
Références industrielles, notamment AutoCAD Electrical
(contexte exigeant, architectures éprouvées)
Blog : Trucs & Astuces sur AutoCAD LT (2024+)

0 Likes
Accepted solutions (1)
1,402 Views
10 Replies
Replies (10)
Message 2 of 11

pendean
Community Legend
Community Legend
Please explain in more detail (feel free to use your native language too, many that read these forums are multi-national).
0 Likes
Message 3 of 11

Alfred.NESWADBA
Consultant
Consultant

Hi,

 

just tried it, started WBLOCK, selected "EntireDrawing", gave it a filename and pressed OK to create the drawing.
Next step was that I opened this drawing, started DWGPROPS and the properties are valid (with all the settings I did in the original drawing.

 

So the question is, what are you doing different or what product do you use that might be different to my test scenario with AutoCAD 2016 SP1.

 

- alfred -

------------------------------------------------------------------------------------
Alfred NESWADBA
ISH-Solutions GmbH / Ingenieur Studio HOLLAUS
www.ish-solutions.at ... blog.ish-solutions.at ... LinkedIn ... CDay 2026
------------------------------------------------------------------------------------

(not an Autodesk consultant)
0 Likes
Message 4 of 11

didier_lourdelle
Collaborator
Collaborator

les manipulations en video, sur AutoCAD 2015 Electrical French. (Le problemes est sur plusieurs version....)




 

 

 

 

Didier Lourdelle EESignature

Industrialisation AutoCAD / AutoCAD LT – 2D / 3D
Architectures AutoLISP & .NET maintenables
Références industrielles, notamment AutoCAD Electrical
(contexte exigeant, architectures éprouvées)
Blog : Trucs & Astuces sur AutoCAD LT (2024+)

0 Likes
Message 5 of 11

Alfred.NESWADBA
Consultant
Consultant

Hi,

 

thank you for the video, but sorry that I'm not understanding French, so I may miss something.

 

If you copy a field pointing to drawing-properties into another drawing, which does not have any properties assigned, the field lost it's source of information ... with other words it can't find in the new/current drawing the property-names, so it does not have any chance to write a value to the screen.

 

If the drawing to which you copied the block already has the same properties assigned (by DWGPROPS) then the copied field will fill the values well.

 

- alfred -

 

------------------------------------------------------------------------------------
Alfred NESWADBA
ISH-Solutions GmbH / Ingenieur Studio HOLLAUS
www.ish-solutions.at ... blog.ish-solutions.at ... LinkedIn ... CDay 2026
------------------------------------------------------------------------------------

(not an Autodesk consultant)
Message 6 of 11

didier_lourdelle
Collaborator
Collaborator

For me this is a bug copy and paste a block if not now added to the drawing, a style, a line type , layer ...

Pour moi il s'agit d'un bug un copier-coller d'un bloc si pas présent ajouté au dessin, un style, un type de ligne, un calque ...

Didier



Didier Lourdelle EESignature

Industrialisation AutoCAD / AutoCAD LT – 2D / 3D
Architectures AutoLISP & .NET maintenables
Références industrielles, notamment AutoCAD Electrical
(contexte exigeant, architectures éprouvées)
Blog : Trucs & Astuces sur AutoCAD LT (2024+)

0 Likes
Message 7 of 11

Alfred.NESWADBA
Consultant
Consultant

Hi,

 

>> For me this is a bug

To be honest, not for me.

If you create a field which shows the area of a hatch and you copy that field object to another drawing (without copying the hatch) this field can't show an area of an object that does not exist. So my understanding is when the other drawing does not contain the DWGPROPS it can't show a value in the same way as the area of a hatch that does not exists.

 

But if you would like to have that modified you can report this to Autodesk either through your subscription center and open a support case or create a feedback >>>here<<<.

 

- alfred -

------------------------------------------------------------------------------------
Alfred NESWADBA
ISH-Solutions GmbH / Ingenieur Studio HOLLAUS
www.ish-solutions.at ... blog.ish-solutions.at ... LinkedIn ... CDay 2026
------------------------------------------------------------------------------------

(not an Autodesk consultant)
0 Likes
Message 8 of 11

dbroad
Mentor
Mentor

As Alfred is saying, this behavior is not a bug.  If you want to keep the drawing summary, wblock the entire drawing or use saveas to a new drawing name and then erase the objects you don't want in the new drawing.  The drawing summary properties are not properties of the objects being copyclipped but of the drawing itself.  When using copy/paste with fields, the fields will always be broken when the objects they reference become unavailable. 

 

If you want to keep the field information when copycliping/pasteclipping to a new drawing, but do not need to keep the linked relationship, explode the fields before the copy/paste.

Architect, Registered NC, VA, SC, & GA.
0 Likes
Message 9 of 11

didier_lourdelle
Collaborator
Collaborator
Accepted solution

Ma solution :

j'ai développer des commandes pour arriver à reprendre les informations rapidement d'un autre dessin.

My solution :
I develop order to reach resume information quickly with another drawing

Didier Lourdelle EESignature

Industrialisation AutoCAD / AutoCAD LT – 2D / 3D
Architectures AutoLISP & .NET maintenables
Références industrielles, notamment AutoCAD Electrical
(contexte exigeant, architectures éprouvées)
Blog : Trucs & Astuces sur AutoCAD LT (2024+)

0 Likes
Message 10 of 11

cschnarr
Enthusiast
Enthusiast

Hi Alfred. I am working on a problem that fits what you described here as being successful. I have a full set of custom drawing properties that I use for title block fields and other block attribute fields. When I WBLOCK the whole drawing, including all the attributed blocks (placed in model space and used), the new drawing created has no custom drawing properties left in it. You mentioned that when you did this all your drawing properties are "valid" in the new drawing. Are you only referring to object based geometry properties? Because in DWGPROPS my custom tab comes up empty. I need to preserve all these custom drawing properties. I am using WBLOCK to try to dump some AECB block garbage that cannot be purged.

 

AutoCAD 2019 

 

Although every single custom drawing property in the drawing may not be "filled in" most of them are but they are all deleted by WBLOCK. I need to find a way to preserve these but create a "clean" template without all the AECB junk.

 

Please clarify how you are able to keep drawing properties intact using WBLOCK.

0 Likes
Message 11 of 11

cadffm
Consultant
Consultant

 

 

 

 

Because you wrote "the whole drawing, including all the attributed blocks" and not "entire drawing", I think your statement is not correct.
I have just tested 2019.1.2 and the command WBLOCK with the option 'entire drawing' creates a DWG as expected with the custom properties,
What is the right behavior in 2016 and 2019, like all other version too.

 


@cschnarr  schrieb:

Although every single custom drawing property in the drawing may not be "filled in" most of them are but they are all deleted by WBLOCK. I need to find a way to preserve these but create a "clean" template without all the AECB junk.

Do you mean "AEB" from AutoDESKS products? The command to convert a file to a plain AutoCAD DWG is _-AECEXPORTTOAUTOCAD, not 'WBLOCK' !?

 

Please clarify how you are able to keep drawing properties intact using WBLOCK.

Start WBLOCK command, use the 'entire drawing' option - thats all, it works on our side as expected.


If you have Problems with _-AECEXPORTTOAUTOCAD and AEC stuff, start a new threads with a detailed explanation and a sample file,

(which ways tested without success, what ObjectEnablers are running,..)

i am sure you get help to solve the problem if possible.

 

 

Sebastian