Missing ConnectedTo in exported JSON

Question

I am extracting my chart which has shapes with custom data fields and while I was doing this I have listed the connections between shapes. The issue I’m having is that even though the chart shows a visually connected the JSON has NULLs in the ConnectedTo fields.

 {            "id": "dDPlxxxF0BoT",            "endpoint1": {              "style": "None",              "connectedTo": "7bxxxO~cExxTq"            },            "endpoint2": {              "style": "Arrow",              "connectedTo": null            },            "textAreas": [],            "customData": [              {                "key": "Logic",                "value": ""              }

I’ve tried many times to connect the shapes but I cannot get the connectedTo to reflect the connections.

vscala · Answer

Hi there! Thanks for sharing the example.

The response shows that the connection is recorded for endpoint1, but not for endpoint2. Since the second endpoint appears connected in the document, let’s verify whether Lucid is registering and saving that attachment correctly.

Please try the following:

1. Confirm that Line connections is enabled in the document settings.
2. Select the affected line and drag the endpoint away from the shape.
3. Drag the endpoint back to the shape’s border.
4. Wait until the target shape highlights, then release the endpoint while the highlight is still visible.
5. Move the target shape as a test. If the endpoint is attached, the line should move with the shape.
6. Wait for the document to show that all changes have been saved, then request the document contents again.

Lucid’s documentation defines connectedTo as the ID of the shape or line to which the endpoint is attached, or null when it is unconnected:

https://developer.lucid.co/reference/document-contents-resource
https://help.lucid.co/hc/en-us/articles/16157138194836-Add-and-style-lines-in-Lucidchart

If the field still returns null, could you provide some additional information?

Was the document created manually, from a Lucid template, imported from another format, created through the Public API, or created by an integration or editor extension?
How were the affected shapes and lines created? Were they drawn manually, imported, generated by an integration, created by Lucid AI, or copied from another document?
If an integration created them, which API or SDK endpoint or method was used? A sanitized example of the input would be helpful.
Can you reproduce the behavior with two standard shapes and a standard line in a new blank document?
Are the affected line or shapes locked, grouped, contained within another shape, or generated from linked data?
When you move the expected target shape, does the line endpoint move with it?
Is the issue limited to one endpoint, one line, or a particular custom shape type?
Are the line and expected target shape on the same page?
Does the expected target ID appear in that page’s `shapes`, `lines`, or `groups` collection?
Which API endpoint and `Lucid-Api-Version` header are you using?
Does the result remain the same after refreshing the editor and requesting the document contents again?

A short screen recording showing the endpoint being connected and then the target shape being moved would also help us determine whether this is a visual overlap or a stored attachment.

If the line follows the shape when it is moved but the API still returns null, that would be unexpected. In that case, in a support ticket, can you please provide the document ID, affected line ID, expected target shape ID, API version, and a support PIN. Please don’t post a support PIN or sensitive document information publicly.

Create an account in the community

Log in to the community