Children fields with same keys as other root field is showing incorrect in UI about zapier-platform-cli HOT 5 CLOSED

Yep! All keys need to be unique. So instead of 2 name fields, try shipping_name and billing_name.

from zapier-platform-cli.

Yep! All keys need to be unique. So instead of 2 name fields, try shipping_name and billing_name.

So if I use keys like shipping_name, billing_name then does it will auto break to object like
shipping :{ name:"myname"}, billing:{"name":"bname"} ?

from zapier-platform-cli.

Nope. Regardless of how you set up input fields, the result will be a flat object: {shipping_name: 'a', billing_name: 'b'}

from zapier-platform-cli.

object

Thanks for the reply, I read somewhere in the article If we create fields like this
{ key: 'billingAddress__name', label: 'Billing Address Name', /*other properties*/ }, { key: 'billingAddress__line1', label: 'Billing Address Line 1', /*other properties*/ },

Then Zapier will break them as below before sending to api
{ "billingAddress" : { "name": "whatever value" } }

Is this correct?

I tried this but not working same, it sending a flat object instead of inherit object

from zapier-platform-cli.

I believe those are old docs (which we are aware of, but haven't been able to clear yet) and aren't relevant here. CLI always gets a flat object. You could filter your object for keys starting with billing and grab that subset of properties that way.

from zapier-platform-cli.