i can just without thinking a lot find lots af reasons:

- You (or the actuall loggin in user) does not have editor access on related bim+ project any more
- No internet access during that process
- lost connection between allplan project and bim+ project
- unsuffizient project space in bim+
- error in allplan 3+ modell
- error in allplan ifc structur
- temporarly error on bim+ server during this operation
- .... end i think someone less will find much more reasons ...

to reduce this list, you can check some of the points and maybe some more infos may help to point into the right direction.

- is this connect account also used in allplan as account for the upload ?
- used allplan version (exact f.e. 2017-1-3 )
- use operating system
- firewall ? virus scanner ?
- does the problem occur twice with same modell and same change ? (so if you change anything else and update the model to bim+ does the problem occur again ?

- exact date and time when you upload the modell update (maybe there is some error on our server log)

and maybe we need more infos like : name of the team and name of the project for a better research ..

Hi ricmerz,

thank you for recording the video. It would be helpfull if you could send me exported zip-ed allplan project where you expereienced this problem. Ideally if you send me dropbox link to private message here in forum. I'm then going to analyze it and find out root cause.

Pavol Nagy
bim+ Product Owner

Dear Mr. G. Ballesteros,
the problem is quite a complicated, it's not a pure bug. The whole update is working based on so called update flag. This means, once you make an export from Allplan into bim+, the next one is update only, means changed elements are updated, new are added and deleted are deleted too. The layer visibility flag is here not considered. Reason is, after set it back to visible, there's no information about this element need to be updated again because the object itself is not updated. therefore also trick I'm told you does not worked sufficiently. To build it such a logic is a quite a dangerous, there could be a lot of confusion about. Instead of that we will build an "force update" checkbox into export dialogue which means by that user can decide to update everything what's currently loaded independent from the layer status, visibility flag, exporting state etc. etc.
But this we cannot achieve for any 2017 Service release as we had discussed, we will build it into Version 2018 first.
We are apologising for the inconveniencies and tanks for the useful hint.

E. Mrazek.