TOC Tree Structure Not Retained During Build/Publishing

[Jnicol]

My department was using SalesForce Connect to publish articles to a Knowledge community. It was working fine until the powers-that-be decided to ditch SF Connect and team up with SearchUnify. The Flare project is built and published to a server that SearchUnify sweeps to then publish the articles to the SF community. I'm using Clean XHTML as the output type (because of SearchUnify) and File System as the Destination type. When I build and publish to the server, the TOC's tree structure is not being retained. Instead, it's the same folder structure from the project in the Flare Content Explorer. SearchUnify uses the folder structure from the server to build the side-menu in the SF community, which means there are a bunch of folders with names that only make sense to the writers and aren't organized in a coherent manner.

I've researched and tried everything, and I've never had any major issues producing online Help and PDF documents. Does anyone know why the folders are structured like the project and not the TOC?

Out of curiosity, is anyone using SearchUnify or worked with the company in the past? On it's website, the company seems to be big on it's ability to integrate with Flare. However, I was pulled into a meeting with some of their devs and project managers to give them a demo of Flare, how my org uses it, topic-based authoring, and so on. It went from a demo to an abbreviated Flare training session (red flag).

[NorthEast]

Does anyone know why the folders are structured like the project and not the TOC?

Ok, so I don't know anything about SearchUnify, but the only way to include TOC data in the Clean XHTML output is to select Include TOC path meta tag in the target Advanced tab.
That adds basic TOC information in each output topic's meta tag; e.g.:

Code: Select all

<meta name="tocPath" content="Topic 1|Topic 2" />

That's the only way to include TOC data in a CleanXHTML output, so it's entirely down to whether SearchUnify can use that data to create the TOC. You probably need to ask that question to SearchUnify support.

[dc715]

When I build and publish to the server, the TOC's tree structure is not being retained. Instead, it's the same folder structure from the project in the Flare Content Explorer. SearchUnify uses the folder structure from the server to build the side-menu in the SF community, which means there are a bunch of folders with names that only make sense to the writers and aren't organized in a coherent manner.

I've researched and tried everything, and I've never had any major issues producing online Help and PDF documents. Does anyone know why the folders are structured like the project and not the TOC?

Were you able to get the TOC to display as expected? My company is looking into SearchUnify and I'm hoping to get some insights into the current state of the integration with Flare.