search

amanwas / magento-w2p

Automatically exported from code.google.com/p/magento-w2p
0 stars 0 forks source link

Import / export #422

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Fixed qty data should be included into import/export.
A user with large inventory base won't be able to use this extension without 
off0line editing.

Original issue reported on code.google.com by zetapri...@gmail.com on 9 Jan 2011 at 10:34

GoogleCodeExporter commented 9 years ago

Original comment by zetapri...@gmail.com on 13 Jan 2011 at 4:51

GoogleCodeExporter commented 9 years ago 
It is possible to import/export it but since fixed quantity prices (fqp) are 
complex data they should be serialized in some manner - "100 business 
cards|100|10.00". Probably we'll need to make documentation note about this.

Original comment by jamb...@gmail.com on 17 Jan 2011 at 12:46

GoogleCodeExporter commented 9 years ago 
OK. Let's do it.

Document in a draft post on magentohelp.

Original comment by zetapri...@gmail.com on 17 Jan 2011 at 10:48

GoogleCodeExporter commented 9 years ago 
Default import/export adapters are not suitable for our type of data.
I propose to have separate adapters specific for fixed qtys only.
So importing fixed quantities will have to be done after importing base product 
import.

Original comment by jamb...@gmail.com on 25 Jan 2011 at 6:15

GoogleCodeExporter commented 9 years ago 
Considerations about fixed quantities (FQ) import/export.

Each product can have multiple and variable number of FQ. Each
FQ consists of several fields - website, label, qty, price.
We need these imported/exported. One approach is to have multiple rows per
product, where each row represents one FQ and each field of FQ is separate
field in the table. This would require some extra processing, like loading all
records and grouping them per product, also this will increase file sizes by
having redundant repeating of product's SKU each row. Good part is that this is
probably easier for users to prepare. A row in csv file will look like:

"SKU",      "Units",          "Qty", "Price",    "is_default"   "enabled"
"some_sku", "A box of cards", "100", "5.00",     "1"            "1"

Where 'some_sku' will repeat for each FQ.

Another option would be to group FQ for each product in a sort of serialized
string. Then for each FQ fileds will be separated by pipe |, and each FQ will
be enclosed in {} - characters were chosen as delimeters because it is less
likely to be used in 'Units' label as part of the text. So with this option a
row would be:

"SKU", "fq", "enabled"
"some_sku", "{A box of cardxs|100|5.00|1},{3 boxes of cards|300|12.00|0},{10 
boxes of cards|1000|30.0|0}", "1"

With this variant each row in csv file represents a product.
Pros: smaller file size, process records per product - no need to parse entire
record set to have all FQ per product, format could be incorporated into
product adapter (not good idea, but possible).
Cons: for non technical people it is harder to type in this way - especially if
creating csv in excel, still have to parse the string to usable data.

Before actually implementing import/export it would be good to have a decision
on format option.

Also during import if product already has FQ - what to do - overwrite, add to
existing, ignore import?

Original comment by jamb...@gmail.com on 31 Jan 2011 at 8:59

GoogleCodeExporter commented 9 years ago 
Is it going to be the same CSV file they import from Mage with all the other 
options?

If yes, I think we just add Price1, price2, price3 columns for as many as we 
need.

I'd prefer to see it as part of the same import/export.

Original comment by zetapri...@gmail.com on 31 Jan 2011 at 10:14

GoogleCodeExporter commented 9 years ago 
If we add this to common file, then we HAVE to override default product 
adapter, and entire huge method that does data parsing. This is generally fine, 
as long as no other extension does the same thing, if another extension 
overrides adapter as well there will be conflict.
Also we need a naming conventions on columns, and each column will have to hold 
a FQ entry in "A box of cardxs|100|5.00|1" form.

Original comment by jamb...@gmail.com on 31 Jan 2011 at 11:49

GoogleCodeExporter commented 9 years ago 
I take your point about potential conflicts. Maybe better to keep this 
import/export separate.

