Regel 4
> ERROR: 22P02: invalid input syntax for type integer: “Pro Vitales”\nLINE 1: …ull, null, null, ‘2026-02-09 12:53:07’, ‘1’, ‘1’, 'Pro Vital…\n ^\nLOCATION: pg_strtoint32_safe, numutils.c:615
which version @martindoornbos
If you export existing users and compares the fields in the export and import - do they match?
yes, the same fields
@martindoornbos which version of dolibarr, and can you share a line from the file you import?
iI use
22.0.4
I also try 22.3
2
martin.doornbos
Doornbos
martin
1
Directeur
man
Tielman Oemstraat 1
3117 cd
Schiedam
0107070008
0636015053
mdoornbos@provitales.nl
1
dolcrypt:AES-256-CTR:10fbb3f05469219f:uL+F7wnS/DvMtwEk
1957-07-06
2026-01-07 16:09:57
2026-01-08 14:23:37.991232
1
1
Backoffice
Bericht
the file with 1 rule
oude crm 2-6 export_user_forum.zip (6.7 KB)
I haven change the database, new, same problem
* Regel 3
> ERROR: 22P02: invalid input syntax for type integer: “Pro Vitales”\nLINE 1: …ull, null, null, ‘2026-02-09 12:53:07’, ‘1’, ‘1’, 'Pro Vital…\n ^\nLOCATION: pg_strtoint32_safe, numutils.c:615
I checked the import definition in htdocs/core/modules/modUser.class.php.
For user import, u.fk_soc is labelled as Company*, and the example says: 0 (internal user) or company name (external user). But u.fk_soc is an integer field, and I do not see any conversion rule for u.fk_soc in import_convertvalue_array.
So with PostgreSQL, importing Pro Vitales into u.fk_soc fails because PostgreSQL expects the company rowid, not the company name.
Can you try replacing Pro Vitales by the rowid of that third party in llx_societe, or use 0 for an internal user? This looks like a bug/inconsistency in the user import template or conversion rules.




