Need to set up a numbering system to track your records? Define and add a unique ID identifier field to any SugarCRM record. Many options to define any alphanumeric format you need. Start tracking your Quote, Cases, Accounts and any other module today..
#2899 - Sequences
I've been using the Sequences add on for a couple of years and have discovered that it occasionally duplicates a sequence -- always the same number. I went into admin and it shows that I have no sequences defined, but I know that there are 2 that are running. What do I do?
-
"Would need this for Sugar7. Is this planned?" - filcher1448
Read More Reviews
- Most Recent Love from Users
taufiqueahmed- jkoop
- jkoop
- matoulas
- CM & Sugar
7 years ago
Sounds like there is permission issues going on. If a sequence is deleted, it is not triggered any more at your modules. Maybe it is linked to another user? You can check it by reading the table "sequences" If you dont want to use it, you can update the "deleted" flag to "1".
6 years ago
I confirmed that the table has 2 active sequences. The sequence is defined as: Code Prefix » First Number » Date Format » Code Suffix Code Prefix: LD First Number: 1 Date Format: blank Code Suffix: blank
The next number in the sequence is: LD23309. However, if I look into the table that uses the sequence, I see multiple instances of LD004324. How does this happen?
6 years ago
Well there were definitely two sequences defined. I guess that is the reason for your current issue. They have different length and different zero padding. Therefore it will always create one number and use it. To fix it, you must correct either the old wrong values from your table by hand, or you remove them and use autofill. Otherwise you can send me your table and sequence definition and I can try to repair by some sql commands, but that service would be paid in advance.
6 years ago
Thanks for getting back to me. Yes, there are two sequences but they are acting on different tables (leads, opportunities). I might have misunderstood the documentation, but that sholdn't be a problem -- should it?
6 years ago
not at all. You can have as many sequences as you want acting on different modules. There you are right, However, you sent me two different sequences and thats the actual problem. Somehow there must have been a previous one, which is interfering to the current one. The next value check uses always the same procedure within the column of a table. But if the setup changes and there are already older values given, you can face such problems. To solve it, you must repair the data by your own and reset the values. In any case, you should backup your table(s) before!
6 years ago
OK - so I finally got back to doing something about this. I've created a new sequence and assigned it to a new alpha-numeric field. I did the initial fill and everything looked good. Now it is stuck again. It has a prefix of LD, zero pad of 6, begins with 1. It sequenced everything up to LD126617 and then got stuck using LD098298 for everything after that.
6 years ago
Do you got any email address? I would like to send you version 1.4.1. Maybe that issue has been already fixed.
6 years ago
richard.weir@lile.com