We're sorry AsposeCloud doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.cloud

Aspose Cloud UpdateAll Fields not working

We have a file that we generated programmatically. That file has a ToC in it. When we attempt to open the file we are prompted to update fields (indicating that the dirty flag is set, AS IT SHOULD BE) If we say yes the ToC is generated and everything is great. SP (SharePoint) WAS (Word Automation Services) will update the fields and spit out a file with the ToC generated w/o the prompt. Your site indicates that Aspose SHOULD do the same but thus far our experience has been that the file either gets corrupted or the fields are not updated at all. We have tried using the nodejs example here (https://docs.aspose.cloud/words/fields/update/) with and without the dirty flag set to true and neither updates the ToC.

This begs the question, does Aspose actually support evaluating the pageRefs/page layout?


The API should update the TOC field. Please share your sample document with us. We will investigate the issue and guide you accordingly.

This is a file that is not working

toc_20230510092322.docx (14.2 KB)

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSCLOUD-2323

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

@tilal.ahmad is there any way for us to track the progress of that ticket?


I am afraid you cannot check the status of our internal ticket directly. However, please check the ticket status in the Issues Status window at the right bottom of the thread, or you can ask us for the update.

We believe we have identified the cause of the issue. It appears that you support evaluation of the paragraph property pstyle values but not the Run Property rStyle values. We are using run (<w:r>) property (<w:rPr>) rStyle (<w:rStyle>) values (w:val) to define our heading styles. MS Word handles this properly, Aspose Cloud does not, yet.

      <w:rStyle w:val="Heading1Char"/>
    <w:t xml:space="preserve">ARTICLE I - Jake</w:t>


Thanks for sharing your finding; it will help us investigate and fix the problem.