Exalate - not all (custom) fields are fetched from remote

Csaba Vertessy
Contributor
February 16, 2024

Hey there,

Has somebody using Exalate already experienced this?

I have created a new connection, was able to map almost all the fields but sometimes not all of them are fetched from remote.

If I switch to the remote and try to do the mapping there the field is there but then it's not listed from the other remote (so switching sides basically).

 

1 answer

1 accepted

0 votes
Answer accepted
Dhiren Notani_Exalate_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 17, 2024

Hi @Csaba Vertessy ,

Thanks for asking your question!

I am Dhiren, one of the solutions engineers working with Exalate.

May I please ask for some more details here, like the connectors involved and also what type of connection did you create (Basic, Visual or Script)?

I would suggest creating a support ticket with us using this link and we can take this discussion forward.

Thanks, Dhiren

Csaba Vertessy
Contributor
February 19, 2024

Hi @Dhiren Notani_Exalate_ ,

It's a Cloud2Cloud connection and I have used the Visual type of connector to create the mappings.

In the meantime I have already raised a support ticket for you.

Thanks, Csaba

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events