BigCommerce possible UI bug

Integrator.io
1

There appears to be a bug in the BigCommerce import step.

I set a request body in the REST API configuration, for example:

The image shows a form for importing records using a REST API, with fields for HTTP method, relative URI, HTTP headers, and request body. (Captioned by AI)
The image shows a form for importing records using a REST API, with fields for HTTP method, relative URI, HTTP headers, and request body. (Captioned by AI)1578×1250 50.5 KB

In the requestbody I filled it in { "test" : "test" }.
After saving the step, the request body disappears from the UI. It looks like it's not saved:

A bright pink arrow pointing towards a menu item labeled "Mapping" with a description underneath. (Captioned by AI)
A bright pink arrow pointing towards a menu item labeled "Mapping" with a description underneath. (Captioned by AI)830×200 16.3 KB

However, when I add a UI mapping to the same step and run the flow, the request body I originally entered still gets sent (the test json):

The image shows an error message indicating a 422 status code from BigCommerce, stating that the request payload must be a JSON array for the endpoint. (Captioned by AI)
The image shows an error message indicating a 422 status code from BigCommerce, stating that the request payload must be a JSON array for the endpoint. (Captioned by AI)1586×352 38.2 KB

This shows that the request body is still there in the background, but it’s not visible or editable in the UI after saving. That makes it hard to know what’s actually being sent, and hard to update or debug.

2

@nuriensing - I am unable to reproduce this behavior. Can you please provide any additional steps that you have performed? There is a known bug where setting the form view to REST API and reopening the step defaults the form view to BigCommerce, which we are fixing and plan to release a fix for on 06/05.

3

I don’t recall any additional steps beyond what I already mentioned.
I simply open it, modify the request body, save it, and then it disappears from the UI.

1 Like
4

@nuriensing - Can you please share the backend json of the BigCommerce import ?

5

Hi Sree,

Is it ok if I DM you this one?

6

Sure @nuriensing . You can email me at sreevani.amara@celigo.com.

7

Thanks! Will send it now.

8

@sreevaniamara has fixed the bug.
@sreevaniamara If you could add some context or details here, I’ll mark your comment as the accepted solution.

9

We have released a patch to fix the BigCommerce steps defaulting to the BigCommerce view, even when the form view is set to REST and saved.