Skip to main content
Solved

Export of CSV Shape Data - Inconsistent


Forum|alt.badge.img+1

Hello Lucid Community,

 

I have been leveraging the ability to export csv shape data from Lucid for the past several months; however, recently I’ve noticed that the shape names data are now coming back inconsistently.  I wanted to learn if anyone else is experiencing this and/or if there is a way I can address the issue myself.  This does appear to be a regression in Lucid’s export csv shape data from what I’ve experienced.

I can use the exact same shape and then export the csv and the shape name will come back as a [custom title I created], but then other shapes that are of the exact same type will show a default name that Lucid provides the shape and is not using the [custom title I created] when naming the shape.  

Two reasons I think this is a regression, One- I have examples of a csv export of shape data for the same Lucid document that was exported months ago and if I attempt to run the same export of shape data today for the same file, the names of the shapes are no longer the same as what they were when I exported the csv shape data months ago.  Note, no changes were made to the Lucid document itself, it is just the name of the shape in the new csv export that is different.

The 2nd reason is that when working in a Lucid document and I add one of my custom names shapes to the file and I immediately export the csv to shape data before exiting the Lucid document, I will see the appropriate custom name of the shapes that I just added.  But, if I exit and come back to the Lucid document and attempt to export the shape data again, the shape names change back to a default name the Lucid provides them and it does not retain the original custom name I gave them and thus the export is inconsistent.

Thank you to anyone who can help me work around this.  We have written code to leverage the Custom naming we provided shapes within Lucid, but now we’re finding we have to go back and edit the csv shape name data.  If I were to guess, I’d say I first noticed this issue in late February 2025.

 

Best answer by Emma D

Hi ​@LucidProductSupportNeeded, just an update on this. After further testing, we were able to reproduce this behaviour and have reported it as a bug. It looks like this happens when the custom shape library containing the shape is not enabled/loaded in the Shapes menu to the left of the canvas.

As a workaround, you can favorite the custom shape library containing the shape(s) in question.  This will ensure that it is always enabled when you reload the document. You can do this from the Shapes menu by clicking the star icon next to the library name.  

I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below. Thanks again for bringing this to our attention.

View original
Did this topic help you find an answer to your question?

Emma D
Forum|alt.badge.img+7
  • Lucid support team
  • March 28, 2025

Hey ​@LucidProductSupportNeeded, thanks for posting! We can’t reproduce the issue you described, so it might be specific to your documents and/or custom shapes. As a test, could you try creating a brand new custom shape in one of the affected documents and then checking if its name is retained in the shape data CSV export? 

Would you also be willing to share a temporary Support PIN for one of the affected documents?  This will allow us to take a closer look at the issue you’re experiencing. For more information on generating a Support PIN, check out this Help Center article.

 


Emma D
Forum|alt.badge.img+7
  • Lucid support team
  • March 31, 2025

Hi ​@LucidProductSupportNeeded, just an update on this. After further testing, we were able to reproduce this behaviour and have reported it as a bug. It looks like this happens when the custom shape library containing the shape is not enabled/loaded in the Shapes menu to the left of the canvas.

As a workaround, you can favorite the custom shape library containing the shape(s) in question.  This will ensure that it is always enabled when you reload the document. You can do this from the Shapes menu by clicking the star icon next to the library name.  

I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below. Thanks again for bringing this to our attention.


Forum|alt.badge.img+1

Thank you for the feedback and I’m glad you were able to reproduce the issue. We are using a custom shape library and it is selected as a favorite; however, it appears that they only keep the shape name before I exit the document. When I come back to the document and re-export, the shape names are lost and they go back to their default naming convention. For now, I’ll continue to manually change the shape names on the export itself unless there may be another workaround until the bug is squashed. Thank you again.


Emma D
Forum|alt.badge.img+7
  • Lucid support team
  • April 4, 2025

Hi ​@LucidProductSupportNeeded, sorry to hear that workaround didn’t work for you! When you reload the document, I recommend double checking in the Shapes menu just to make sure that the favorited/pinned custom library is appearing before you export again (as shown below)- sometimes this can take a second to load in. 


It’s also worth mentioning that the actual custom library needs to be enabled/pinned (even if the shape is already appearing under ‘Shapes in Use’). Finally, it needs to be enabled/pinned for the individual currently doing the export.
Apologies again for the disruption- we’ll be sure to let you in an update here once we have any news on a fix.


Reply