Announcement

Collapse
No announcement yet.

Bug:- Hierarchical Import / Replace fails with Custom Property in 6.1.2.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Bug:- Hierarchical Import / Replace fails with Custom Property in 6.1.2.

    Hierarchical Import / Replace fails with Custom Property in 6.1.2.

    Scenario. Using standard demo catalog create a customvar TEST of type text.

    In the Calculator product add Custom Property TEST, give it text "HELLO"
    and set "Use as CUSTOMVAR" (leave other options unselected).

    Export the catalog to a textfile.

    Re-import choosing "Update" - all should be OK.

    Re-import choosing "Replace" and the following error occurs:-

    Line 32: The imported custom property does not refer to a predefined valid custom property.

    Where line 32 contained the perfectly valid

    CustomProperty,TEST,"HELLO",1,0,0,0

    Norman
    Norman - www.drillpine.biz
    Edinburgh, U K / Bitez, Turkey

    #2
    Hi Norman

    This is a known problem and is being addressed in the next release of Actinic Ecommerce. You should find that despite the error, the custom properties still import.

    Comment


      #3
      You should find that despite the error, the custom properties still import
      Afraid not.

      Top level CUSTOMVARS fail to be updated whenever this error occurs using Import / Replace. I'm not sure about product level CUSTOMVARS but I suspect they're not updating either.

      Wierdly, they do import ok and without errors, if I run the import a second time.

      Norman
      Norman - www.drillpine.biz
      Edinburgh, U K / Bitez, Turkey

      Comment


        #4
        OK Norman - I'll feed this back to the team.

        Comment


          #5
          I use 6.1.3 and have still had difficulty with this.

          I got around it by ensuring that 'ValidCustomProperty' was specified in the import file. I had thought that because I'd already set up the valid custom properties using the Actinic GUI, I didn't have to re-import them every time, but you do.

          Heirarchical import csv needs to look something like this:


          Header:ValidCustomProperty,Name,Type
          Header:CustomProperty,Custom Property Name,Value,Use as CUSTOMVAR,Is Searchable,Is File Name,Use File Content

          ValidCustomProperty,"ThingOne",1
          ValidCustomProperty,"ThingTwo",1

          Product,"MyProduct1", ...
          CustomProperty,ThingOne,"Value One",1,1,0,0
          CustomProperty,ThingTwo,"Value Two",1,1,0,0


          Hope this helps someone
          Andrew

          Comment

          Working...
          X