We already have our customer's Order Information in MailChimp. It shows on the "E-Commerce" tab of each Contact in the List.
Is it possible to send out a campaign in MailChimp that includes this information?
For example, the customer's most recent Order Number?
Unfortunately, they don't yet have pre-built tool capable of pulling customer/order attributes into a Campaign's content, and at least currently adding any data like this you'd like to dynamically populate in Campaign would require adding any data directly to the list fields and using their merge tags.
http://kb.mailchimp.com/merge-tags/getting-started-with-merge-tags
They do offer Product centric dynamic content options, if that'd be in any way helpful.
Use Product Recommendation Content Blocks: http://kb.mailchimp.com/campaigns/content-blocks/use-product-recommendation-content-blocks?utm_source=mc-kb&utm_medium=kb-site&utm_campaign=eepurl
Merge tags for products: http://kb.mailchimp.com/merge-tags/all-the-merge-tags-cheat-sheet#Merge-Tags-for-Product-Recommendations
You can optionally store merge fields associated with each list recipient:
http://developer.mailchimp.com/documentation/mailchimp/reference/lists/merge-fields/
You could create a custom merge field for "MOSTRECENTORDER" for each customer, and then reference it within templates using |MOSTRECENTORDER|
Related
For complex TYPO3 project using fluidcontent I'm looking for a tool, which show me the followering informations:
which FCE exists
how often and on what pages are they in use
which partials are used
which flux form fields are used (with name and type)
diposit some meta informations, e.g. tags, description ...
How would be the smartest way to implement this library in a typo3 project?
My idea is, to develop an extension which read the fluidcontent templates and show the informations in a frontend plugin with examples. But i have no idea to read out the information like "used partials" or "used flux form fields".
Any ideas?
Thanks.
FCE's are just cType elements in the tt_content table. you can write a simple query to count the different cTypes, thus gives you a list with all the used FCE's on your site. you can know on witch page they are used because every tt_content entry has a pageUId
for the flux fields. you will have to create a function that fetch all content elements that uses flux and then parse all the flexform fields. note that flux can also store data in other fields then flexform xml.
you can create a basic extbase plugin for this to show it in the front or backend
I am working on a product catalog whose search is powered by GSA. Each product is a single entry, but may have many associated documents. As I see there is only one content node allowed in the feed XML. is there a way to add multiple files to same record in the feed xml? Any suggestions?
Your best bet is going be when submitting each record to the feed, is to extract the content of associated documents and add as additional meta-data before sending to the feed.
Alternately, you can submit each record and each document, with some meta-data that references the record it's associated with. When returning search results, you could customize the front-end results to display related content (records or other attached documents).
You can try additional document content into new metadata(1500 char limit) or document body.
I have a business requirement that execs are really wanting to see. In our lead and email templates we have a few of our products listed. The products themselves are pretty stable but the prices are of course subject to change.
I'm OK with hard coding the product name into email but I was hoping the price could be a slug that get's resolved.
We only have one price list so nothing to worry about there.
I see no way to get access to the product and or price list entities through the data field values dialog.
So my thought was to create the 2-4 fields in the lead and opportunity entities. Then create a background workflow that takes the price from the price list and sets those fields.
Then when an email is generated I can access those hidden fields as they will be available through the lead or opportunity entity.
Any thoughts, concerns, better approaches?
Unfortunately CRM's email template system is not capable of what you describe out of the box. As you have discovered it will only permit you to insert placeholders from, or assocated with, the primary entity. It won't let you insert fields from other entities. What you suggest as a workaround is possible but it's not an ideal solution as you'll have these 2-4 redundant fields on each record type that contain duplicated data from the price list.
If you have any experience with creating custom workflow activities using the SDK then the best solution here is to create a custom activity that accepts either an draft Email or Email template as a input parameter, instantiates the email if required, loads the price list data, and performs your own custom placeholder replacements.
I've done this on a few projects in order to pass multiple entity records into the template, or to insert complex tables into emails by loading data from relationships. See the screenshots below for an example of how I've configured the email template and dialog process to pass both an 'Account' and 'User' record into the email template.
I am working on an install of AspDotNetStoreFront (version 9.3.1.0). Currently, the company stores their own SKU's from their business system in the provided SKU field. They often use Manufacturer Part Number to store their vendors part number.
Example:
The above example is a variant of a product where we would like to store UPC information.
I searched the AspDotNetStoreFront manuals and could not find a recommended strategy for storing UPC codes. Its easy enough to add a field to the database and bulk import the data, however, an admin needs to be able to maintain them from within the stores user interface.
Is there a way to add a UPC field without modifying core ASPDNSF code and still allow users to maintain it from within the UI? Or do I have to use the SKU or MPN fields?
Update
I do see that there are 5 fields for "ExtensionData" that I could possibly use, but I don't see those fields as editable for Variants in the UI the way ExtensionData is for the Products themselves.
I don't think we have had customers who didn't use sku for their UPC code. In the event that you need to modify the table by adding another column, you can modify the admin to show this.
You should be ab able to edit entityEditProducts.aspx and entityEditProducts.aspx.cs to edit this in the admin area. You will just need to modify the sql scripts and the view.
I'm not sure if it's important enough for you to upgrade over, but version 9.4 added fields for UPC. From the 9.4 release notes (http://partners.vortx.com/t-summer2013releasenotes.aspx):
"Added new GTIN field to the product variant information for unique product identification. This new field holds up to 14 characters and can be used for EAN, UPC, ISBN, etc. This new field is included in WSI, Excel & XML Imports, and supported by DotFeed."
The GTIN field works for both variant and size/color.
you can use one of the 5 extension field given by default in the product table to store UPC code. By default it has also UI in edit product under Extension Data tab.
I am looking for a reliable way to get names of available data fields when creating or extending OpenOffice/LibreOffice report files.
I already do know many field names from the existing reports. I also can lookup the field names in the module definitions.
For example in the file addons\base\res\partner\partner.py I find a field list for the partner model:
class res_partner(osv.osv):
_columns = {
'name': fields.char('Name', size=128, required=True, select=True),
'date': fields.date('Date', select=1),
'title': fields.many2one('res.partner.title','Partner Form'),
'parent_id': fields.many2one('res.partner','Parent Partner'),
'child_ids': fields.one2many('res.partner', 'parent_id', 'Partner Ref.'),
# many more...
}
But this is only guessing and it is not complete. I would prefer to know the fields that are really available for any given report, and not guess.
There are also reports with data from linked tables, which is also important.
For instance if I print an invoice there should be also the delivery address and the billing address available for the report, including the name field of the contact.
(It is also possible to use the "OpenERP Report Designer" addon for OpenOffice. You find that solution here: How to get field lists using the OpenERP Report Designer Addon for OpenOffice / LibreOffice )
How can I find out the available fields - and the best would be to also know how to make more of the existing fields available to the reports, for example from linked tables.
This would maybe include how to find the function definition that provide the fields. And I guess making more fields avalable would best be done by extending the respective module and rewriting the function that delivers the data to the report.
Under the Administration menu, open Customization: Database Structure: Objects. (I'm using version 5.0. The menus have changed in 6.0, so you might have to hunt for it.) Search for the object you're interested in, and open the form. That will list all the fields, including related fields, inherited fields, and functional fields.
If you want to know how to extend a module and add related fields, read about the different types of fields. One type is the related field.