Page Comparison

Sometimes an issue will occur where mail merge documents fail to produce certain fields. In this example, we will consider how to solve this for , such as the primary/secondary contacts within the client management module (sContNameFull and sSecContNameFull). This is in essence to do with the way that primary/secondary contacts are created, and requires a simple workaround fix.

To solve this quickly, simply change around the primary and secondary contacts (i.e. secondary to primary, and then back again to reflect its original position). Then test to see if this has worked in respective mail merge document. If this issue still persists, check the mail merge field itself to ensure that is correct and full.

Detailed steps:

Image Removed

...

contact details for a client.

In this case, a simple fix is required.

1. Open Framework ECM, and navigate to the Client / Contacts screen for the trouble job/client.
   
   Image Added
   
   
2. From the available contacts, change the secondary contact to a primary contact as shown above.
   
   Image Added
   
   Image Added
   Note that now the 'Test' contact is now primary, shown by the tick in the primary column, and Insula Test is now secondary, shown by a tick in the secondary column.
   
   
3. Then, swap back the secondary and primary to reflect how the clients were originally (an inverse of previous steps)
   
   Image Added
   Note that the primary/secondary flags would have now reversed, and you will be back at the original primary/secondary position for the client contacts.
   
   
4. To test, run a mail merge document that includes a sSecContFull merge, this fix should generate the secondary contact name correctly.

...