Autonumbering failure in 1C Entreprise


If you wish to leave comments or ask questions, please log on or sign up.

This forum is intended for cases when a problem can not be solved due to restrictions of the platform: a bug or lack of functionality.

#1
People who like this:0Yes/0No
Active user
Rating: 3
Joined: Jul 24, 2017
Company: Smart ID Dynamics

Hello guys.
I have a small problem which I don't figure out how to fix it. I have a Workorders Document which, by default, has the field "Number" that is set to Autonumbering and Check uniqeness ( You can see in the photo ).
A while ago an error occured ( You ll see in the photo ) that the field "Number" which is autocompleted by the platform is not unique.
Does anyone have any ideas why this happens?
Thanks,
Lucian.

 
#2
People who like this:0Yes/0No
Administrator
Rating: 4
Joined: Dec 4, 2017
Company:

Dear Lucian,

Could you please provide us with the following information:

- 1C:Enterprise platform version
- steps to reproduce the issue you described
?

Best regards,
Vladimir Gurov

1C Company support team
 
#3
People who like this:0Yes/0No
Active user
Rating: 3
Joined: Jul 24, 2017
Company: Smart ID Dynamics

Hello Vladimir,
The platform is 1C Enterprise 8.3.9.2309.
This error happend when a client wanted to create a new document ( workorder ). I don't really know more details of how this happened. I tried to recreate the enviromnent which generated this error, but this was a fail. The autonumbering worked perfectly when I tested it and, until now, this never happened.
Do you have any suggestions for me?
Thank you for your reply.
Best regards,
Lucian Rada.

 
#4
People who like this:0Yes/0No
Active user
Rating: 3
Joined: Jul 24, 2017
Company: Smart ID Dynamics

Hello again.
I found a method in the platform. RefreshObjectsNumbering(Metadata.Documents.Workorders). What do you think? Does this work without modifying the existing code?
I am waiting for your opinion.
Thank you very much.
Best regards,
Lucian Rada

 
#5
People who like this:1Yes/0No
Administrator
Rating: 4
Joined: Dec 4, 2017
Company:

Hi Lucian,

Thank you for the extra information you provided.

We are investigating the issue you posted and will keep you informed on the results.

Best regards,
Vladimir Gurov

1C Company support team
 
#6
People who like this:0Yes/0No
Interested
Rating: 30
Joined: Oct 27, 2011
Company: Abaco Soluciones S.A.

Lucian, your suggestion of RefreshObjectsNumbering(Metadata.Documents.Workorders) works 90% of the time. Also sometimes Verify and repair helps. In client-server mode restarting server helps.

I have a suggestion to 1c developers hat after Verify and repair if the restored objects have F000...01 names, do not follow those, rather continue with "normal" numbering.

 
#7
People who like this:1Yes/0No
Administrator
Rating: 4
Joined: Dec 4, 2017
Company:

Hi Lucian,

We need your answers to further questions:

- Which configuration do you use? If it is your custom configuration, can we get it in order to reproduce the issue? DT format is preferable.

- What happens when the user clicks the OK button in the error message box? Does the application go on running or fail?

- Do you use a single- or multi-user configuration?

- What client-side OS do you use?

- What database type do you use: file or client-server? What server-side OS do you use? If it's a client-server database, what DBMS do you use?

Best regards,
Vladimir Gurov

1C Company support team
 
Subscribe