Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
Hello,
When I try to import a large file of 4000 lines in the journal entries, the system is stuck at loading until it displays the message 'please press the F5 key to refresh' and nothing happen after that. I can't figure out where is the problem !
Any help would be appreciated, thank you.
Hello,
You should change the time out limit on the server configuration which is defined by default at 300 seconds.
To import large files, you can shoot it at something like 5000 seconds in order to let the file finish to import.
I know it has already solved some problem of import for us...
Hope it is going to work for you !
Pierre
I had this problem when I was importing 300,000 records. You've two options:
1. First option, and better one in your case: Divide the 4000 in smaller chunks and import.
2. Use a Tool like "Navicat for Postgres" or "pgAdmin3" to import data using Postgresql. You don't have to write SQL yourself, rather these tools provide you all the fields and you can carry on without writing any SQL.
Hope it helps.
Thanks,
Abdul
Hi.
Importing directly to DB is not the best solution. For example when you import products data is stored to different tables (product.product and product.template).
Thank you for your replies, please where I can change the time out limit in Odoo ?
the time limit setting can be done in your odoo .conf file
source: https://www.odoo.com/documentation/14.0/developer/misc/other/cmdline.html
You can change the timeout in configuration file as well as through the commandline param --limit-time-real=1000
Cree una cuenta para poder utilizar funciones exclusivas e interactuar con la comunidad.
Inscribirse
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
@Mos, You may want to check out this post: https://www.odoo.com/forum/help-1/question/csv-product-import-issues-import-preview-failed-due-to-field-larger-than-field-limit-131072-57081 It's more of a hack than a permanent solution, however it may function as a workaround until you find a proper solution. I have not tested this in production so i'd recommend a full filesystem and database backup before trying it.