[albertpro]

Hi,

I need help. I Upgrade 4.7.4 - 4.8.1 and I am having a problem, with the export result.

 

I just want to know if anyone has this problem.

 

I am using a certain export for updating inventory like always for years by using these fields

 

• product id 
• Language
• Product code
• Quantity
• Availbility
• Status
• List Price
• Price

After update I did export file in csv format like always, (and also tried in different format too the same problem)

 

it was an interesting result. there is a line break after certain line. I tried in my other website with cscart and I see the same result.

 

Is there anything we can do to resolve, this is very important and we need the data update.

 

I attached the excel files and I highliged Yellow the break lines.

 

Thank you

Albert

Attached Files

•  products_Inventory Update_06252018 (7).csv   25.56KB   22 downloads

[tbirnseth]

Any formatting probably won't stick.  Maybe reference the product code in your data.

It looks like you have a non-escaped double-quote in the "Language" column for Product Doce 34 H0030.

Most likely this is an error in the Product code "34 H0030

[JohnCarroll]

Hi,

I need help. I Upgrade 4.7.4 - 4.8.1 and I am having a problem, with the export result.

 

I just want to know if anyone has this problem.

 

I am using a certain export for updating inventory like always for years by using these fields

 

• product id 
• Language
• Product code
• Quantity
• Availbility
• Status
• List Price
• Price

After update I did export file in csv format like always, (and also tried in different format too the same problem)

 

it was an interesting result. there is a line break after certain line. I tried in my other website with cscart and I see the same result.

 

Is there anything we can do to resolve, this is very important and we need the data update.

 

I attached the excel files and I highliged Yellow the break lines.

 

Thank you

Albert

 

 

App/controllers/backend/exim.php

 

this may be problem: fn_define('DB_LIMIT_SELECT_ROW', 30);

 

change the value 30 to a lot higher number, clear cache and try again.

[albertpro]

App/controllers/backend/exim.php

 

this may be problem: fn_define('DB_LIMIT_SELECT_ROW', 30);

 

change the value 30 to a lot higher number, clear cache and try again.

 

Hi John,

Thank you so much, for the help I changed the 30 to 3000000 and it worked. 

 

I am sure that was something that changed during the update.

[The Tool]

I haven't experienced the issue but fn_define('DB_LIMIT_SELECT_ROW', 30) has been in the code forever.  Why is it now causing an issue?

[tbirnseth]

Could be that the number of products has tipped the scale on how many can be processed within the Webservice timeout and increasing the number of rows processed on each request can lower that somewhat at the cost of some memory.  I personally think that going from 30 to 3 million rows is a bit much, but again, you're then just reading a bunch of data into memory and moving it between processes.  The exim stuff generally keeps everything in memory anyway.  However, this number dies influence (I think) when the data is sync'd to disk.