linking markers between projects

[Patrick M]

I have a project team that wants to put their details in a separate file. 
the project has an architecture shell/core team, and an interiors team. The interiors team wants their details separated out for simplicity, and to avoid unnecessary pollution when pulling cut sheets, other project's details, etc. in.
My plan is to create a blank file, hotlink the main project teamwork file in, then they can draft details from the hotlink, updating when necessary.
...
My only sticking point is that we want to be able to reference the detail views drawings/layouts from the interiors model into the shell/core model. I really want to avoid views > layouts from file B to file A; updating those is a PITA that I will avoid at almost any cost. 
Is there any other option ya'll can think of to make this workflow happen and properly reference the details (manual text in det markers is 100% NOT an option)

Operating system used: Mac Intel-based

[Lingwisyer]

Just clarifying, you are wanting the reference marker to the detail in one file while the referenced layout is in a second file?

[MitchD]

exporting PMK's from file B and linking them in file A is a muuuuuuuuch quicker and cleaner way of showing drawings from another file. as long as they are published after any changes, they work seamlessly.

[Patrick M]

it just seems a bit antiquated to cling to .pmk as a workflow... I remember the plotmaker days, and really don't want to go back to them.
...
@Lingwisyer, we want to draw the details in file B, place them to layouts in file B, but have linked markers referencing those layouts/drawings in file A.

[Stefan L_]

---

@Patrick M  schrieb:

... but have linked markers referencing those [file B] layouts/drawings in file A

---

Because you want to:

- [in file A] open the floor plan, click a marker and beeing beamed to that content in file B?

- [in file B] select a drawing and beeing beamed to the linked marker in file A?

Sounds quite impossible to me, but I'm here to learn. 🤓

We keep main TW model and detail TW seperated since ages, for different reasons:

- file size, performance

- less TW reservation conflicts

- detail TW is 'outlaw territory'; content is pasted from everywhere (including late '90s attributes...)

- 1:50 main model content seldomly suits details (section through window? No, thanks...)

So: manual text in det markers is 100% NOT an our only option

We use a quite dumb lib element as marker BTW: