🚀 go-pugleaf

Hi Jen,

Here's some ideas... but be forewarned that I'm not a variable expert.

Variable definitions are part of a document's template, not its content. When you import XML, you import into a template, so it makes sense to me that you'll get whatever formatting is in the template. (that is, the variable will be whatever is defined in the receiving template). Frame is supposed to write out entities for variables on export, which includes the variable text. However, I don't think that it is advanced enough to redefine the template upon import, although I could be wrong. If I'm not, you'll need an import/export API client to pull this off.

This might also be simply a job for an import checklist - with the last step being to import variable definitions.

I think the core of your problem, though, is that you are attempting to mix an unstructured component with markup. What I would suggest is finding a different way of denoting your conditional material using the markup itself, instead of an old FM gizmo. You have an endless amount of metadata available once your document is structured, and there are some native features that can help you control content with it. If you venture into FrameScript, plugins, or the API, the possibilities are virtually endless.

Russ