Hi all,
hope you’re doing great!
I’m currently working with this connector, but I have a question related to the data. I have two entities coming from the API provider and locations linked to the provider. My question is, is there a way to create a new Location entities coming from this connector linked to the new provider?
Because I created a new Field called Linked Locations with a entity relationship to Location, but it did not work - so, my unique solution for this is creating text lists, but idk if that’s the best solution. Here’s an example of the data coming from the API:
Hi Joseph!
You should definitely be able to use the entity relationship field. Are the new locations coming through in the same data source?
You might want to use a separate connector to create those locations, and then use the new Trigger type “Linked Connectors” to trigger a run of the provider Connector. That connector should then be able to populate with the Linked Location Ids since we can ensure they have already been created.
If we misunderstood your question or any nuances, please let us know!
Best,
Rachel
Thanks @Rachel_Adler for your response! But I don’t know if I clearly understand what I have to do.
I’ll give you my understanding of this Connector already provided by Yext. For example, I can use the Location entity in the connector to try to get the data coming, but the thing is, the location data is coming in arrays - so, I can’t map that info into a single entity of type Location.
Does that make sense? Sorry about all the questions, I’m new working with Connectors.
No worries!
So is the question now, how to split data in a single row into multiple rows?
We do have a Split into Rows transform, but it only splits on a delimiter of a single column, which makes this a little more difficult.
What you’ll want to do is add a selector for all location data, locations.
You can then use the “split into rows” transform with this delimiter "}","{ in order to get one row per location.
Then, use the “Split Columns Transform” with the delimiter ,"" to make all the columns that your currently have for each location data point (e.g. city, line1, latitude, etc…).
Finally, you’ll need to perform some data cleaning with 2 separate “Find and Replace” transforms, to replace the JSON syntax of } and " with empty strings.
Hope this helps and let us know if you need further assisstance!
Best,
Rachel
1 Like
Hi @Rachel_Adler,
Thank you so much! That solution worked perfectly!
I have another question, maybe you know this more than me. How can I troubleshoot these kinds of errors? Because the entire data is not shown in the raw response of the connector.
2829398,en,Address > Line 1,ERROR,Value may not be a P.O. box
2829048,en,Fax Number,ERROR,Value must be a valid phone number
Thanks! Really appreciate your help!
That’s great to hear!!
To troubleshoot, if you turn on the Early Access Feature for Run Results that should help 
You can click on “View Details” for each run to view a page that lists all the errors, including the attempted value, so you can more clearly see what caused the issue and attempt to resolve
1 Like
Thanks for that Feature @Rachel_Adler! It made this work more easy!
Maybe you got this error in the past, do you know what can I do?
Hmm I believe that an actual Street Address is required for Address > Line 1, rather than a PO Box, which it appears you’ve provided.
Do you have a Street Address Available?
Not really, because the data is coming from the Kyruus API.
Hi @Rachel_Adler, just one last question! Do you know if there is anything I can do to fix this?
Hi Joseph,
Unfortunately, the reason you’re seeing this error is because the photo is too large. To fix this, we would recommend identifying a way you can resize the photo either through the URL itself, or by connecting with the source system to see if they can be resized there.
Best,
Ben
1 Like
