Forum Discussion

mangru's avatar
mangru
Copper Contributor
Oct 25, 2024

Newest Office365 word update damages tables

In newest Office365 Word table (one column) in table (many columns) with fixed width does not work.  It works as "Adjust by content" even if I enforce fixed width. If document was correct, and you open with a new Word and save it - document becomes damaged.

 

If you open with old word - it opens and saves as expected. Problem is that all Office365 became updated this week, and we can not fid how to revert to old version.

 

This is critical issue - all words templates becomes damaged after saving. Is there any workaround to fix this issue?

  • Kevinzeng's avatar
    Kevinzeng
    Copper Contributor

    I have a similar issue. My original Word documents had the right border of the nested table lining up with the right border of the outer table. However with the new Word update, the right border of the nested table is automatically indented to the left. I have tried the below methods to make the border of the nested table flush with the outer table.

    • 'Table Layout' -> 'Autofit' -> 'Fixed Column Width' -> setting 'Column width'
    • 'Table Properties' -> 'Cell' -> 'Options' -> uncheck 'Cell margins: Same as whole table'
    • 'Table Properties' -> 'Column' -> set preferred width

    None of the above methods worked as the right border of the inner table will temporarily line up but then will snap back to its original indentation. I have also tried a quick repair of the application which didn't work.

    I should also mention this issue only arose recently when I edited my document on my Macbook over the past week and then reopened the document today on my PC. Now every document I open on PC has this issue.

    Any help would be greatly appreciated as I have many years of documents formatted like this and all have the same issue with text/table contents being cut off by the border.

    Right borders of nested tables don't line up with right border of outer tablesText is cut off
  • lucgrass's avatar
    lucgrass
    Copper Contributor

    I have a similar issue. I want to export a Jasper report with a simple table to Microsoft Word. I encountered a formatting issue with the table starting from MS Word version 2409, while in earlier versions, the layout appears correct. I tried different Jasper versions (6.20.1, 6.23.1, and 7.0.1), but the issue persists.

    Here are the details:

    In Jaspersoft Studio, the table displays correctly in the preview.
    When I export the table to Word (.docx) and open it in a Word version prior to 2409, the layout matches the preview in Jaspersoft Studio.

    However, in Word version 2409, the result changes significantly: the column widths are altered, making the report less readable.

    Any help to resolve this issue would be greatly appreciated.

    Thanks in advance.

  • mangru's avatar
    mangru
    Copper Contributor
    I have a temporary solution - I installed MS Office 2010 on another computer. It works as expected - tables are not damaged.

    Newest office still has that issue - I hope it will be fixed soon.
    • mangru's avatar
      mangru
      Copper Contributor

      But hey are - client tried to modify the document, and got exactly same results. I tried creating from new - and also same result - table in table gets damaged. It is impossible to create fixed width cells in table, which is in another tables cell anymore.

  • eseligmancrm's avatar
    eseligmancrm
    Copper Contributor

    I have also been having this issue on multiple docs we use for docgen. versions from prior to late october seem to be fine, but any time we open any of them to make changes a handful of nested tables have their columns shifted with no way to fix them. Any attempt to drag or manually enter column widths momentarily changes them before snapping back to how they were (or something worse) on their own. Fixed column width has been confirmed enabled on all of them as well.

  • me_5's avatar
    me_5
    Copper Contributor

    I am having this issue as well. Is there a way to report this to Microsoft directly?

Resources