Bind link with phasing

[Anonymous]

Please,

I wish some Autodesk valiant engineer to reply with instructions on how to bind a linked model MAINTAINING the phases of each elements...?

Yes?

Revit 2020...

thank you

[Anonymous]

@Anonymous  when you BIND a link into a file, the objects of the link model are "created" in the host file and the link instance ceases to exist. On doing that, this new objects of the bind link are created in the phase of the view where you commanded the bind. Revit applies this same phase as the PHASE CREATED for all the objects of the link that are bind. The PHASE DEMOLISHED, however is not assigned to any of the bind objects.

To circle the phase created issue, I use phase filters and phases to bind the objects to the correct phase created. I haven't find a way to set the phase demolished during the bind process, however. I reset all demolished elements to the appropriate phase manually.

Hope it helps.

[Anonymous]

But how do you "circle" the phasing assignment of the binder objects?

We have existing and new construction objects in the same linked file, the liked file phasing mapping is correct, but once binded ALL objects are placed in the current phase...

[Anonymous]

Hi Giovanni, first let me understand your needs. Why do you want to bind
instead of coping? Any special objective? Or was it the way you found
better to copy a model to another model file?


Now let's see your issue:

The BIND tool is not meant to copy the objects of the linked file, but
rather to create them as new objects in the main file (host file). Hence,
the assignment of the current phase from the view where the selection of
the link to be bind was made into the "phase created" for this new bind
objects. Bear in mind that the phase filter set on the view where the link
selection is made also interferes with the selection of the bind objects as
the phase filter is applied to the visibility of the linked model objects
in that view. In a nutshell: you go to a view; select a link to be bind;
only the link's objects that correspond to both phase and phase filter
criteria of that view you are in are bind to the model; Revit assigns the
same phase of the view where they were selected to the binding object's
"phase created" system parameter. No value is assigned to "phase
demolished" system parameter of those bind objects.

To copy a model's objects maintaining all it's original properties use the
copy/monitor tool and then stop monitoring all the elements you've copied.

[Anonymous]

Ricardo,

regrettably your description of how the "bind" feature works does not seem to be correct.

Binding a linked model moves *all* its elements into the current phase, even elements that are not visible because of the current phase filter.

I have binded a building with a "DEMO only" phase filter, and view set to New Construction. Only elements demolished in the "New construction" phase were visible in the view, yet *all* the building elements were moved into the current model, and thus phase. I was left with the whole building in the New Construction phase (including existing and demolished elements).

This is an old issue.

Binding linked models should at least provide an option to preserve the phasing of the linked elements.

Linked files have type property that allows to map the phasing of the linked model to the host model. Once there is the need to bind the linked model, why would anyone want to "flatten" all phasing into one?

In what circumstances would *that* be a desirable outcome?

Thanks

Gio

[ToanDN]

Binding links with phasing has always been a losing battle so try to avoid doing it has much as you can.

When you must, open the link file, add a text parameter [Phase], set the view's phase status and phase filter to isolate elements of each phase (e.g. existing phase to remain; or existing to be demolished under phase 1, etc...), select them and type in the [Phase] field. Repeat until you enter the value reflecting the phase created and phase demolished for all elements. Now when you bind the link, you can filter elements by [Phase] and reconstruct their phase created and phase demolished.

[Anonymous]

Hi. Why don't you try to copy your linked model instead of binding it. With
copy you can achieve what you need.

[Anonymous]

---

@Anonymous wrote:

Ricardo, regrettably your description of how the "bind" feature works does not seem to be correct. Binding a linked model moves *all* its elements into the current phase, even elements that are not visible because of the current phase filter.

Hi, Giovanni, the part were wrote: "Bear in mind that the phase filter set on the view where the link selection is made also interferes with the selection of the bind objects as the phase filter is applied to the visibility of the linked model objects in that view. In a nutshell: you go to a view; select a link to be bind; only the link's objects that correspond to both phase and phase filter
criteria of that view you are in are bind to the model"  is not correct. Please disconsider this info and accept my apologies for this wrong information. As you've said ALL the link's objects are copied as a group to the host file.

[Anonymous]

Hi,

to copy over several hundreds elements does not work really.

Revit make the error "Cannot copy to clipboard because of relationship between elements" if I try dragging a window on the model, in a 3D view.

If I have to pick each element and copy / paste across, I may as well bind the link and manually move the new elements to new construction, demo, etc.

Also, remember that the link file is being documented (views on sheets, annotation, tags...).

When I bind the link file, more annotations are likely to survive the transition than copy pasting elements one at a time.

In any case, this is obviously a big issue that Autodesk must resolve, so that we can properly embed linked models, when needed.

Thank you

Gio

[sdurkee_sa]

Everyone who comes across this post, please vote for the "Bind Revit Link - Maintain Phases" idea at https://forums.autodesk.com/t5/revit-ideas/bind-revit-link-maintain-phases/idi-p/7464661 

[awasyliw]

Done. I can't believe that post is from 2017 and we are still having to push for it.

[GaryOrrMBI]

It's 2024 and, working in Revit 2023 and we're still having to jump through hoops...

Voting the idea up...

[b.ross]

Ah another day of hitting my head against a brick wall. Thanks Autodesk.