29,131
edits
Changes
m
→Table and fields structures
Line 99:
Line 99:
- date_creation datetime that is the creation date
− - date_modification datetime that is the last modification date
When you create a new table, it is recommended to use the same conventions as other Dolibarr tables. This means the following fields:
When you create a new table, it is recommended to use the same conventions as other Dolibarr tables. This means the following fields:
- rowid integer for id
- rowid integer for id
− - tms timestamp that will contain date of last modification (the database manages this field automatically, no need to manage it by the code, just create the field)
+ - entity integer default 1 that is id for the multicompany feature
+ - date_creation datetime that is the creation date
+ - tms timestamp that will contain date of last modification (the database manages this field automatically, no need to manage it by the code, just create the field)
- import_key that will contains the import code YYYYMMDDHHMMSS if you make mass import.
- import_key that will contains the import code YYYYMMDDHHMMSS if you make mass import.
Eventually
Eventually
− - fk_user_author integer that is the id of user making creation
- fk_user_author integer that is the id of user making creation
- fk_user_mod integer that is the id of user making change
- fk_user_mod integer that is the id of user making change
+ - fk_user_valid integer that is the id of user validating record
- fk_soc integer that is the ID of the Third party (if applicable)
- fk_soc integer that is the ID of the Third party (if applicable)