Word document editor - Track changes - Render a custom field on comment / change card

[swarnkamal.parmar]

We need a metadata field to pass the serial number in the syncfusion xml payload and display it somewhere in track changes card for a word document.

Any suggestions would be highly appreciated?

[Dhanush Sekar]

Hi Swarnkamal,

For the purpose of linking a revision, the Document Editor maintains the revision id. also, the revision id is dynamic.

We have following limitation in providing the requested support.

1. Track change Id is not static as per docx specification.
2. In file level, track change id is zero based index.
3. If one revision is added, track change id for all the track changes present in the document is updated with new Id.
4. Once the SFDT is converted to docx, we can't keep track of track change ids.

Due to the above limitation, we can't maintain static id for track changes. We have attached a video for your reference.

Regards,

Dhanush Sekar

Attachment: media1_(4)_58a8a71b.zip

[Olivia Naylor]

Tracking changes in a Word document editor is crucial for collaboration, especially when rendering custom fields on comment or change cards. It's similar to when you might hire someone to do assignment, ensuring tasks are managed efficiently and accurately, just as custom fields help track detailed edits seamlessly.

[Dhanush Sekar]

Hi Olivia,

Please give more details about this requirement if possible. because the document editor allows tracked changes to be revisions in track changes pane.

How do you expect the custom fields? So, that it will be helpful to understand your requirement.

Regards,

Dhanush S

[Chandia Khalid]

While directly adding custom fields to track changes cards might be limited, you could explore adding a comment with the serial number and attaching a custom property to the comment itself. The property could store the serial number data.

[Dhanush Sekar]

Hi Chandia,

As previously stated regarding track changes, we are unable to maintain static IDs for comments. 

We have following limitation in providing the requested support.

1. Comment Id is not static as per docx specification.
2. In file level, comment id is zero based index.
3. Once the SFDT is converted to docx, we can't keep track of comment ids.

Note:  we can preserve static IDs if the document is kept in SFDT format without converting it to DOCX.

Regards,

Dhanush s

[George Adams]

To include a serial number in the Syncfusion XML payload, consider using a custom metadata field within the <w:docPropsCustom> section. Then, extract and display it dynamically in the track changes card using Syncfusion’s document editor API.

[George Adams]

Check out this article - it helps students develop structured arguments and critical thinking. When exploring literature, understanding the best genres of books can enhance reading choices, providing valuable insights for both academic research and personal enrichment in various fields.

[Dhanush Sekar]

Hi George,

For the purpose of linking a revision, the Document Editor maintains the revision id. also, the revision id is dynamic.

We have following limitation in providing the requested support.

1. Track change Id is not static as per docx specification.
2. In file level, track change id is zero based index.
3. If one revision is added, track change id for all the track changes present in the document is updated with new Id.
4. Once the SFDT is converted to docx, we can't keep track of track change ids.

Due to the above limitation, we can't maintain static id for track changes. We have attached a video for your reference.

Regards,

Dhanush Sekar

Attachment: media1_(4)_58a8a71b_f44bac10.zip

[Ali Raza]

1. Track change Id is not static as per docx specification.
2. In file level, track change id is zero based index.
3. If one revision is added, track change id for all the track changes present in the document is updated with new Id.      Locksmith Huddersfield  
4. Once the SFDT is converted to docx, we can't keep track of track change ids. 

To include a serial number in the Syncfusion XML payload, consider using a custom metadata field within the <w:docPropsCustom> section. Then, extract and display it dynamically in the track changes card using Syncfusion’s document editor API.

[Sujitha Siva]

Hi Ali Raza,

Thank you for sharing your requirement. To help us assess feasibility and provide the most appropriate guidance, we kindly request a few clarifications:

1. Purpose: Could you please share the exact end goal of assigning serial numbers to track changes?
2. Source: Where do you intend to preserve the serial number — will it be passed programmatically within your application.
3. User Mapping: Should the serial number remain consistent for specific cases (e.g., User 1 always receives serial number 01 across all revisions).
4. Persistence: Do you expect the serial number to be preserved only within the application, or should it also be embedded in the exported Word document?

Once we receive these details, we’ll be able to evaluate and suggest the suitable approach.

Regards,

Sujitha S

[Ali Raza]

ChatGPT said:

1. Track change Id is not static as per docx specification.
2. In file level, track change id is zero based index.
3. If one revision is added, track change id for all the track changes present in the document is updated with new Id.       Locksmith near me
4. Once the SFDT is converted to docx, we can't keep track of track change ids. 

To include a serial number in the Syncfusion XML payload, consider using a custom metadata field within the <w:docPropsCustom> section. Then, extract and display it dynamically in the track changes card using Syncfusion’s document editor API.