EasyPopulate 4.0 Support Thread

[propster]

Hi, I am using this EP4 mod ok but would like to add an extra column in the detailed stock by attributes data csv file down load.This would allow me to easily cross reference the output to a stock quantity file supplied by a manufacturer using their stock codes which are slightly different to the model numbers I use on my site. I would like a new column showing the manufacturers product code. This would be tied to the stock i.d. for each product attribute. I am currently manually creating the table by adding the manufacturers code but this is a long process and I would like to automate this if possible.

[mc12345678]

Hi, I am using this EP4 mod ok but would like to add an extra column in the detailed stock by attributes data csv file down load.This would allow me to easily cross reference the output to a stock quantity file supplied by a manufacturer using their stock codes which are slightly different to the model numbers I use on my site. I would like a new column showing the manufacturers product code. This would be tied to the stock i.d. for each product attribute. I am currently manually creating the table by adding the manufacturers code but this is a long process and I would like to automate this if possible.

Sort of have lots of questions related to this query; however,am I correct in assuming that if the currently preffered SBA (that has an additional field) was being used then the issue would be resolved?

That would allow storing the identifier that is described so that updates would be easier, but it would not resolve new items per se as the data would not be present to export until it was imported at least once. That also assumes that the additional field added by that version of SBA isn't used for other purposes of SBA. (Haven't identified how that field is used yet, just know that it exists.)

Otherwise the question would be how would one create the data of that field on export and what if anything is stored back into the database associated with that field.

Otherwise some custom programming to do all that would be needed. But first clarification would help from start to "finish".

[propster]

Sort of have lots of questions related to this query; however,am I correct in assuming that if the currently preffered SBA (that has an additional field) was being used then the issue would be resolved?

That would allow storing the identifier that is described so that updates would be easier, but it would not resolve new items per se as the data would not be present to export until it was imported at least once. That also assumes that the additional field added by that version of SBA isn't used for other purposes of SBA. (Haven't identified how that field is used yet, just know that it exists.)

Otherwise the question would be how would one create the data of that field on export and what if anything is stored back into the database associated with that field.

Otherwise some custom programming to do all that would be needed. But first clarification would help from start to "finish".

Yes the addition of an extra field would be a great help. I am trying to update quantities from a supplied csv file, but the fields in the supplied file do not match the Detailed Stock By Attribute Data file exported by EP4. At the moment I am using a separate look up file to cross reference the required info then reimporting the generated output file. To do this I have to manually add a column to the Detailed Stock by attribute data file that I download to give the manufacturers stock code. This is used in the look up table to find the stock quantities. Once the stock quantity is updated in the look up table I remove the added column and upload the file to update stock quantities in my store.
I realise I would have to input the information for all existing products but for any new products it would just be added at the same time as all the new product information.