I think every value needs its own cell.
Name columns the same as in the admin, but add 1,2,3,n.
So no separators inside the cells.

Original comment by zetapri...@gmail.com on 31 Jan 2011 at 8:51

GoogleCodeExporter commented 9 years ago 
New functionality is added to magedev. There are 2 new advanced profiles 
installed:
http://ec2-174-129-95-130.compute-1.amazonaws.com/magedev/index.php/admin/system
_convert_profile/edit/id/10/ - for Export
and
http://ec2-174-129-95-130.compute-1.amazonaws.com/magedev/index.php/admin/system
_convert_profile/edit/id/9 - for Import

You can run export profile to get what ever fixed qtys are set at the moment, 
make changes, copy file to /var/import and run import profile to see your 
changes applied.
File names for both profiles should be 'fixed_qtys_data.csv' . The files can be 
edited in excel, but should remain as csv files.

Original comment by jamb...@gmail.com on 2 Feb 2011 at 1:21

GoogleCodeExporter commented 9 years ago 
Is this where the fie should be exported to?
/magedev/var/export

If it is, then the info is not in a separate cell. Values are in a single cell 
per row (fixed_qty_values.png).

Original comment by agur...@gmail.com on 7 Feb 2011 at 10:28

Attachments:

GoogleCodeExporter commented 9 years ago 
No they are not, this is csv file, you should explain to excel how to load it. 
Format is same as default magento one, text is delimited by " and separated by 
, (comma)

Original comment by jamb...@gmail.com on 7 Feb 2011 at 10:38

GoogleCodeExporter commented 9 years ago 
1. Although saving with no extension / format changes, I couldn't do it through 
Excel editing.
I was only able to make changes through these profiles using notepad.

2. How come I can't add new Fixed Qty options? Ex. The CSV file contains 3 sets 
of options for this product:
http://ec2-174-129-95-130.compute-1.amazonaws.com/magedev/index.php/test/t-shirt
-01.html
I added another set of values (csv_fixed_options.png) and uploaded/ran the 
profile. The fixed Qty option was not added in the frontend.

Original comment by agur...@gmail.com on 7 Feb 2011 at 12:17

Attachments:

GoogleCodeExporter commented 9 years ago 
Now I cannot help with excel - there are tutorials on the net how to open and 
work with csv files in Excel:
http://help.yahoo.com/l/us/yahoo/smallbusiness/store/shipping/shipping-57.html
http://wiki.answers.com/Q/How_do_you_open_CSV_file_in_MS_Excel

About 2 - you have to have corresponding headers in first row, like - qty3, 
label3 etc.
So adding more prices means adding more fields to the headings.
I know this sounds like slow and painful process but this is how Max said it 
should be - read the discussion for reference. And is for sure quicker than 
doing this in Magento admin.

Original comment by jamb...@gmail.com on 7 Feb 2011 at 12:34

GoogleCodeExporter commented 9 years ago 
Code about this is here: 
http://code.google.com/p/magento-w2p/source/detail?r=1354

Original comment by jamb...@gmail.com on 7 Feb 2011 at 4:52

GoogleCodeExporter commented 9 years ago 
Has this been properly tested?

Original comment by jamb...@gmail.com on 22 Feb 2011 at 7:34

GoogleCodeExporter commented 9 years ago 
Well, before it can be tested we probably need to properly document it.
A wiki page will do.

Original comment by zetapri...@gmail.com on 23 Feb 2011 at 12:14

GoogleCodeExporter commented 9 years ago 
It should be documented, but how is this related to testing?

Original comment by jamb...@gmail.com on 23 Feb 2011 at 7:55

GoogleCodeExporter commented 9 years ago 
Testing requires understanding of what it is and how it works. Please document 
first.

Original comment by zetapri...@gmail.com on 23 Feb 2011 at 8:17

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/magento-w2p/wiki/FixedQuantitiesImportExportProfiles

