Recently active topics

Developing a LiveDoc in German and running into issues with German number formats.To get the format 1.234 I enter in the Format tab, Custom Types: #.##0,  (variable Type is Integer).The issue is that #.##0, adds a leading period for values under 1,000 (e.g., .234 instead of 234). I’ve tried various things to remove the leading period but can’t find a solution that works for values equal or greater than 1000 and values less than 1000. Any suggestions or solutions for this?

We’re working on Taxonomy and Tagging, and looking for ideas from more experienced users.  What do you find is the most popular way your sales team surfaces the content they need to quickly serve their customer?  I realize the answers will be different for everyone, but I’m wondering what your sales team chooses most?  It may be one of these examples, or something completely different that we haven’t thought of yet:  Buyer Persona, Content Purpose, Sales Cycle, Content Type, Industry, Product Category, etc.   Thanks in advance!  

Hi everyone - my team is looking to enhance our content governance and dependency management using Seismic.Here’s an example of what I mean:Currently, when we publish a new version of a Data Source, we need to know every downstream Reference Slide and LiveDoc that references the old version so we can update them. Right now the only way we've found to do this is clicking into each object individually in the UI — which is slow, painful, doesn’t scale, and leaves us open to manual error.We would prefer to set up queries/alerting for several rules - for instance, downstream Reference Slides/LiveDocs should never be using outdated versions of Data Sources. How can we accomplish this?It seems like the Reporting API tables that come with the Snowflake Data Share aren’t meant for this purpose - I’ve searched through the tables but can’t find the necessary data points to create a dependency query.After some more research, we haven't found any Integration or Library API endpoint that exposes the