Forum

The forum is a free service supported by community members. Please consider opening a support ticket if you need timely help.

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Jul 2018 06:32 PM by  Steve L
product attribute import problem
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages


Basic Member


Posts:120
Basic Member


--
26 Jun 2018 04:40 PM

    When importing product attributes :

    We are using a selection value that corresponds to the ProductAttributeDefinitionSelectionID

    eg 6|

    When the import takes place the database always shows a NULL field and the selection value is not updated


    and before you ask - we are not specifying booleanValue, decimalValue, integerValue or stringValue - we are leaving these fileds blank.


    We have tried manually adding product attributes on the site, which works a treat. Then we have exported the productattributes. When we re-import them the same issue occurs where the selction value is NULL


    Do you have any ideas what may be the problem and how to solve it ?


    Thank-you

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    30 Jun 2018 01:36 PM

    Hi Steve

    What Storefront version are you running? In your map file, do you specify the SelectionValue and if so does it match up with your column name? In the Act column, do you specify "u" for update operation?

    0


    Basic Member


    Posts:120
    Basic Member


    --
    03 Jul 2018 10:19 AM

    Hi Stephen

    It is : v13.0.0.0 PROFESSIONAL

    The map file is correct in the columns except with CreateDate and UpdateDate as additional columns, compared with the map file shown in the import routine.


    We use a selection value of EG 6| (6| being one ofthe ProductAttributeDefinitionSelection IDs')


    We can manually update the database in SQL with 6| and this shows up nicely in the storefront product attribute in shopadmin


    But the import then changes this to a NULL value in SQL ?

    We are using U for the Act column


    Any further ideas please ?


    Thank-you

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    11 Jul 2018 06:32 PM

    Hi Steve

    We were able to reproduce the bug and have corrected it for the next upcoming release v13.4 (in a few weeks). Meanwhile, you can try to delete the other columns from your CSV file (StringValue, BooleanValue, IntegerValue, DecimalValue) if you only need to bulk update SelectionValue. You can do the same for the other column (delete other non-participating Value column). This should prevent it from nullifying the wrong column on import.

    0
    You are not authorized to post a reply.