Wiki page created

Original comment by jamb...@gmail.com on 23 Feb 2011 at 9:24

GoogleCodeExporter commented 9 years ago 
Works ok on M 1.4.1 - magedev. Wasn't ale to get it going through actual MS 
Excel edits. Gave up after a few tries.
Did it using plain text editor (notepad). Was even able to assign Fixed Q 
options to a product that didn't have any assigned originally:
http://ec2-174-129-95-130.compute-1.amazonaws.com/magedev/index.php/default/test
/1800mm-x-1200mm-renowned-properties-sign.html

Flagging this "More Work" because I wasn't able to test it on M 1.5. Mageimage 
has something weird going on with Magento connect. Can't install the extension. 
Please set it up so that I can confirm it there as well.

Original comment by agur...@gmail.com on 23 Feb 2011 at 7:08

GoogleCodeExporter commented 9 years ago 
We need to figure out why it won't even set up.

Not being able to use Excel is a big worry.
This must be user friendly or it's not worth doing.
What editor can be used?
Are there any additional steps to use this file in Excel?

Please, get to the bottom of this.

Original comment by zetapri...@gmail.com on 24 Feb 2011 at 3:16

GoogleCodeExporter commented 9 years ago 
To install it on 1.5 you need version 2 of extension key. Also since it is in 
beta state you need to have beta extensions enabled in magento connect settings.
It is installed now.

I am sorry but I am convinced that it works after editing with excel, you need 
to save it back to csv format and set delimiters to be commas and enclosing to 
be double quotes. I repeat - csv format that we use is exactly the same as 
general Magento csv format no differences at all.

Original comment by jamb...@gmail.com on 24 Feb 2011 at 8:03

GoogleCodeExporter commented 9 years ago 
I have installed excel 2010 on VM to test and I have been able to import FQ for 
3 products (I have tried only 3 so that is 100% success) after I have edited 
the file in Excel. What I noticed is that excel was able to open the file 
straight away without need to import the data. Also when saving the file it 
stripped all double quotes, nevertheless the import went trough.

Original comment by jamb...@gmail.com on 24 Feb 2011 at 11:17

GoogleCodeExporter commented 9 years ago 
Tested on /mageimage/
Magento ver. 1.5.0.1
ZetaPrints_Fixedprices  0.3.0.1b (beta)

1. As far as functionality is concerned, it works. Was able to assign FQ to a 
new product and add columns with options.

2. As far as CSV edits in Excel are concerned, I wasn't able to get it going. 
As Petar said, " are not even necessary. Simple comas do the trick and the file 
goes through. 
It is relatively easy to open and view the exported .csv file as separate cell 
values in Excel. I can explain this in the help post so that users know how.
Problem is the output. Saving the file as comma delimited .csv file results in 
values separated by ; instead of ,
Don't know if this is the problem
http://office.microsoft.com/en-us/excel-help/import-or-export-text-files-HP01009
9725.aspx#BMchange_the_separator_in_all_.csv_text
But asking users to edit Win control panel settings and stuff is a bit over the 
edge. Did you guys had this set up before or something? Did you have this 
problem at all?

Original comment by agur...@gmail.com on 24 Feb 2011 at 5:42

GoogleCodeExporter commented 9 years ago 
As I said in previous comment, I installed latest version of Excel and all 
worked just fine. It is known issue that older versions of Excel do have 
problems with csv files.
That is why I would recommend updating Excel or using OpenOffice Calc to open 
csv files. 
Once more I repeat - if this is problem for an user with our csv files it will 
be problem for default Magento exports too when they are in csv format. 
Just try to get an export of all products and edit it in Excel, then try to 
import it.

As you noted there are solutions on Excel side, there are also solutions on 
Magento side - you can edit the profile xml and change delimiters. But these 
are common Magento problems and solutions not specific for our extension.

Original comment by jamb...@gmail.com on 24 Feb 2011 at 5:55

