Increment auto numbering

Hello.
I'm very new to CB.
I need to create a field with incremental auto numbering, like an id.
Is there a way to do it with CB?

i.e. - Joomla has its own id for each user, but i need to create a unique id for some selected users...

Please Help.

Best Regards.

Users already have a unique ID. Add [user_id] to a delimiter field to display it. Alternative is to create an integer field then use CB Auto Actions with a Query action at whatever trigger you want it to be incremented at (registration I suppose?) that queries _comprofiler for that column and increments it (order by that column and limit to 1) then stores it to the user.

Dear krileon.
Yes, Joomla already sets an auto increment id. Before saying what i do really need, let me say i'm using J!2.5 and CB 1.9.
But what i was looking for is a solution for this, maybe a little bit complicated:

- 2 Groups created. Group 1 and Group 2
- 4 Users created. User 1, User 2, User 3 and User 4.
- Make users 1 and 2 members of Group 1
- Make users 2 and 3 members of Group 2

User 1 should have an ID (not J! id) like 1001 ( Group 1)
User 2 should have an ID (not J! id) like 1002 ( Group 1)

User 3 should have an ID (not J! id) like 2001 ( Group 2)
User 4 should have an ID (not J! id) like 2001 ( Group 2)

Users cannot self register and all the registrations are made on the back-end, but i need to have a auto suggested ID (not J! id) for each user in each group.

Do you think this is possible?

Thanks in advance.

That's possible, but you're going to have to write the database queries to handle all of that. Probably better to be done in a new CB plugin using triggers to do all the complex calculations needed. There's no easy way to do it.

Huummm...
Well, so, what if i simplify a bit...

Can i create a field related with a group, where i set an initial value [1001] and then set manually when the user is created.

The only thing is it should suggest the next available number and not allow use already used numbers.

Is this easier?

You can create a read only field and manually set it, sure, but it's not going to check that the number is already used (you can try using DB Lookup for that). It still won't suggest the next number though. You need a custom solution for what you're wanting.