ACCESS EXTENDED DATA???

[treaves04413213]

I have attached a screen shot of my properties menu of what I am trying access via autolisp or visual lisp. I am trying to sort the electrical devices in my plan by the style name that is in the extended data (or key). All devices are on *-elec-fx-* layer. when I use (entget(car(entsel))'("*")) to view the xdata the information I am looking for is not there. (see attached extended data2.png). How can I get to this information? I am trying to avoid making a layer for every device and filter it that way.

I am needing to count the number of each device and then send that number to a variable where I will then use a field in a table to autofill the table.

Thanks in advance for any help.

[dgorsman]

Not everything holds its information in XData. The information may be stored as XRecords in a dictionary on the object; or references to XRecords in a dictionary on the Named Object Dictionary; or through properties embedded in the object that are not accessible through LISP.

[treaves04413213]

Could I access it via .net? If so does anyone know how?

[treaves04413213]

I made a post on cadtutor and someone posted the lisp below. This will dump everything associated with it. I was able to get the data I needed listed beside Name (RO) =. Look at the attached png and you will be able to see what all it returned. Now I just have to figure out how to filter for this data. Any ideas? Should I call the dumpit function and then filter for what I need in the return or is there a way I can just get the info I need to return?

;;;===================================================================; 
;;; DumpIt                                                            ; 
;;;-------------------------------------------------------------------; 
;;; Dump all methods and properties for selected objects              ; 
;;;===================================================================; 
(defun C:DumpIt ( / ent) 
  (while (setq ent (entsel)) 
    (vlax-Dump-Object 
      (vlax-Ename->Vla-Object (car ent)) 
    ) 
  ) 
  (princ) 
)

[dgorsman]

From my post on one of your other threads, you *really* need to read the API for your product. It will describe the methods and properties applicable to the objects.