Teamwork: Complex Profiles can be edited even when reserved by another user.

[Mechiel]

When working in a Teamwork project, if someone else has reserved the Complex Profiles settings, it is still possible to create a new profile or duplicate an existing one, without the settings being released first. This causes “Send & Receive” to get stuck. At that point, the only way to save your work is to force-remove the other user or wait until they release the reservation.

It would be better if all Complex Profiles functionality were blocked until the user releases it. As it is, I sometimes keep drawing for quite a while, only to find out that I can’t send any of my changes unless I take the drastic step of force-removing someone. Unfortunately, it happens quite often that items turn out to still be reserved by someone who has the day off.

On that subject there is a checkbox that enables you to release when closing a file. Could this not be made the default setting strait out of the box?

It would be great if this could be fixed. 

[Lingwisyer]

All Attributes are like that. Without reserving, as long as you have permissions, you can CREATE NEW attributes. You will not be able to EDIT any EXISTING, as you obviously have not reserved anything. I have not run into any Send & Receive issues due to this though, attribute management issues being seperate...

I believe there is a wish somewhere regarding Release on File Close.

[Stefan L_]

---

@Mechiel   schrieb:

... the only way to save your work is to force-remove the other user or wait until they release the reservation.

---

I'd switch this to:

The only way to save your work is to wait until they release the reservation (or force-remove the other user).

While you are waiting to send your "Profile One", the other user might have created his "Profile One".

This would lead to a 'Clash of the Titans' (or whatever you profiles are made of).

Blocking is no option, if you copy&paste an element based on "Profile One", the latter will (and must) be created.

As Ling states, this is standard behaviour for all attributes.

So:

Getting a coffee while having attributes reserved is bad style, but happens nonetheless.

Kick'em, they'll learn it the hard way. 👹

[Lingwisyer]

Indeed. When working in TW, I feel like you should enforce that people release EVERYTHING if they are leaving for an extended period of time, whether that be stepping out for a coffee or leaving for the day. If you are not actively utilising things, they should not be reserved.

Though on the topic of blocking things, settings dialoges should really be locked when they are no reserved, instead of letting you edit things, then silently close when you press enter... Pretty sure I made a thread about this somewhere...

[Stefan L_]

---

@Lingwisyer  schrieb:

... people release EVERYTHING if they are leaving...

---

I'm pretty sure this never happens to me.

Well... 🤣

IMHO the whole logic is cool and OK, but maybe a little warning could be helpful?

"You just created/imported the complex profile 'Profile One', it might be tricky to send..."

But there's a TW bug concerning MVO at least up to AC27 (maybe only GER version).

When opening the dialogue 1st time, all elements are active, including the OK button.

Changing an existing MVO definition 'works', but every dependent view reports a missing MVO...
Can't wait to check AC30, but we have no BIMcloud yet. 🤓