Skip to main content

I think I have found a critical bug for API users when in my document I have a form of type "DefaultTableBlock" of a size other than 3 x 3 the document content request returns the figure trimmed to the first 9 cells ( 3 x 3) if the size is smaller the response JSON has empty cells in the same way if the size is larger I lose information.



This is intermittent since if I modify the document moving the pages of the document or delete figures the request for the document content returns the information correctly however if I leave the document without modifying it for at least 5 minutes and return to run the request the error happens again.



however in the diagram displayed in Lucidchart there is no loss of information or any visible errors.



At the moment as far as I've tested this only affects "DefaultTableBlock" figures is it a bug?




Example with bug:



{

"id": "8~wjFQtBQs06"

"class": "DefaultTableBlock"

"textAreas": [

{

"label": "Cell_00"

"text": "test1"

}

{

"label": "Cell_01"

"text": "test2"

}

{

"label": "Cell_02"

"text": ""

}

{

"label": "Cell_10"

"text": "1"

}

{

"label": "Cell_11"

"text": "2"

}

{

"label": "Cell_12"

"text": ""

}

{

"label": "Cell_20"

"text": "3"

}

{

"label": "Cell_21"

"text": "4"

}

{

"label": "Cell_22"

"text": ""

}
}


Example after edit the document 


{

"id": "8~wjFQtBQs06"

"class": "DefaultTableBlock"

"textAreas": [

{

"label": "Cell_00"

"text": "test1"

}

{

"label": "Cell_01"

"text": "test2"

}

{

"label": "Cell_10"

"text": "1"

}

{

"label": "Cell_11"

"text": "2"

}

{

"label": "Cell_20"

"text": "3"

}

{

"label": "Cell_21"

"text": "4"

}
}

Hi @team f thank you for posting in the Lucid Developer community and thanks for bringing this to our attention! I was able to reproduce this behaviour in our document contents endpoint and I have reported this to our API team. We will update this thread as soon as we have more information.


Thank you for the heads up and patience! I'm sorry for any inconvenience this may cause. Please don't hesitate to let us know if you have any other questions!


Hi Team F


We have found a solution to this bug and are currently going through our review and release process. We'll update you here when the changes are live.


Hi @team f


The fix should be live now. Let us know if it works for you.


Hi Jacke C and Team Lucid


I wanted to extend my gratitude for your assistance – the fix is working flawlessly!
Your support is greatly appreciated Thank You!!


Best regards 


Reply