I have made static form custid when add new user. i make static because i need unique custid when add user and it must unique as custid so i add rule no duplicate custid. it can not add in contact information form because it's dynamic form and code save to ost_user_cdata table. so it make problem when try to find custid. so i add new colomn custid in table ost_user. all configuration work fine now, but when i try to import csv file in user tab -->import, it say nothing to import while csv format are correct.
genx88
Uhhh, yea because you modified a core table. Data updates via import are handled via the Contact Information Form.
Cheers.
I can not use contact information form as custid because it save in different table ost_user_cdata not in ost_user and i need unique id for my system. i hope next version 2.0 have custid, name. phone, email, address as a default contact form field.
I guess I don't understand your use-case. Every User (and Agent) in osTicket has a unique ID (integer). In addition, any custom field added to the Contact Information Form will be available when viewing the User and can be pulled in things email templates and ticket filters. Yes, it's added to user__cdata but that's simply the indexed data used for searching purposes. The real values are stored in the user and form_field_values table.
user
form_field_values
KevinTheJedi I know every user and agent have unique id automatically by system like user1=1, user2=2 etc not custom id that can be set to 123456 digit manually. in my plan. my customer have custID with 6 digit like 123321, 123331 etc. this custid must be add by agent when create new user with role no duplicate custID allowed. so for next when agent create a new ticket. just need enter custID only because custID is unique no duplicate like name. 123321 = jhon 123421 = Peter 123433 = Emily
I mean you can always add a custom field to the Contact Information Form for this but unfortunately you cannot set a uniqueness flag on the field so that ALL values (regardless of User) are unique. So the only way to accomplish what you are looking for is to modify the codebase.
