Hi there,
Thanks for your inquiry.
Please ensure you are inserting the field using the MERGEFORMAT switch. This switch causes the formatting on the original field to be carried over to the merged result.
but when i expand it using the following code the merge code styles are lost for first sentence ie where there are other styles in the sentence.
whereas OfficeName retains** style as it is the only word in that sentence.
If I select the reguar font and then make it bold in e.g. MS office, I will not get the correct bold version. If I select the Bold version of the font, it will seem like it is regular and nothing will happen if I change it to bold.
Is there a "howto for dummies" on how I can make sure that one of them is identified as the Bold weight for the regular font ? I basically want to see it as a single font in e.g. ms office and then it should toggle between them when selecting bold/regular/italic.
I export my output to excel and i want to know How to merge the cells with certain intervals, center allignment etc
for ex, (10,Apple,Red - is one row set ) i want to center alligment the full column value, apply border and make bold only to the second value of one set.
merge the cells in between each row set
Is this possible to do in knime?
my input data
and my expected output
Sample Output730394 6.23 KB
If you just mean formatting the merged text (the whole content of a merge field) with a specific style, e.g. make it bold or italic, you only need to apply this formatting on the merge field itself in the document where you defined the merge layout.
But if you want only part of the merged text to be formatted in a specific way, you could well use e.g. HTML tags (or any arbitrary easily searchable tag) to mark part of the text, then have this text merged, including the tags, and then use Regular Expression in Find and Replace to apply actual formatting:
To facilitate this merger, both Bold and Perennial have been acquired by EverCommerce, a leading multi-vertical service commerce platform. Perennial was acquired earlier this year in February, with Bold following on June 1st.
Coles will share his vision for the new company along with immediate plans for the future at the 2018 Bold Users Conference taking place in Albuquerque, New Mexico, from July 31st to August 2nd. Interested parties can learn more at boldgroup.com.
Bold Group has been providing total business solutions for the security industry for over three decades through Bold Technologies, Ltd. and Perennial Software, LLC, respectively. Our core products, Manitou, SedonaOffice, and AlarmBiller are the leading software choices for over 650 top security companies and dealers globally. Bold Group provides solutions for alarm monitoring and business management software with installation available on-premises or in a secure, Cloud-based environment. For more information on Bold Group, visit www.boldgroup.com or call 1-800-255-BOLD.
I am using Dropbox Sign for Salesforce, and have a series of merge fields I am pulling into my template. I need these merge fields to be bold in format. How can I do this? The only options I have are to select a font type and font size, but I can't apply any other formatting.
As you can see, rather than display a blank graphic, data merge would insert a page break where noted, place a graphic for the Heading and place a different graphic for a Subheading, and skip over the lines that I don't want to show. Are these things possible? I'm new to Data Merge so I don't know if this is within the capabilities of the platform. I also am not sure if this is better done (or even possible at all) with scripting.
InDesign doesn't offer any conditional formatting upon importing text or generating content with data merge. At best, it just interprets styles. The only feature which can define very precise conditions (and act upon it) is GREP. Using textual indicators in your data like "do-show" or "no-show" and "heading" or "subhead", you can let GREP search for these indicators, and apply Cell and Paragraph Styles to those texts, including settings like "Start on next page". And items/rows/paragraphs can disappear by letting GREP delete (actually Find/Replace) the whole paragraph by searching for the indicator.
Data Merge is great for Microsoft Word style mail merges that are one record (not one field, but one record - a row of fields) to one page or one record to many pages, but not so great for many records to one or many pages, such as a catalogue.
I'm getting a very annoying error when merging to a specific branch: I have double-checked (several times) that the workspace is clean, i.e. there are no changes on the workspace before starting the merge. That particular file behaves normally when I apply changes, i.e. I can make changes to the file, undo those changes. There are no changes on that file compared to the changeset that I'm working on (or at least none that would show up but I have confirmed that when there are changes, they do show up).
26075 is the last changeset on this branch (that I'm currently on and merging to). So before I started the merge, there was no change on that file. All changes currently on that file are due to the merge (there was a merge conflict but nothing particularly complicated, could easily be resolved with the merge tool).
I was at first confused about what you meant by "It should be the one in bold" because the alpha UI doesn't bold changesets in the history (regardless of dark or light theme). But I did find it with the legacy UI (also, I just saw that the changeset of the file is also shown in the Workspace Explorer, so that would be the way to find out in the alpha UI, I guess) ... and:
Turns out the active version on that branch was one from a child branch of this current branch that we hadn't merged back into this branch (so that was definitely not the correct version - there's no way I can think of how that version became the active one on my branch). Now I have reverted to the last version on this current branch and after that, it shows the commit I just made as active one. It's really weird that it showed the version from the other branch instead of the commit (if we even did revert something there in this case - it certainly doesn't look like that from the history).
When you create a merge field in Microsoft Word (see Creating a WordWriter Template), you can apply formatting to the field. For example, you can set a merge field's format to "Uppercase" to display the field's value in uppercase letters. WordWriter supports most text, date, and time formats available in Microsoft Word.
You can also set these formatting options by entering special codes in the merge field. To view and edit a merge field's field codes, right-click the field and select Toggle Field Codes. A field without special formatting looks like this:MERGEFIELD FieldName
Using field codes, you can apply date/time formatting to merge fields that will bind to database fields of types Date, Time, and Timestamp, or to an object of type System.DateTime. The general format for applying date/time format codes is:
The following examples generate a Word file from a template that contains merge fields with date and currency formatting. To see (or hide) a merge field's formatting codes:
In this tutorial, we will discuss some advanced customizations for merge codes, including formatting and transforming data in merge codes and replacing strings within merge codes. Let's begin by learning a little more about how merge codes work.
At times, you may need to customize the look & feel of a merge code, or perhaps link the merge code to a url. Both of these actions introduce HTML code around the merge code (behind the scenes).
When HTML is introduced into a merge code, Alchemer will convert any double quotes in the merge code to single quotes (on Save) to maintain the merge code functionality and avoid potentially compromising the HTML behind the scenes.
The bolded text below immediately following the opening bracket and ending before the opening parenthesis is the Merge Code category and defines the available properties (discussed in the next section).
The bolded text below is the property, found between the double quotation marks within the parenthesis. Available properties are determined by the Merge Code category and like the category, they must be all lowercase. If you think of a category as the city in a mailing address, then the property is the street address.
The bolded text below is an attribute of the Merge Code and is matched to the specific property. If the property is the street address of a mailing address, the attributes are the house/apartment/suite number. However, unlike the category and property, you can have none or multiple attributes, all separated by commas in the latter case. Attributes are always paired as an identifier and its value. In the example above, id is the identifier and the value is inside double quotes. They are connected by an equals sign.
df19127ead