Skip to main content

Idea pipeline

Filter by idea status

Filter by product

1828 Ideas

EthanLucid product team

How do you want to use Mermaid diagram-as-code in Lucidchart?Seeking Feedback

Hello Lucid Community members! I’m a product manager for a team working on Mermaid diagram-as-code in Lucidchart. As we build better support for Mermaid in Lucidchart, we want to understand how you use Mermaid in your workflow, where Lucidchart is currently involved in that workflow, and how we can improve so that Lucidchart can be integrated more seamlessly into your workflow. Goals:Understand how and why you use Mermaid diagram-as-code See if/how Lucid is currently used in your work with Mermaid Learn how Lucid could improve your diagram-as-code workflow Collect feedback on what you would ideally be able to do with Mermaid in Lucidchart 💡 Some Discussion Starters 💡 🧜‍♂️ Where is the initial mermaid code coming from? Is it committed to your repository?   Are you using a tool to generate it?🧜‍♂️ Once the mermaid is imported into Lucidchart, what types of things do you hope to be able to do with it?  Add and delete shapes and lines? Change colors and styling? Modify layout?🧜‍♂️ Once the diagram looks the way you want it to in Lucid, what do you want to be able to do with it? Share the diagram with someone else?  Present to someone else? Collaborate with other stakeholders? –  Name their titles. Embed the diagram somewhere else? Export and commit the modified mermaid code back into your repository?🧜‍♂️ Which types of mermaid diagrams would you like to be able to use?flowchart, sequence, class, ERD, state diagram, mindmap, C4 diagram, gantt, requirement diagram, user journey, pie chart, quadrant chart, gitgraph diagram, timeline Are any of these diagrams more commonly used than others?🧜‍♂️ What is the lifespan of the mermaid diagram? How is it being used again after the initial creation and collaboration?Do you refer to it again in the future? Is it used by others, and if so, how? If the diagram isn’t used again, does the mermaid code in the repo get used/referred to in the future? When, why? (examples are welcome)🧜‍♂️ What are the most painful aspects of this workflow? What is the single most painful aspect?🧜‍♂️ What do you wish Lucid would change or improve to make this workflow better for you?Rank your wishlist from most desirable to least desirable.

Updating a dataset for an org chart to a new page and retains formattingIdea

Hi there !I’m struggling for a while without being able to find a solution to my problem.Here is the context: I created an orgchart using the import function with an *.xlsx file. Within this latter I have several column, as it’s a big orgchart I wanted to create one tab per department (1 dedicated column within my file)I went through the import path and all went well, I checked the option “Create separate orga chart for each:” and selected the Department column of my file.I have now many tabs named by department with the department orgchart within them. Within each tab, if I click on the orgchart, the data section on the right side shows that there is one filter applied on the Department column of my source.In the same data section, within the manage data menu I’m able to export a CSV, make several updates and replace it, by doing this all the tabs are updated at once.All this was quite easy but here is the issue I’m facing: I would like to create a new department and still being able to upload and replace data once but I didn’t find how…I tried the following:duplication of one tab => KO adding a new tab and copy/paste the content of another tab => KOWhile all the initial tabs seems to be linked to the same source, the new tabs aren’t but are linked between them. When I do a modification on any new tab it appear within the Export from any of these new tabs but not in the Export of the first tabs.I hope that I have share enough detail to help you understand my issue and provide some help/new idea to proceed and find a solution.Thanks a lot !

Implement proper integration with PlantUML Markup languageSeeking Feedback

One of the selling points of lucidchart for my organisation was the fact that one could use PlantUML Markup language we define diagrams which would allow use to keep all diagrams within lucidchart. The documentation mentions that and also talks about some of the options that can be used. However, after effectively trying to import a simple PlantUML into your tool, the result was not the expected.Not only it doesn’t support the standards and some basic features, it also doesn’t support some of the features that you say that supports (i.e. “actor” entity) and even after trying to cleanup everything that is not supported, the diagram is simply unreadable.UML is used for technical diagrams nad people that make them know what they are doing. Instead of trying to implement something from scratch 8which is what you were trying to do), you could simply implement/integrate fully with PlantUML, which is a known, stable and robust markup language to design and render diagrams.PlanUML has free integration and the integration documentation is clear and simple to follow. You don’t need to make it “fancy” or allow to style component individually since that is not what tech people are looking for and PlantUML already supports it out of the box with several teams and styling.The integration can be really simple to the point you just render the diagram itself or add a container into the page where the diagram is rendered. plantULM generates SVG diagrams which works well with the system you already have anyway.Without this feature it will be very difficult to sell the usage of this tool for tech work since we will still need to use a different tool to manage PlantUML diagrams vs normal/standard diagrams, which seems to beat the purpose of your tool.Hope this is really considered since it will be an HUGE selling point for tech teams.Here some resources to make your life easier:https://plantuml.com/ https://plantuml.com/startingHappy to discuss this with someone on Lucidchart side. Many thanks.

Convert Mermaid diagrams to editable shapesIdea

