Hi,
I have just installed suitecrm 7.1.4 on a Centos6, x64 server and I noticed that when using email templates to compose an email, the variables do not get replaced by the actual values; the receiver always gets something like(this is displayed on the CRM as well):
"
Hi $contact_first_name $contact_last_name,
We’ve received your case $acase_name (# $acase_case_number) on $acase_date_entered
Status $acase_status
Reference $acase_case_number
Description $acase_description
"
I enabled debug logging and noticed these 2 errors but I do not know what to do to fix ithem:
Sun Oct 19 01:52:22 2014 [9043][1][ERROR] Unable to load related bean by id
Sun Oct 19 01:52:22 2014 [9043][1][WARN] CaseUpdatesHook: saveEmailUpdate: Not a create case or wrong parent type
I made another fresh installation and I got exactly the same error.
On the other hand I noticed that at Inbound Email Queue which has
Create Case from Email: ON
New Case Auto-Reply Template: OFF
Auto-Reply Template: OFF
there are still automatic emails triggered to sender(in correct format!); But if I enable “New Case Auto-Reply Template”(and select Case Create template) the sender gets 2 emails: one in correct format and another one as in the problem described above.
I have the same problem here with “cases”. I created a test case and sent an email from the email module using a case template.
The mail arrives without the variables being substituted.
Sending an email from the emails module, the CRM will not know which record to reference. These variables will work if the email is sent via AOW(Workflow) for example.
But why can I select a specific case? I select that the E-Mail is linked to “cases” and then select the specific case. The CRM should then know which case to reference.
So I tried using $contact_first_name instead of $lead_first_name is it was correctly expanded. There is more than meets the eye because not all variables are expanded. For instance $lead_assigned_user_name and $contact_assigned_user_name are not expanded at all despite the fact that both the lead and the contact are assigned to Administrator.
As this appears to be different from your problem, I’ll start a new thread.
There is a line of code that determines which modules will be expanded for a email variables in modules/Emails/Emails.php around line 500. I added the Cases line below.
Is anyone able to solve this problem? I also have this problem with SuiteCRM 7.2 and i don’t know how to check what’s wrong with this. Everything was normal but then suddenly it goes wrong like nothing filled in the variable name
I’m having this same issue – the variables populate if I setup a workflow to trigger an email when a field updates, however if I manually create an email under “activities” in the module – even though the email is related correctly to that particular record — , the variables won’t populate when I send the email out (the email is received, just no variable substitution).
any help, general direction would be most appreciated –
Can some of the CRM gurus help the novices in this group. I have an email template and try to populate the following from the Opportunities table.My template looks like this.
“We are writing in reference to $opportunity_name. We are willing to submit our tender number $opportunity_quotenumber_c for the same. If you have any questions, please contact us.”
I was expecting that the fields will get populated with the information from the Opportunities table, but it does not happen. If somebody can help, I will be greatful.
I’ve tried Nelem’s fix from a few posts above and it did not work for me.
I’ve configured an inbound email with:
Import Emails automatically: yes
Create Case from Email: yes
Distribution: Round Robin
New Case Auto-Reply Template: MyTemplate
The case number variable gets replaced in the subject, but not in the body of the email…
Seeing same problem in Leads module, when sending a single email from a lead record using an email template, or adding variables during email composition.
-> Email goes out, but variables are not replaced with dynamic data!
e.g. $lead_first_name is shown in Email instead of the data from related lead record.
This works for Emails sent out of a workflow though.