Filter items in CAD from Stratus custom properties

[aoslos]

Is there a way to do a "Mapfilter" or "Selectfilter" command for custom properties? Say in CAD I want to isolate all items in a specific Package, can I do a filter based on the "STRATUS Package Name" property? 

[davidratx]

Not sure you can do Custom Data with MAPFILTER but you can add Custom Data to SELECTFILTER

[aoslos]

YES!!! It worked! Thank you very much!

[Joe Kuhr]

If you add the Custom Data field to your CADmep List (see attached) you can also use LISP to make the selection.

Code: [Select]

(defun c:SelectStratus( / STRATUS)
(command "undo" "m") ;_undo mark
(setq STRATUS (ssget "X" (List (Cons 300 (getstring T "Enter STRATUS Package Name: "))))) ;_creates selection from user input.  Note, this is case sensitive.
(command "zoom" "object" STRATUS "") ;_zoom to selection
(sssetfirst nil STRATUS) ;_Select selection
(princ)
);_end defun


[mdomer]

Has anyone tried to package in CAD and push up to Stratus?

In theory, this would streamline the process and would avoid extra model uploads.

Stratus is kicking back on certain CAD items, it would be much quicker to fix it in cad without having to re-upload only to have Stratus complain again.

Edit: I just added "test" to the 'stratus package' data field on a piece and uploaded to Stratus. It didn't take.

[mdomer]

Joe,

Since I'm not a lisp expert, I have an additional question about your fancy filter. Would it be possible for someone to take it a step further and instead of entering the entire package name, maybe just enter the 3 numbers at the end?

In Excel, it would be something like RIGHT(3).

I did look through a lisp book I have and didn't find what I was looking for.

[Joe Kuhr]

mdomer,

For you issue with Stratus overwriting items changed in CAD, have you tried playing with the Admin > Settings > Specific to AutoCAD > Assembly Conflict Resolution?  This might work with Packages, too.  In the event of a conflict, the setting allows you to pick if Stratus is always right, AutoCAD is always right, or if the user should be prompted.

As for the LISP, yes that should be achievable.  You could also use a * wildcard with the code above.  if you wanted to find package 123-456-789, I believe you can search for *789.

[madcad]

As for the "Assembly Conflict Resolution" Setting. I had mine set to Revit is always correct. I created Packages and Assemblies in Stratus.
Re-Published the model from Revit, My Packages remained in Stratus but my Assemblies were deleted. I guess it only applies to Assemblies.
We have tried pushing Packages from Revit to Stratus using the Package parameters without success.

[mdomer]

MadCad,

I believe Stratus assigns unique id's to each piece/part/assembly so that could be the reason you were unsuccessful in pushing packages from Revit to Stratus. Revit wouldn't know what id to assign to a part.

I feel your pain on assemblies, a couple months ago before a big update came it deleted my assemblies as well. It seems to be more stable these days. I made a habit of creating copies before publishing for instances like that.

One of the biggest tips I have is after renumbering packages, you must import back to Revit/CAD and save.

Joe,

In my experience the command line doesn't take well to "*" so I'll play with it a bit to see if I can pull a rabbit out of a hat.