Resolve embedded variables without an "Error while parsing external reference" in Oxygen.

We have defined all of our trademarks as variables, and stored them in a library file, to ensure that they are applied correctly.

Within each publication, we also have variables, such as "software" and "product", which contain embedded trademark variables. So, we might have a topic that appears in all of our Software Installation Guides. In place of the software name, we use the "software" variable. The SCIEX OS Software Installation Guide contains a library file in which the "software" variable is defined as follows: <ph varid=software><ph varref=os></ph></ph>. The software TMs file contains the definition <ph varid=os>SCIEX OS</ph>.

Previously, we were using XMetal, and the variables were resolving correctly. Now, we are using Oxygen, and we are getting the error, "DIspatch not hooked to windows memory", see below.

Variables are resolved and shown correctly in Pub Mgr.

We are using Tridion Docs 14.0.3 with Oxygen 21.1.

Cobina Price-Jones

Cobina Price-Jones over 2 years ago in reply to Larry Kunz

Thanks, that works fine for most variables, but when I have nested variables, I get the error, even though both variables (the first-level variable and the nested variable) are defined in resources in the publication.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Larry Kunz over 2 years ago

Cobina,

I find that if I define the Variables file as a resource within the publication, and then I open the topic for editing from within the Publication (rather than from Browse Repository or from within Oxygen), Tridion Docs "knows" the context and resolves my variables in the Oxygen editing window.

Hope that helps.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Cobina Price-Jones over 2 years ago

Great, thanks!
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel

Tridion Ideas > Tridion Docs Ideas

Resolve embedded variables without an "Error while parsing external reference" in Oxygen.