Skip to main content
Practitioner ⭐️
March 1, 2023
Solved

Could not create transformation for edges/relationships

  • March 1, 2023
  • 6 replies
  • 220 views

It seems I can create transformations for types but there is no option to select a relationship when creating a transformation to a data model. Below it shows the “Target type and relationship” dropdown only has types but not relationships. Is there anything I missing?

 

 

    Best answer by Anders Hafreager

    We are happy to share that transformations now support edges! It should appear naturally in the list where you choose what to ingest, and you are guided to find startNode and endNode which are the two required properties on the edge (in addition to the edge type).

    6 replies

    Committed ⭐️⭐️⭐️
    March 2, 2023

    Hi,

    Thanks for reporting this.

    No, you are not missing anything. This is a known bug and the team is working on a fix.

    Practitioner ⭐️
    March 6, 2023

    Hi,

    Thanks for confirming this is an known issue. I just tried to switch to use the API to post an edge instead. I am able to ingest nodes but could not ingest an edge through the API. To ingest an edge it requires a “type” field, which needs an “externalId” field. Do you know where I can find the “externalId” for the edge? 

     

    Anders Hafreager
    Practitioner ⭐️⭐️⭐️
    Practitioner ⭐️⭐️⭐️
    March 7, 2023

    Hi,

     

    thanks for asking. This is being added these days and should be available in the UI within a week or two. In the meantime, the API can be used to add edges.

    Anders Hafreager
    Practitioner ⭐️⭐️⭐️
    Practitioner ⭐️⭐️⭐️
    March 23, 2023

    We are happy to share that transformations now support edges! It should appear naturally in the list where you choose what to ingest, and you are guided to find startNode and endNode which are the two required properties on the edge (in addition to the edge type).

    Expert ⭐️⭐️⭐️⭐️
    March 23, 2023

    Xaiofeng, Can you confirm this is resolved?

    Jason

    Practitioner ⭐️
    March 27, 2023

    Yes, it is already fixed. Thanks!