Very solid question. In most instances, if I have a data type of Container, I would never have fields of container_name or container_id, I’d simply use name or id since it is redundant to always put container at the beginning of each field name.
However, in this implementation of my data, I am running a system to track all activities that take place across the entire life cycle of an international freight forwarder, and in doing this I am using the API to bulk create the Activity data type and need to differentiate between the different activity types that come through the webhooks, some of which are container events others are shipment events etc. so I need the container_id and container_name to differentiate between a shipment_id or shipment_name since the webhook json with nested arrays is getting flattened and having prefixed keys so that I can run my bulk update API call with that flattened and prefixed JSON.
But, nonetheless, there are other times at which my field names do not fit into the fixed width provided as well.
1 Like