One-to-Many Import Post Response Map Script Preview Data

Integrator.io
, , ,
1

Hey Everyone,

Need confirmation on something.

In creating a Post Response Map Hook script on a One-To-Many import I don't think the preview data in the script editor is correct. The data in the script editor is in the context of the path to many array records. However, based on my testing, at run time the context is really the original record among the page of records.

I tried to add a new field to the _PARENT in my script which worked fine in the editor preview but did nothing when running the flow.

Can someone confirm?

Thanks,

2

@davidgollom it looks like postResponseMap is still within the path of one-to-many, but it looks like runtime isn't giving the _PARENT object. I just console logged this to test and am looking internally why _PARENT isn't there at runtime.

5301043caa20740200000001-92d06ce736514d21925ee749fb7b677b.png
5301043caa20740200000001-92d06ce736514d21925ee749fb7b677b.png2402×1253 235 KB

5301043caa20740200000001-2922ea09ebcd43f0932c0f35a69f42ba.png
5301043caa20740200000001-2922ea09ebcd43f0932c0f35a69f42ba.png2540×1253 277 KB

3

Hey Tyler,

This makes sense. There's no parent object and you have to access the target array with main record. Let me know what you find out.

Thanks!!

4

@davidgollom sorry for the delay here, I met with engineering this morning and they're checking on expected behavior. Depending on that, we'll log an issue for it.

5

Hi @tylerlamparter I'm not sure if it's related to what @davidgollom259 reported, but I just struggled with a strange post response map script preview on a One-to-Many lookup. I'm adding this note to this topic because I suspect it's related.

My situation is pretty standard: Exporting order data, for each line on the order I lookup additional product attributes. The API payloads are messy and I need to filter the lookup results to grab only an array element I actually care about. I was planning to use a Post Response Map script for this, but the Input and Preview data is whacky!

My path to One-To-Many is 'lines' and I output mapped my lookup results to product_ex_data. I would expect to see Input preview like:

{
  "postResponseMapData": [
    {
      "lines": [
        {
          "line_id": 14263214276915,
          "product_id": 8059359985971,
          "variant_id": 44195116941619,
          "product_ex_data": [
            {
              "variant_id": 44195116941619,
              "barcode": 843578102703
            },
            {
              "variant_id": 441951169416198,
              "barcode": 8435781027033
            }
          ]
        }
      ]
    }
  ],
  ...
}

where the lookup results are located in the "many" record. Instead the Input preview looks like this:

{
  "postResponseMapData": [
    {
      "lines": [
        {
          "line_id": 14263214276915,
          "product_id": 8059359985971,
          "variant_id": 44195116941619
        },
        {
          "line_id": 14263214309683,
          "product_id": 8059371782451,
          "variant_id": 44195138928947
        },
        {
          "line_id": 14263214342451,
          "product_id": 8059786690867,
          "variant_id": 44196141891891
        }
      ],
      "product_ex_data": [
        {
          "variant_id": 44195116941619,
          "barcode": 843578102703
        },
        {
          "variant_id": 441951169416198,
          "barcode": 8435781027033
        }
      ]
    }
  ],
 ...
}

It's incorrect. If I actually run the flow and force an error I can see that the lookup data IS mapped to the child record as expected, but in the script editor you'd never know it.

I've worked around this, but still happy to review with anyone if interested.

6

@steveklett - Thank you for reaching out ! We are aware of this issue and actively addressing it.

7

I'll tack myself on as someone experiencing the strange symptoms as documented by @steveklett. In my case, it feels like this specific issue manifested shortly after the latest feature rollout, though I have no way of confirming this as enhancement of this legacy script and subsequent debugging only began roughly around that time.

8

@andrewsanjanwala @steveklett this should be resolved shortly. During runtime, everything is running as expected, but the UI preview is being incorrectly displayed. Since the UI preview is incorrect, it could lead you to building your script wrong. In the meantime, you can add console.log(JSON.stringify(options)) to the top of your script, enable debug on the script, then review what was logged. The logged JSON will be what you should use when building the script.