I think it might have to do with having conditional text with the variable hidden, the variable definition changed, and then the conditional text exposed. Even if I run Update References, the variables can remain unchanged. In such cases, I have to go through the document and manually update the problem variables. This runs counter to the usefulness of variables, of course, especially if you have a lot of them. Any ideas/suggestions?
No, I haven't had that experience with variables and conditional text. When I update a variable with hidden condition tags, and then show those hidden tags, they show the updated definition.
On a separate note, I'm not sure what Update References has to do it. There's no variables command in there...
Can you document your process—maybe show two variables on the same page where one updates and the other doesn't? Let's see if we can figure it out.
Unfortunately, I don't have any to show right now (all already manually corrected). I'm thinking about this as a workaround: Put the file in a book, have my variables in a separate empty file in the book, and import variables from the empty file as needed (e.g., prior to any publication). Ugly, but it just might work.
Well, if the variables aren't updating normally in the one file, will they update this way? I wouldn't think so, but you'd have to try.
While we know any software application has bugs, this is not one I've come across in FrameMaker, and as you said, it runs counter to the usefulness of variables, so it would be a big deal.
I'm guessing that there's an error in the process somewhere, but I can't help you find it if I can't see it in action.
Ok, here is an example (done with a stale version of the same file). I change 4.11.6 for the variable to 4.11.7, update the variable definition, and the old definition in the doc remains, but only in the conditional text that was hidden (and then set to show):
Any chance the stale variable instances are actually Xrefs to actual variable instances, and didn't get updated for lack of an Update Cross References?
Reasonable question, but no. If I double click the instance, it goes right to the variable definition.
Thanks for the screen shots. Is the blue redacted info? Why did the variable background change from green to gray? Is green the highlight color for Windows? (Just trying to get my bearings.)
So try this:
Then try this again, but hide that yellowish condition. Edit the variable definition, then click Update and show all condition tags. Did it fail to update this time?
I'm able to successfully update variable definitions, whether or not the condition tag is set to Show. If you can't, you can file a bug report here: Tracker.
BTW, I'm happy to look at the file, but based on the redaction and close cropping, I'm assuming you won't feel comfortable sharing it.
Sorry, I still need to try your checks; just haven't had time yet.
HI Bruce, since you're working with AMM, do you have a structured or unstructured doc?
Also, do you have any "extras" in play to allow database access or easier editing of content?
Yes, I'm using Structured FrameMaker (to help define and manage Workspaces, one of the advantages of using Structured). FrameMaker specific extras: Paragraph Tools and Index Tools Pro. I also use Launch-n-Go for text macros (not just for FrameMaker). I should mention that this one document is where I encounter the issue (no others to date), and it is loaded with both variables and conditional text. I can't help wondering if I'm overdriving the Model T!
Yes, I'm using Structured FrameMaker
Hey Bruce—you posted your inquiry in the unstructured forum. I'll move over to the correct one for you.
I have this problem in an unstructured document.
Have you opened a thread in the standard Fm forum?
No, do I need to create a copy of this thread there? This problem seems to occur in both versions of FM; is there a forum for that? Can this tread be moved there.
Most of all I’m informing Adobe so that they can fix this bug.
You may find that your EDD contains the variable definitions, and that you can modify them in the EDD.
One note: Modifying the EDD may result in changes necessary to the DTD as well.
Also, conditional text is often managed by attributes in structured docs. Is this the case in your docs?
By the way, I don't know that you gain any Workspace advantages with structured docs vs. unstructured docs.