Skip navigation
Currently Being Moderated

Variables within Tables in Insets

Jan 24, 2013 2:02 PM

Tags: #framemaker #tables #11 #variables #inset

We use insets. We have just upgraded to FrameMaker 11 recently. We share inset files in multiple "container" FrameMaker files. When a variable is within a table in an inset, when the inset is updated in any way, the inset does not respect the variable definitions of its "container" file.


If you sweep new variables into the container file, the inset updates. As soon as you update the file via a book update or update the inset itself in the container file, the inset reverts to its own definitions. The insets are properly set to inherit their formatting/variables/conditions/etc from their container files. If the variables are outside of a table, they inherit the definitions properly. Is this a bug? Has anyone else experienced this and fixed in on their own?

  • Currently Being Moderated
    Jan 24, 2013 9:16 PM   in reply to ASnyder28

    I just tried this and I don't seem to get this behaviour. If I update the variable and the imported flow is set to use the curren document features, the variables tak on the correct values regardless of whether or not their in a table.




    When you double-click on the text inset in the table and get the Text Inset Properties pane, check the Settings to ensure that they have "Reformat Using Current Document's Format" enabled.



    Mark as:
  • Currently Being Moderated
    Jan 25, 2013 10:21 AM   in reply to ASnyder28

    As soon as we update the inset, the inset's settings win again.


    I am probably grasping at straws here...


    If you have a container file open and update the inset file, the container file probably does not update immediately, even if set to automatic update. You may have to select the inset in the container file and click Update in the Test Inset Properties dialog.


    Again, I am just guessing because I am not sure of the sequence of steps you are taking...or maybe I am completely wrong about my premisses.



    Mark as:
  • Currently Being Moderated
    Jan 25, 2013 10:47 AM   in reply to ASnyder28

    I've tried following your steps, but I simply don't see this behaviour happening. Several questions for clarification.


    1. When you "edit" the text inset source, exactly what are you changing - the variables or some other content?


    2. When you say the "inset's settings" win, do you mean that the source variable definitions used in the inset show instead of those in the container file?


    3. When you "update" the inset, do you mean that you've made some sort of edit to inset source file and then do a Save on that file?


    4. What precisely do you mean by "sweep the correct variable into every inset" ?


    6. How exactly (menu, double-click the inset & update or close & open file) are you doing the inset updates in the container files?

    Mark as:
  • Currently Being Moderated
    Jan 25, 2013 1:59 PM   in reply to ASnyder28

    Bug confirmed - specific to FM11!


    Andrea sent me a sample set of files. I had misread Andrea's initial post and missed the part about the variable being within a table in the inset source file. I had been testing pulling the inset into a table... Doooh, whack! When this scenario is pulled into the container, the variable stays per the source *only* if it is in the table. The same variable used outside of the table in the inset source does take on the container value, so one sees both values for the same variable in the inset.


    Testing in FM8, 9 & 10 shows that these versions behave as expected. I've also compared the MIF versions to see if there's anything different in the FM11 version, but they're identical.


    Please file a bug report at: FrameMaker Bugs & Wish List


    and reference this thread:

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points