Start a conversation
  1. ACRM Support
  2. ACRM - Articles
  3. Public Articles

Aurea CRM: DOCX Template Saves as .DOC When Using “Connection with Word Processor” (Auto-Save/Background)

Contents

Overview

When generating documents using Connection with Word Processor (configured in CRM.win and triggered from CRM.web), the saved file extension may be incorrect during auto-save/background creation. A common symptom is that a .docx template and a “Save document as” value containing .docx still produce an output saved as .doc (for example, test.docx is saved as test.doc).

This is expected behavior based on configuration rules: for automatically saved single letters, Aurea CRM determines the final extension from the Transfer Format → Document Type, not from a manually typed extension in Save document as. No product defect or fix version is associated with this behavior.

Solution

Issue / Symptom

  • Template is .docx
  • “Save document as” is set to a filename that includes .docx (example: test.docx)
  • Result is saved as .doc (example: output becomes test.doc)

Why this happens

For single letters saved automatically (auto-save / save without prompt / background creation), Aurea CRM determines the output extension in this order:

  1. The “Save document as” field is intended to contain the filename without an extension.
  2. The system appends the extension based on the selected Transfer Format → Document Type.
  3. Only if no Document Type is selected, the system falls back to the template’s extension.

As a result, if the Transfer Format’s Document Type is set to a legacy Word type (for example, “Word Document”), the output can be saved as .doc even when .docx was typed into “Save document as”.

1) Update “Save document as” (do not hardcode the extension)

In the relevant Transfer Format in CRM.win, update “Save document as” to avoid manually appending .docx.

  • Option A (no extension): enter a filename pattern without an extension, for example:
    {tablecaption:<your_letter_table>}_{today}
  • Option B (recommended): use the supported placeholder so the extension always matches the configured Document Type:
    {tablecaption:<your_letter_table>}_{today}{extension}
    • {extension} includes the leading dot (for example, .docx).
    • This prevents mismatches caused by manually typing an extension into the name.

2) Set the Transfer Format “Document Type” to DOCX (DOCX MIME type)

In the same Transfer Format, set Document Type to the DOCX type corresponding to the following MIME type:

application/vnd.openxmlformats-officedocument.wordprocessingml.document
(MS Word document (*.docx))

This ensures Aurea CRM appends .docx during auto-save/background creation.

3) If DOCX is missing from the Document Type dropdown (server-side configuration)

If the DOCX option is not available in the Document Type dropdown, add or restore it in the server configuration:

  • Configuration Info Area → Configuration Settings → Word Processor → Document Types
  • Ensure an entry exists for:
    application/vnd.openxmlformats-officedocument.wordprocessingml.document (DOCX)

After adding/restoring the entry, return to the Transfer Format and select the DOCX Document Type.

Verification (Confirm the Fix)

  1. From CRM.web, trigger the same Connection with Word Processor using the updated Transfer Format.
  2. Confirm the generated file is saved with .docx (not .doc).
  3. If it still saves as .doc after selecting the DOCX Document Type, collect and provide:
    1. Aurea CRM version
    2. Microsoft Word version on the machine/server performing the background creation

  4. This helps confirm whether DOCX saving is supported by the installed Word/automation environment.

Frequently Asked Questions

1. How do I know this is the same problem?
You are affected if a DOCX template generates a file saved as .doc (for example, “Save document as = test.docx” but the output is saved as test.doc), especially when “Save without prompt” / auto-save or background creation is enabled in the Transfer Format.
2. Why doesn’t typing “.docx” into “Save document as” force DOCX output?
For automatically saved single letters, Aurea CRM appends the extension based on the Transfer Format’s Document Type. “Save document as” is intended to be entered without an extension (or using {extension}), so a typed extension can be ignored/overridden by the Document Type.
3. What should “Save document as” look like to avoid extension issues?
Use a filename without an extension, or use the placeholder that appends the correct one automatically:
  • {tablecaption:<your_letter_table>}_{today}
  • {tablecaption:<your_letter_table>}_{today}{extension} (recommended)
4. I cannot select DOCX in the “Document Type” dropdown. What do I do?
Add/restore the DOCX Document Type in server configuration:

Configuration Info Area → Configuration Settings → Word Processor → Document Types

Ensure the DOCX MIME type application/vnd.openxmlformats-officedocument.wordprocessingml.document exists. Then re-open the Transfer Format and select it.

5. What if it still saves as “.doc” after setting the DOCX Document Type?
Provide (1) your Aurea CRM version and (2) the Microsoft Word version on the machine/server that performs background creation. The background automation environment can affect whether DOCX save is supported and configured correctly.
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments