Hello.
When I delete some fields from configuration objects and then try to save the configuration to repository I receive this message:

Usually when I lock all roles it goes right, but sometimes, when I try to lock all roles, it shows me other message:


but these objects are already locked. So, then I have to release lock on them and lose all changes that I made. It doesn't happen very frequently, but when it happens it is very inconvenient.

Hello, Mikhail!

If you have problems that require you to release objects without committing changes, you can save your current configuration to file, release objects, obtain locks and then merge the obtained configuration with one, that you have saved to file.

Regarding problems with other objects that require to be locked when you delete some other objects, this is caused by references that those objects have. You can see which objects have references to one that you are going to delete by right-clicking on that object and then clicking Find references to object.

Hello.
I know this way to solve the problem and also understand why it is asking me about locking roles to clear some references, but why it is asking me to lock again already locked object?

Can you provide screenshots for this problem?

I have the solution for this problem:
http://1c-dn.com/forum/forum17/topic935/

Timofey, it is really annoying this problem. Sometimes it takes more than 20 minutes to save to separete file, reverse changes and merge again. If there are more than 2-3 persons have locked objects, it is a noticable loss of time.

I will help wou with screenshots when it'll happen again. Basicaly you need to delete any object which are referenced by roles.

Thank you, Alexey.
I will doublecheck if there is some recommendation for your case. But I suppose the best solution is to make the application structure more granular and assing tasks to employees according to parts of application that they develop. Plus maybe it will be better to develop on a copy, and merge and commit changes only when a the task is completed.

Yes, Alexey, the standard says that when you develop a new functionality, you create a new (not a copy, but new) configuration repository, develop entire the enhancement project, and when it is tested, you apply changes to the main repository and test again. This allows to make developers independent, especially on large projects.