Tom Dalton · Owner · Silver Medal

The PDF guide that you linked to says "January 28, 2014" on the front page. Reference Checkout 2.02.0 was Released on February 5th 2014 (based on the date that this thread was started). So, would that PDF still be current to version 2.02.0? Do you have something LIKE THIS, but for reference checkout 2.02.0 non-beta?

Thanks again Mariano. I wish that NetSuite made some "code generation tools" for the Reference checkout and Reference my account. If 3rd party developers can do it, then why can't or why won't NetSuite?? For instance, see this NetSuite developer's video here... http://www.mvlwebtech.com/my-orders.html The 3rd video in the…

It says: Bundle Release Process An improved Bundle release process allows for multiple versions of the bundle to be displayed in a Customer's account. For example, customers will be able to install Checkout 2.02.0 and Checkout 2.01.0 into one account. Checkout 2.01.0 is now a shared bundle, but available for anyone who…

Yes. We're on mac. I have Reference Checkout turned off in our account right now. Do you know what file that the "textarea {width: XXXpx; height: XXXem;}" would be in?

This release did not address the Shipping + Handling Issue. We currently do not honor the Site Setting. We know this and have filed a defect. That said, because you have full access to the code you should be able to concatenate the values and put everything together on one line. I will reach out to our DEV team and see if…

if you don't have a sandbox account I strongly recommend you get one - very helpful in development without breaking production OK, sandbox = helpful. Chauffeur and butler also = helpful and also come highly recommended by those that have them. In other words, sure.. but the price is simply wrong IMHO. -Tom

I wonder why the Reference Checkout and other Reference my account can't pull prefs from the WebStore preference areas. For instance, couldn't they use the area for google analytics tracking code in the webstore prefs and then have a variable in the reference checkout that inserts the code from the prefs into the reference…

Am I the only one with the "Reference Checkout" formatting issues or the only one trying to use "Reference Checkout"? Is there a sample "Wolfe Electronics" NetSuite site that shows how the checkout "should" look? Then we can determine if the issue is unique to our account or another "as designed" issue. Also, is there a…

Thanks, you did the impossible (according to NS support). I'll try the fix tonight. What input do you have on my previous post (post #14)?

Before I test, did it fix the shipping problem from Reference Checkout v2.0? Can we now display just one combined number for shipping and handling (as the field help in NetSuite indicates is expected behavior)? If it didn't fix the issue ...did it at least open up a new possibility for a work-around. T

I got it to work. I'll post the details if anybody needs them. I found two more issues with reference checkout. #1: It ignores our site settings to combine shipping and handling into one number. #2: When it encounters an issue with an order, it shows a generic error. For example, we have a $5 minimum. I tried checking out…

More road blocks with the instructions. I assume every instance of "custom_message" was to be replaced with our custom field's ID. Lets say our NetSuite field ID is xxxxx. So, when we see "#custom_message" in the NS code, do we leave the # and make it "#xxxxx"?

We had it on our site. We had check-out errors. Not everyone had errors, but enough customers complained so we turned it off. We opened a NS support case on 12-11-13. NetSuite asked one question on that day and hasn't communicated with us since then. So, you might not see many (or any) examples until the bugs are worked…

In the cart, the quantity being ordered is barely showing. Maybe the top 1/4 of the number is visible. see image... The image above is from the shopping cart. The left image was from Chrome. That chopped off number also appeared exactly the same way in Safari. It looked like the right side image when viewed in Firefox (all…

Thinking on the forced separation of Shipping and Handling in the Reference cart 2.0. I wonder why a user can't just edit the JS config/template to display a custom shipping field? EG: {Custom_Combined_shipping} = {altshippingcost}+{althandlingcost} ..and then make the JS show the custom field and hide the default…

I found two more issues with reference checkout. #1: It ignores our site settings to combine shipping and handling into one number. #2: When it encounters an issue with an order, it shows a generic error. The customers have NO IDEA what the problem is! For example, we have a $5 minimum. I tried checking out with a test…

I wish that NetSuite made some "code generation tools" for the Reference checkout and Reference my account. If 3rd party developers can do it, then why can't or why won't NetSuite?? For instance, see this NetSuite developer's video here... http://www.mvlwebtech.com/my-orders.html The 3rd video in the bottom right corner…

If the reference cart behavior disobeys NS field instructions, then why is the fix called an "enhancement request"?

NetSuite, can you update the instructions for adding a custom entry field (Like "Customer Comments")? The instructions found in SuiteAnswers (Answer Id: 24969) are NOT for Reference Cart v2.0? Or, can you post the instructions in here. -T

Dadabase, Do you need shipping and handling to display as one value (titled:"Shipping") in the checkout? If so, then there is another BUG blocking you from using he reference checkout.

NS answered in regards to "is there a work-around for the forced cart separation of shipping and handling" and they said... there is no alternate solution available This would not be classified as a Defect since there is no breakage in the functionality and it is working as designed. So, NetSuite shipping had/has a setting…

The "generic error" problem was a NetSuite bug. The workaround/fix was to go to "Setup > Site Builder > Customize Text" and copying the standard warning massages over into the corresponding custom message area. So, in the case of "Your order is under our $5 minimum"... we copied the NetSuite default message for that error…

Bump... Has anyone else tested the reference checkout v2.0 and if so... did a percent of your customers get the "Internal Errors" message during checkout? I opened a case with NetSuite and it seems to be moving slowly. -Tom

Apparently it doesn't pull analytics settings from the default NetSuite Google analytics settings area. Looks like we have to edit Javascript files to make Google analytics work again. Seems like a big step back in configurability (as far as user friendliness goes). The old system wasn't intuitive. Now it appears to be…

Nice. I'm excited. So, this is the non-beta version? It works with PayPal? -Tom

Mariano, before we test v.2.0.1, did they fix the shipping problem from Reference Checkout v2.0? Can we now display just one combined number for shipping and handling (as the field help in NetSuite indicates is expected behavior)?

NetSuite, can you tell us when the reference checkout issues will be fixed?

The reference checkout seems to be a step backwards in a number of ways. The biggest issue is usability (requires a programer and a bit of arcane knowledge to do anything). This shipping issue is just another flaw. Not having the ability to combine shipping and handling (which was an easy setting in the old cart) is a deal…

Found the custom transaction field answer here... https://netsuite.custhelp.com/app/answers/detail/a_id/24969/kw/custom%20transaction%20field%20reference%20checkout BUT, it had this note...."This article applies to the Reference Cart & One Page Checkout bundle prior to v 2.0" It references files not in v2.0. NetSuite, can…

Go to Setup > Company > Enable features. Click the Web Presence subtab. If you don't see "SuiteCommerce Advanced" as an option... then, you don't have "SuiteCommerce Advanced" and you either have SiteBuilder or no ecom.