• Release History
  • Documentation
  • Back to www.mscrm-addons.com
  • Release History
  • Documentation
  • Back to www.mscrm-addons.com
home/Knowledge Base/Template Designer(DCP)/Concatenate Syntax

Concatenate Syntax

910 views 0 Updated on December 11, 2024

For the Concatenate Type, the numbers are no longer used as of DocumentsCorePack version 2020.53 (If you are still using it, have a look at the Deprecated Combine Types). Now, the individual options can be chosen by writing them as a string in the following syntax:

[Doc|Content]
[KeepSourceFormatting|UseDestStyle]
[AutoLink|Link|LinkAll|Unlink]
[KeepSectionBreak|NewPage|Continuous]
[ContinuePageNumbering|RestartPageNumbering]

For a brief description of the individual options, see below.

If no option of a group [] is specified, the default is used (corresponds to the bolded ones).

Like in this example we use “Doc”, and it would use all remaining default values. The same happens when you leave it blank. If you like to choose another option, you have to write it in the ❶ input field of the Concatenate Type  like:

Doc, UseDestStyle, Unlink, NewPage

Just leave a space and/or a comma between the individual options.


Figure 1: Select Concatenate Type

Here is an overview of the individual options that can be chosen

Define what shall be concatenated:

OptionDescription
Doc (default)This document will be appended to the previous document.
ContentOnly the contents of this document will be appended to previous document. (Headers/Footers/SectionBreaks of this document will be ignored.)

Define how the formatting of this document shall be treated:

OptionDescription
KeepSourceFormatting (default)The formatting of this document will be retained. (If, for example, this document uses a different font for Heading1, that difference will be retained.)
UseDestStyleThe formatting of the previous document will be applied to this document. (If, for example, this document uses a different font for Heading1, that different font will be ignored and the same font as in the previous document will be used for Heading1.)

Define if and how the headers/footers shall be linked to the previous document:

OptionDescription
AutoLink (default)If the first section of this document has no or empty header/footer then it is [Linked], otherwise it is [Unlinked].
LinkThe first section of this document will be [Linked].
LinkAllAll sections of this document will be [Linked].
UnlinkThe first section of this document will be [Unlinked].

Please Note:

  • If a section is [Linked], that means: The headers/footers from the previous section are continued.
  • If a section is [Unlinked], that means:  The headers/footers of that section remain exactly as they are.

Define the type of the SectionBreak between the two documents:

OptionDescription
KeepSectionBreak (default)The type of the SectionBreak between the two documents is defined by the type of the first section of this document. (By default the first sections type is ‘NextPage’, so usually there will be a ‘SectionBreak(NextPage)’ between the documents.)
NewPageConcatenate this document on a new page. (There will be a ‘SectionBreak(NextPage)’ between the documents.)
ContinuousConcatenate this document directly to the end of the previous document. (There will be a ‘SectionBreak(Continuous)’ between the documents.)

Please Note:

  • If the documents have a different page size, then a ‘SectionBreak(NextPage)’ is created between them.

Define how the Page Numbering shall be treated:

OptionDescription
ContinuePageNumbering (default)The page numbering of this document will follow the previous document. (Adding 3 pages to 2 pages will result in: 1/5, 2/5, 3/5, 4/5, 5/5)
RestartPageNumberingThe page numbering of this document will be restarted from 1. The field ‘NUMPAGES’ (Total nr of pages) will be fixed in the previous document and in this document. (Adding 3 pages to 2 pages will result in: 1/2, 2/2, 1/3, 2/3, 3/3

.

Deprecated Combine Types

These CombineTypes are no longer used since DocumentsCorePack Serverversion 2020.53, but they are still working, if you are used to it to determine how document B will be inserted in document A.

 

CombineType = 0 
The formatting of document A will be applied to document B

CombineType = 1
The formatting will be retained.

CombineType = 2
Does the same as CombineType = 0. In addition, the link to the previous section will be disconnected here (disconnects your header or footer from the header or footer in the previous section).

CombineType = 3
Does the same as CombineType = 1. In addition, the link to the previous section will be disconnected here (disconnects your header or footer from the header or footer in the previous section).

CombineType = 4
The formatting of the previous document will be applied to the document. The headers/footers of that section remain exactly as they are. The document will be concatenated on a new page.

CombineType = 5
The headers/footers of that section remain exactly as they are. The document will be concatenated on a new page.

CombineType = 96
The documents are saved locally in the file format .pdf. This uses a more recent method of concatenation than CombineType 98.

CombineType = 97
The documents are saved locally in the file format .docx. Outcome is a .pdf.

CombineType = 98
The documents are saved locally in the file format .pdf.  

CombineType = 99
The content of document B will be inserted at the end.

Please notice: The CombineType field is mandatory otherwise there will be an error.

 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Was this helpful?

Yes  No
Related Articles
  • Ensuring correct time zone display for DateTime fields
  • How to compare a date-fields with the current date 
  • Create a template for XML or plain text
  • E-Invoicing with DocumentsCorePack
  • How to add content from SharePoint to a document
  • Using MS Word field codes in DocumentsCorePack templates
Leave A Comment Cancel reply

You must be logged in to post a comment.

Latest Articles
  • Document Generation via Copilot in Dynamics 365 Sales using DocumentsCorePack
  • DocumentsCorePack: Best practices for Dynamics 365 on-premises to online migration projects
  • Multilingual Support in DocumentsCorePack
  • Recap: ColorCloud 2025
  • Configure DocumentsCorePack within custom pages
Popular Articles
  • DocumentsCorePack Template Designer – Getting Started
  • Step-by-Step: How to configure a One-Click-Action
  • Application Access for Dynamics 365
  • How to find your environment’s unique name in Microsoft Dynamics 365
  • How licenses are counted
Top Rated Articles
  • “Undefined”-labels in Chrome and Edge 114 and higher
  • Important information for Dynamics 365 online customers using DocumentsCorePack and/or AttachmentExtractor
  • How to activate the DocumentsCorePack Connector for PowerApps & Microsoft Flow
  • How licenses are counted
  • How to insert Condition Fields in DocumentsCorePack Templates designer
Categories
  • *News and General Infos* 62
  • Webinars 45
  • Template Designer(DCP 196
  • DocumentsCorePack(DCP 251
  • TelephoneIntegration (TI 65
  • AttachmentExtractor (AE 72
  • PowerSearch (PS 50
  • ActivityTools (AT 61
  • SmartBar (SB 54
  • GroupCalendar (GC 47
Our Vision

“We see it as our purpose to provide products that simplify and speed up our customers’ Microsoft Dynamics 365 experience.”

Knowledgebase
LogIn
mscrm-addons.com
  • Products
  • Online Shop
  • Downloads
  • My Account
About Us
  • About Us
  • Case Studies
  • Newsletter
  • Partner Program
  • Contact
Support
  • Support
  • Terms & Conditions
  • Documentation
  • Webinars
  • Legal Documents
  • Impressum
  • © 2022 www.mscrm-addons.com. All Rights Reserved.