Problem with Teamwork views linked to PLN file

[Achille Pavlidis]

I have a large project with a teamwork file and several pln files. To manage the drawings i created a separate PLN file just for the drawings, where i have linked the views from the various files.
Today when i wanted to update the views of the Teamwork file, i get this error message: "Unsent changes in your source project are preventing the status checking process.
Go to the project and send your changes to the Server, then press the Check Status command again in the current project."

I did Send and Receive a lot of times, but to no avail, i cannot update my views. Even if i delete them and re-link them i get a blank drawing.

What can i do???

[Noemi Balogh]

Sorry, if I misunderstood something, I didn't read all previous comments.

What I believe causes your issue is that you try to modify something which should be reserved, and as in solo you can't reserve elements, it fails.

What if you try to reserve everything in the project and then link it to a PLN?

Also, I suggest to contact your local support to start an investigation, they can involve our support team to help as well.

[Achille Pavlidis]

Hi Noemi, thanks for the answer

The problem is as follows: There is a PLN file, with a linked Teamwork file. I want to place on a Layout of the PLN file a view of the TW file. Every time I try to do this, I get the error message that "Unsent changes in your source project are preventing the status checking process" and the process fails, even if everyone has sent changes from the TW to the server.
This is a problem I have faced in the past, that was never addressed by Graphisoft, and I thought it was resolved in recent AC versions, only to resurface again with AC24

[Ignacio Azpiazu]

I think I always ended up regretting it when in multi-file projects I didn't go old school by publishing to PMKs and linking to those, instead of linking to views. With multiple files and file types, and even changing file types (a file changes from PLN to TW, gets back to PLN, gets a design variation filename-test-2, and a simultaneous filename-test-3, and nobody knows which one will prevail; some modeling pln gets large and gets broken down into two), PMKs don't care where they come from—one can just republish and overwrite them from any source; PMKs only get updated when you want them to update, and everything is faster because strictly the necessary information is being transferred and Archicad does not need to “open” another pln/tw file to link/check/update. Troubleshooting is much easier also, because the process gets broken down in steps.