GoogleCodeExporter commented 9 years ago 
I tried it both with Excel 2007 and 2010

If we are to instruct users to use workarounds, I'll just explain that they can 
save the file and open in any plain text editor that supports "Find and replace 
all" option to change all ; to '
This is what I did at the end and it worked. But! Not favoring this solution 
for a help post at all.

Original comment by agur...@gmail.com on 24 Feb 2011 at 6:03

GoogleCodeExporter commented 9 years ago 
I don't know what to say - my attempt with Excel did not replace , with ; which 
makes me think that this could be environment and installation dependent.

Original comment by jamb...@gmail.com on 24 Feb 2011 at 6:08

GoogleCodeExporter commented 9 years ago 
I don't like the way it is heading. Not at all.
Can you post that file you downloaded from mage here before making any edits to 
it?

Original comment by zetapri...@gmail.com on 25 Feb 2011 at 2:15

GoogleCodeExporter commented 9 years ago

Original comment by agur...@gmail.com on 25 Feb 2011 at 8:01

Attachments:

GoogleCodeExporter commented 9 years ago 
Well before you make your opinion - search google for magento excel problems.

Original comment by jamb...@gmail.com on 25 Feb 2011 at 8:03

GoogleCodeExporter commented 9 years ago 
Way too  many imports went fine for this to be in more work satus

Original comment by jamb...@gmail.com on 4 Mar 2011 at 8:14

GoogleCodeExporter commented 9 years ago 
You're right. The issue here is to make it work and it does. Exports in a CSV 
file and imports ok as well.

I guess I'll have to struggle with the CSV editing (excel) issues while writing 
the help post.

Original comment by agur...@gmail.com on 4 Mar 2011 at 10:42

GoogleCodeExporter commented 9 years ago 
Docos:
http://code.google.com/p/magento-w2p/wiki/FixedQuantitiesImportExportProfiles

Original comment by jamb...@gmail.com on 4 Mar 2011 at 10:57

GoogleCodeExporter commented 9 years ago

Original comment by jamb...@gmail.com on 7 Mar 2011 at 12:58

GoogleCodeExporter commented 9 years ago 
I think this wiki is sufficient for the help post.

Original comment by agur...@gmail.com on 7 Mar 2011 at 3:55

GoogleCodeExporter commented 9 years ago

Original comment by zetapri...@gmail.com on 7 Mar 2011 at 9:15

GoogleCodeExporter commented 9 years ago 
Help post is published:
http://www.zetaprints.com/magentohelp/bulk-edit-fixed-quantities/

Should be sufficient for people that know what they are doing or have worked 
with csv files before. Unfortunately, we can't expect our customers to know 
this. Trying to make the csv file work only confirmed my previous conclusion. 
This is a tough format to work with :( I actually had to go inside Win/Control 
panel/Regional language settings to change the way Win marks lists (from ; 
delimiters to , delimiters).. and still another problem occurred that I'm not 
even gonna go into. This is too much to ask from people, sorry. My opinion.

The post is there and does not explain the actual CSV editing procedure. If 
we're going with this method, I must write a help post on how to do it and what 
problems to expect. If we can solve this problem from the root, by all means, 
lets do it.

Original comment by agur...@gmail.com on 6 Apr 2011 at 8:04

GoogleCodeExporter commented 9 years ago 
What about TSV ?
They are usually more reliable.

Original comment by ad...@zetaprints.com on 20 Apr 2011 at 7:05

GoogleCodeExporter commented 9 years ago 
Actually they are the same thing using tab as separator. And magento does not 
support out of the box.

Original comment by jamb...@gmail.com on 20 Apr 2011 at 1:23

GoogleCodeExporter commented 9 years ago 
Don't know. I don't have a problem with CSV files, but if Atanas has then 
others are likely to have them too. We'll see what happens.

Original comment by ad...@zetaprints.com on 21 Apr 2011 at 12:42