MERGEFIELD nested IF conditions

I have 2 Code fields in a Mail Merge doc. They are on the same line, and between them I would like a forward slash. However, if either field is blank I would not like the forward slash to display.

So 3 possible outcomes:

• Code_1 / Code2
• Code_1
• Code_2

Currently I have the following { IF { MERGEFIELD Code_1 } = "" "" { IF { MERGEFIELD Code_2 } = "" "" "/" } }. However, this doesn't seem to work, I just get MERGEFIELD displayed. I am adding a proper IF rule to create the field, then I am editing the expression within the Edit dialog. I have found several topics on this, and the only difference I could see is that one solution has additional quotes around the second IF expression, but I couldn't get that to work either.

Any help to adjust this to work would be appreciated, or perhaps I'm doing it completely wrong and there a much better way to achieve the desired results ?

From your description, it seems that the MERGEFIELD code is not being evaluated and is instead being displayed as text.

One possible reason for this could be that the field code is not being updated. To update the field codes, you can press F9 or right-click on the field and select "Update Field."

Regarding the syntax of your IF statement, here's an example of what it should look like:

Please Login or Register  to view this content.

Notice that the second IF statement is enclosed in quotes. This is because it is being used as the "false" value for the first IF statement.

If the above solution does not work, you may want to try replacing the curly braces with chevrons, as some versions of Word require this. Here's an example:

Please Login or Register  to view this content.

or maybe

Please Login or Register  to view this content.

This statement checks if Code_1 is empty, and if it is, it displays Code_2. If Code_2 is empty, it displays Code_1. If both fields have values, it displays both fields separated by a forward slash.

Make sure to include the curly braces {} around each field and the entire statement.

Thanks again for your effort, but I've cracked it.

I didn't notice before, but when viewing the Field Codes the curly braces within the expression weren't as dark as the pair wrapping it, so clearly they weren't being parsed as expected.

I found that I had to build the full expression up in stages...

Add a single IF rule.
Toggle the Field Codes.
Click inside the FALSE argument.
Add another single IF rule in this position.
Highlight the result from the second IF rule, and Toggle the Field Code.
Then just finally clean up the required TRUE and FALSE values.

Madness how fiddly that is!