Document Mailmerge issue on custom entities

Hello,

I've created a new custom entity "fleet" depending on companies.

My goal is to create a template with fields from that new entity but also from company, person, address, newprduct and familyproduct.

When I add some search Select field (flee_companyid,...) in the template I get only the ID on the document not the name (but that seems logical).

So I decided to change the vMailMergeFleet view. I added joins to product, productfamily and address (inspired by vOpportunityMailmerge).

But it doesn't resolved the problem. Instead of the filed value I get only the name of the field.

(By the way, this is the same problem I got with mailmerge on communication, not yet resolved...)

How can I resolve this?

Thanks for your help.

Jerome

  • 0

    Hi Dinesh,

    I use version 7.1g.

    I will try with patch H if it resolves the issue.

    Jerome

  • 0
    Hi,
    I have checked the same at our end and found that it is working as expected. We are using the Sage CRM 7.1 version h patch. Can you confirm the version and patch you are using?
    Sincerely,
    Dinesh
  • 0

    I have the same problem with 7.1g (integrated with Sage200) and can therefore not move to 7.1h.

    Are there any hotfixes?

  • 0

    Ok, I resolved mine.

    I upgraded yesterday from 7.1d1 to 7.1g and as part of the upgrade the system reported errors in 7.1ViewsUpdate.esChange. One of these referred to vMailmergeQuotes.

    The update returned message: "Error creating view vMailMergeQuotes:The view vMailMergeQuotes contained in the view script is different to the view existing in the database. The script view has been saved as vMailMergeQuotes_new".

    I, of course, checked both views and ensured all data was fine and expected that to be the end of it.

    However, in order to overcome the above problem I had to copy the contents of my vMailmergeQuotes to notepad, replace it with the original script and save, then paste the notepad contents back in and save and now it is picking up my customised fields and returning proper data.

  • 0

    Spoke to soon. that only worked for 1 quote template out of 5 (and the smallest one at that) and I am guessing that there were other contributing factors as I was testing all kinds of things before I got data returned.

    Anybody come across this and managed to resolve? Using Sage200 CRM therefore unable to try out 7.1h.