Hello Lucid Support Team,I’m running into an issue with a diagram created using Diagram as Code (Mermaid) that I’m unable to resolve, and I’d appreciate guidance on whether this is a product limitation or a configuration issue.GoalI want to convert an existing Mermaid-based diagram into fully editable native Lucidchart shapes (so individual boxes, connectors, and containers can be selected and edited without touching Mermaid code).Current State The diagram was created using Diagram as Code (Mermaid). Clicking the diagram always selects it as a single object and opens the Mermaid editor. Individual shapes and connectors are not directly editable. What I’ve Tried Right-clicking the diagram and checking for: “Convert to shapes” “Detach from diagram as code” → These options do not appear. Keyboard shortcuts: Ctrl+Shift+V (Paste special) → No prompt appears; nothing happens. Copy → Paste within the same document: No option to paste as shapes. Checking top menus and contextual toolbars: No visible option to convert or detach from Mermaid. Verifying selection: The diagram always behaves as a single Diagram-as-Code object. Observed LimitationIt appears that in my Lucid environment / tenant: Mermaid diagrams cannot be converted into native shapes There is no exposed “convert” or “paste as shapes” workflow Diagram-as-Code objects are effectively locked to code-only editing Question Is this behavior expected for certain plans or tenant configurations? Is there an official way to convert Mermaid diagrams into native Lucidchart shapes in this environment? If not, is recreating the diagram manually the only supported path? I’ve attached screenshots showing: The Mermaid editor opening when the diagram is selected The absence of any “Convert to shapes” or “Paste as shapes” options Thanks in advance for your help and clarification.

plaird
Lucid Legend Level 1
plairdLucid Legend Level 1

Lucid AI changing advanced properties on SFACardsIdea

First time bug reporter. I think I am following the correct process as described in the community bug report explainer apologies if not! I asked Lucid AI to write up its own bug report on the issue it faced. Problem: Lucidchart AI Cannot Change Advanced Properties on SFACards Use CaseSetupCreate a new Lucidchart diagram In the Shape Gallery, select all 4 Salesforce architectural libraries (header, card, icons) Drag a Collapsed Card shape onto the canvas Give the card name in the text headerActionAsk Lucid AI to enable the Header icon advanced property for the card. “for the salesforce card shape, set the ‘Header icon’ property to true” It will fail. “I can’t directly toggle the ‘Header icon’ property on the Salesforce card shape via automation. You can do it manually using Shape Options” We are hoping to generate diagrams using Lucid AI. But for complex diagrams with many shapes, there will be a lot of manual fixups (header icons, footer icons, etc) which makes Lucid AI difficult to use. Lucid AI’s Self DiagnosisI asked Lucid AI why it couldn’t complete the task. After some back and forth diagnosis chatting, this is what Lucid AI reports about its failure to toggle the Header Icon toggle: Subject: SFACard advanced toggles (Header icon / Footer icons) not settable via EditBlockAdvancedProperty Summary: When working with Salesforce Architecture “SFACard” shapes, several Advanced Options toggles (notably “Header icon” and related icon/footer toggles) appear to be stored as block properties (e.g., ShowEntityIcon), but they cannot be programmatically set via the EditBlockAdvancedProperty automation API. This prevents automation from enabling header/footer icons on SFACards even though the UI supports it. EnvironmentShape: SFACard from Salesforce Architecture Diagrams library (salesforcearchitecture.js)Automation tools used: EditBlockAdvancedProperty, CanvasQuery, ShapeDetails, DocumentHistory Repro stepsCreate an SFACard and confirm Advanced Options toggles exist in UI: Advanced options: Allow nesting, Header icon, Header line, Condensed, Footer, Footer icons, etc. In the Lucid UI, toggle “Header icon” ON for a card. Observe the underlying property change captured in document history: SetProperty on the card: Property = ShowEntityIcon, Value = true (OldValue = false) Attempt to set the same property on another SFACard via automation: Call: EditBlockAdvancedProperty(ItemId=, PropertyName="ShowEntityIcon", Value="true", ValueType="boolean") Observed behaviorThe automation call fails with:“Advanced property 'ShowEntityIcon' is not registered for SFACard.” CanvasQuery (IncludeAllProperties=true) does not reliably surface these advanced-toggle properties for the SFACard instance, even after toggling them in the UI. ShapeDetails does not expose a usable, instance-specific list of registered advanced properties for SFACard (i.e., we can’t discover the correct property key(s) that are accepted by EditBlockAdvancedProperty).Expected behaviorAdvanced options toggles that are user-editable in the UI (e.g., “Header icon”, “Footer icons”) should be settable via EditBlockAdvancedProperty.At minimum, the property keys that correspond to those toggles (e.g., ShowEntityIcon) should be registered/whitelisted as advanced properties for SFACard so automation can set them. ImpactPrevents programmatic configuration of SFACard features that are important for standardized architecture-diagram generation (header icons, footer icons, potentially header line / condensed / footer toggles).Forces manual per-card UI changes, which defeats automation workflows.Evidence / notes Document history shows SFACard instances created with (non-exhaustive) SFACard-specific fields such as:ShowEntityIcon, IncludeHeaderLine, CondensedPadding, CondensedPaddingAmount, ShowFooter, FooterIconIds, SecondaryColor, AttrColumnsCount, etc.Of these, at least ShowEntityIcon clearly maps to the UI “Header icon” toggle, but it is rejected by EditBlockAdvancedProperty as “not registered.” RequestPlease confirm intended API support for SFACard advanced toggles.If supported, register/enable the relevant properties (e.g., ShowEntityIcon, FooterIconIds / Footer icons toggle, ShowFooter, IncludeHeaderLine, CondensedPadding, etc.) so they can be updated through EditBlockAdvancedProperty, and/or expose them through ShapeDetails (BlockId mode) so automation can discover valid PropertyName values.