I hadn't tried submitting a case because I don't know whether it's a defect or not, and we have the lowest-level support tier, which means the only kind of support cases we can submit are defect cases, if I understand correctly. That being said, I'll try submitting a case since it is possibly a defect.

What should I do if I do not want SuiteCommerce to create a new lead? When someone enters an existing Lead/Prospect/Customer's email address in registration, I want it to grant access to that entity. I do not want it to create a duplicate lead. How do I get it to behave in that useful way? We have many existing customers,…

Answer: Option A. Manage Escalation Assignment. You can get to that page by this navigation path: Setup > Support > Escalation Management > Manage Escalation Assignment

In our case, checkout page cannot load for a customer that has an empty "Terms" field, so filling that out fixed the problem for us.

Found out in our case that the logged in customer having an empty "Terms" field causes the checkout page(s) to be unable to load.

I'm working on getting the Kit items to be extracted onto their own lines and the Kit item deleted, when the Sales Order is being created, but once I get this working, I will still have to solve the remaining problem: Inventory Items appearing on Sales Orders created by SuiteCommerce do not get a DropShip/SpecOrd link on…

If there's any way to get the items that are in the kit to have Drop Ship/Spec Ord links in the Sales Order created by the SuiteCommerce checkout process, then that will solve our problem.

We are using SuiteCommerce Standard 2023.1.2 (when I went to look at the version number in our bundle list, I saw that an update was available, so I'm installing 2023.1.3 now). The drop ship links appear on Sales Orders that are not created via the SuiteCommerce checkout's Place Order action. They just don't appear on…

I am thinking of having the Scriptable Cart user event script add the Kit components to the Order as it's being created when the user Places their Order, and then delete the Kit. This will need to be done in a way that preserves the price the customer is paying for the original Order in its Kitted form. There is another…

We really only need to drop ship the items that are contained in the Kit. We would use Item Groups instead, but SuiteCommerce doesn't allow those to be displayed in the web store. So can we instead make the individual components have their own line item in the Sales Order as is possible to do in Item Groups? That way we…

In its current state, I was able to use CMS to add this HTML to every page, including MyAccount and Checkout pages. When we started this project, it was only possible to do this on Shopping pages, which necessitated the extension to enable injection of more HTML into every page that needed it. But now that CMS HTML…

Anyway with that support case trouble behind us, back to the original issue: Max Quantity can be bypassed by adding to your cart, logging out, adding to the guest cart, then logging back in, thereby combining the quantities of the same Item together, even past the max quantity. This was determined to NOT be a defect by the…

Also note that if you add a custom field to the Field Sets and/or the search Facets of a SuiteCommerce web site, then that will also cause the custom field configurations to become locked until you remove them from the fieldsets and facets of all web sites.

Outcomes: Inputting the Steps to Reproduce with the text I had for that, is what caused the error to occur. This could be worked around by changing to another browser, which leads us to believe it is either a browser or caching issue. It could also be worked around by omitting the Steps to Reproduce the problem from the…

Yes, I finally managed to create a support case, but only after I left the Steps to Reproduce blank. When I filled it in with all the steps needed to encounter the problem with maximum quantity not being enforced, then the form fails to submit and generates the error instead. So what I did was I submitted a Case with the…

I tried to file a case by using the "Contact Support" button in SuiteAnswers, then the "Create a Support Case" link on the right sidebar, but 3 attempts at filling out the entire Support Case questionnaire all resulted in an unknown error preventing me from submitting it. This error happens to me most of the time when I…

I don't see anything in there that would make the link open in a new tab, but I think you all have answered my question which was whether anything in the multi-column links can be used to make the links open in a new tab. It looks like nothing in that configuration area does that, so I'll continue using my injected…

This is perfect and exactly what I needed! Thank you.

So is there a SuiteCommerce Standard way of configuration that will hide those transaction line fields in SuiteCommerce, or do I need to try something else like a workflow to hide them based on condition of logged in user's role?

I just added two new custom Transaction Line fields, "Troubleshooting A" and "Troubleshooting B". Troubleshooting A is a non-stored decimal field with default value 12. Troubleshooting B is a stored decimal field with default value 24. I see both a 12 and a 24 on a new salesorder I placed, but I don't know if the new…

I see in SuiteAnswer #74826 that the "Hidden" checkbox only works on Site Builder websites, and ours is a SuiteCommerce Standard site. However, I cannot use the advice in this article on how to actually hide the fields because those Configuration menus it mentions are only available in SuiteCommerce Advanced. So anyway,…

I'm currently just trying to hide one of the transaction line columns "Total Gal Beer per line" which I have highlighted by dragging the mouse over it. Once I get that hidden I will apply the same treatment to the other unwanted fields listed on each item in the online purchase (Sales Order). Here's the field configuration…

Well the SuiteAnswer article in the recent comment was the same one mentioned before, which doesn't actually say anything about how to use data-target (though that was addressed in another comment), or how to make SuiteCommerce theme footer links open to a new browser tab. It just says to use the URL. Is there a hash or…

I tried checking the Custom Transaction Line Column's "Store Item" checkbox AND the "Hidden" checkbox next to it, but this didn't hide it; it just moved the field to the top of the list that appears on each line item on the Purchase Details page. Unchecking "Store Item" makes it appear somewhere further down the list…

OK so it sounds like data-target is NOT for setting the "target" attribute on the <a> tag of the link, so I should keep my script since it will be needed to make the links open in a separate tab, but modify it to select the appropriate links based on something other than data-target.

To work around this not working the way I am guessing it should, I added the following Javascript into every page of our SuiteCommerce site: $(".footer-column-link[data-target]:not(.targetbeenset)").each(function(){ $(this).addClass("targetbeenset").attr("target", $(this).data("target")); });

Thank you for the links. I'm familiar with that SuiteAnswer though, which is why I came here. That SuiteAnswer does not explain what the Data-Target is or what it is supposed to do, or how to make sure it works. Data-Target: Select a data-target. That's all the information in the SuiteAnswer regarding Data-Target.

I'll be able to try the CMS approach soon, but the Config field approach is actually by far the fastest to iterate on (as fast as updating a Suitelet script file), so it's made sense at this point in development to keep doing it that way until we don't anticipate any more time-sensitive changes needing to be made.

I tried CMS but at the time, it wouldn't let me do anything with the checkout pages, and I needed to be able to alter every area: Shopping, Checkout, and MyAccount. Has that changed?

I know it's not best practice, but development iteration is extremely slow doing it the right way, partly because we never got local testing to work. So are you saying that a configuration field longer than 300 characters could exceed URI max length, or the JSON file as a whole? If it's the file as a whole, I think I'd…