+- CoreBOSBB (https://discussions.corebos.org)
+-- Forum: Support (https://discussions.corebos.org/forumdisplay.php?fid=17)
+--- Forum: Administrator Support (https://discussions.corebos.org/forumdisplay.php?fid=8)
+--- Thread: [ solved ] Export uses not created a right file (/showthread.php?tid=1086)
[ solved ] Export uses not created a right file - rslemer - 05-13-2018
When you try export users, system not created a right file
See in on line demo.
User admin not listed and another user is list twice ...
RE: Export uses not created a right file - joebordes - 05-13-2018
I don't see the duplicated user. admin is missing but that is probably by design
RE: Export uses not created a right file - rslemer - 05-13-2018
testdmy is listed twice ...
RE: Export uses not created a right file - joebordes - 05-13-2018
please check the file you uploaded I do not see any user twice
RE: Export uses not created a right file - rslemer - 05-13-2018
Linha 1
testdmy off noreply@tsolucio.com Active cbTest testdmy H3 1 123456789 . 0 $1.0 2 dd-mm-yyyy Test user for coreBOSTests 0 UTC softed en_us 0 None 0.00 0 Today This Week 24
testmdy off noreply@tsolucio.com Active cbTest testmdy H3 1 123456789 0 . 1.0$ 3 mm-dd-yyyy Test user for coreBOSTests 0 UTC softed en_us 0 None 0.00 0 Today This Week 24
RE: Export uses not created a right file - rslemer - 05-13-2018
If you export user, use don't see in line 1 admin user
Line 2 and line 3 listed same user
RE: Export uses not created a right file - omarllorens - 05-14-2018
Check it again please, they are not the same user.
Line 2 is testdmy and line 3 is testmdy. Check the last 3 characters, are not in the same order. D - M - Y and M - D - Y.
RE: Export uses not created a right file - rslemer - 05-14-2018
Oh sorry, you are right!
My mistake because user 1 ( admin ) not did is listed and file has same 10 users ..
But, is because line 1 is a header ..
In my system not working, system not created any data in file
I try understand why .....
RE: Export uses not created a right file - rslemer - 01-20-2020
solved in last update