This message was deleted.
# secoda-support
w
This message was deleted.
e
Hey @quick-house-6813 would you be able to share a screenshot of what these two items look like in Fivetran. It would help give me an idea of how to modify the integration to allow you to distinguish what is a destination
q
Sure. Fivetran allows setting different ‘destinations’ aka landing databases for the ‘same’ connector. It does not mean the same conector writes in two places but there are two ‘instances’ of this connector created down each ‘destination’. so destination should be a key metadata to attach to the jobs. Here a screenshot of my sandbox with some notes
For sure it is not critical at all, at least for me
e
Ok, thanks for the context Daniel. I'll create a ticket to update the Fivetran integration to reflect this behaviour
q
No hurry at all, keep your roadmap safe!
1
FYI I noted that
requiredGroup
parameter in the job URL in fact identifies the destination but in Fivetran fashion, using some odd, random combination of two words as id to avoid duplications.
<https://fivetran.com/dashboard/connectors/><a given connector>/status?requiredGroup=<some odd two words combination>
Objective would be to get the mapping between this
requiredGroup
parameter and the true, user-friendly ‘destination name’
👍 1