Hi Sunil,
So the reason this is occurring is because of how the data is coming through liveAPI. In location entities, each address section has its own field:
whereas in the Jobs entity, it’s coming through as one string so the formatter doesn’t know how you want to parse the data.
Is there a consistent way you would want to break up this above location string (e.g., comma separated)?
Are all of the job entities tied to a location entity? I ask because another idea would be to leverage streams to multi-hop and bring in the address field from the location entity.
Alyssa