We understand that your ecommerce site is crucial to the success of your business, from time to time issues and questions can arise and you need to have the assurance there will be someone on hand to help resolve these in a timely fashion so you can spend your time driving your own business forward.

So if you are looking for faster responses to your questions or would like the assurance there is someone on hand for you to contact, fear not we have a number of paid support options that are available to you that can give your organisation the peace of mind knowing a member from the Cart Viper team will always be available to assist!

Purchase a Support Plan

Community Support

HomeHomeIssues and Supp...Issues and Supp...Templates & UITemplates & UICustom Email TokenCustom Email Token
Previous
 
Next
New Post
11/28/2013 10:37 PM
 

Hi Team,

We are using the User Pricing feature within CV, what we do is ask the customer to set (or we edit) a users display name to be their usual "Customer Code". In our order confirmation email we would like to include the "Customer Code" i.e the display name within the email.

What do you advise would be the best way to approach this? Is this a scenario where a skin object could be used or is this something we would need you to to set up for us? Is there a way to create custom email tokens for this kind of scenario?

Thanks!

edit* and/or being able to achieve the same through http post using the Order Notification Callback would be ideal

 
New Post
11/29/2013 11:35 AM
 

Hi,

A skinobject would not work in this scenario, if you wanted a token [DISPLAYNAME] we would need to add it for you. However there is a possible workaround, if you use the singlepage checkout. Go to the Cart Viper my account module settings there is the option to add "custom checkout fields". 

So you could add one requesting the customer enters their "customer code", then you can then use the token [CUSTOMFIELD1] in the order confirmation email to get this value.

Note you can request up to 3 custom fields during the checkout each with their own token:

[CUSTOMFIELD1]
[CUSTOMFIELD2]
[CUSTOMFIELD3]

It is also possible to link them to dnn profile fields so they will auto-populate.

Thanks
Nigel.

 
New Post
12/2/2013 12:28 AM
 

Thanks Nigel,

Sounds like using custom field and linking it to the display name is the way to go - once added will this field automatically be included in the XML when using HTTP Post?

Thanks

 
New Post
12/2/2013 12:58 PM
 

Hi,

No they wont be automatically included in the post, however you could reference our CartViper.Modules.Store.dll in the project. Then you could use the OrderController to look up the order via the order ID , once found the custom checkout fields are stored in the property CustomCheckoutProperties on the OrderInfo object.

Note you will need to copy all the dotnetnuke sections from your website web.config file to the notification web.config file so we can access the database and load the config for all the various other items.

Thanks
Nigel.

 
New Post
3/28/2014 12:32 AM
 

Hi Nigel,

Is the text that is used when the custom field tokens are output into order emails in one of the resource files? I notice that by default this seems to output something along the lines of  [CUSTOMFIELD1] :  [CUSTOMFIELD1VALUE]

So in the order email at the moment I have a custom field for Order Number and my email reads "Thank you for your order, your order number is ORDER NUMBER : 12345"

I haven't been able to find which resource file controls this as I would like to change the wording around this slightly if possible

I am using single page checkout if that makes a difference

Thanks

 
Previous
 
Next
HomeHomeIssues and Supp...Issues and Supp...Templates & UITemplates & UICustom Email TokenCustom Email Token


 

We use cookies on our website to improve our service to you, by continuing you agree to our use of cookies. However you are able to update your settings at any time.

Cookie Policy

A cookie, also known as an HTTP cookie, web cookie, or browser cookie, is a piece of data stored by a website within a browser, and then subsequently sent back to the same website by the browser. Cookies were designed to be a reliable mechanism for websites to remember things that a browser had done there in the past, which can include having clicked particular buttons, logging in, or having read pages on that site months or years ago.

Strictly Necessary Cookies

These cookies cannot be disabled

These cookies are necessary for the website to function and cannot be switched off. They are normally set in response to your interactions on the website e.g. logging in etc.

Cookies:
  • .ASPXANONYMOUS
  • .DOTNETNUKE
  • __RequestVerificationToken
  • authentication
  • CV_Portal
  • CV_Store_Portal_Cart_0
  • CV_USER
  • dnn_IsMobile
  • language
  • LastPageId
  • NADevGDPRCookieConsent_portal_0
  • userBrowsingCookie

Performance Cookies

These cookies allow us to monitor traffic to our website so we can improve the performance and content of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited or how you navigated around our website.

Cookies:
  • _ga
  • _gat
  • _gid

Functional Cookies

These cookies enable the website to provide enhanced functionality and content. They may be set by the website or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

Cookies:

Currently we are not utilizing these types of cookies on our site.

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.

Cookies:

Currently we are not utilizing these types of cookies on our site.

Feedback