This did it... when {transactionlines.nextlinks.linktype} like '%Drop%' then 'drop ship' else 'Our Warehouse' end

I was doing this as a criteria in an analytics dataset. When I tried your idea, I got "Your formula contains a reference to an inaccessible field applyinglinktype". It is a formula field in the dataset.

We don't use special orders. Just regular drop-ship POs. How would you put it into a formula field to make a drop-ship flag... like: Case when {Applying Link Type} is 'Purchase Order' then 'drop ship' else 'Our Warehouse' end Obviously that isn't right, but what would be?

Lastly, is this happening across all users? .. Yes

Yes, the template is blank.

I confirm that I'm referring to font size of standard NetSuite emails. The emails we manually type to customers. What we're typing is very small. On the customer's end it might look bigger, but on our end we have difficulty reading what we're typing.

Receive Customer Replies in Case List Only WAS enabled. Any other ideas? Best Regards, Tom

I think it was a coincidence that made me think {custitem_weight} was being used. Like I changed the weight up +1 lb to test if it was the active field and then ran a test in the web store. At that same item UPS rates were adjusted upwards by UPS. So, it came back with a higher number and I made the wrong assumption that…

That wouldn't be a good Enhancement request to add us to unless it read "Enable capability to default a MAXIMUM package weight for the default package used in item fulfillments as it is currently hard coded at 150 lbs which gets hit with hefty UPS oversized fees".

I accepted the answer too soon. I go to Setup > Accounting > Shipping > Preferences > Rates > UPS Rates and I try all four types of UPS rates and they have ZERO impact on the rates displayed in our web store. I think those are maybe only for what is printed on the UPS label if you use an integrated label printed right out…

thanks So that you know the impact issue, we (and I assume everybody) gets hit with all kinds of upcharge fees from UPS when a UPS box is overweight. It used to be that a box of 70 lbs or more was overweight and got a +$70 fee. In the last year it was lowered and boxes of 50 lbs or more get a +$70 fee. So, if we had to use…

NetSuite help says: Note If you do not enter a maximum number of items, the package type maximum number of items is assumed to be unlimited until the total weight is equal to or greater than 150 lbs. So, where can we change the 150 lbs. max for one package to a lower number?

I know how to add a discount to a shipping item. UPS shows retail UPS ground costs (on our bill) like this... $27.09 UPS Ground Shipping cost <-- *It WAS pulling this into NetSuite for us to apply a discount to +$4.45 - Residential Surcharge +$18 - Length + Girth Surcharge +$3 - Peak Surcharge +$4.07- Fuel Surcharge TOTAL:…

I had already created a template and picked type = case. It had no impact on case responses. How do you specify that a specific email template be used on all case responses? You keep showing me how to apply templates to regular emailed messages sent out of NetSuite. We already know how to do that. In cases, you reply to…

How do you specify that a specific email template be used on all case responses? We already use the setting "Home > Set Preferences > General> Add Signature To Messages" and we have no signatures in our case responses.

I don't have a scriptable template for case responses

This worked.... We already had {custbodyshiptophone} on our sales orders and fulfilments and it lacked the need format. It takes the phone number from the shipping address and if blank it takes the main phone number from the customer record. Then our new custom phone field uses: CASE WHEN {custbodyshiptophone} like '1%'…

I saw your sample fix. Our packing slip has the columns "Item Number", "Description", "Options", "Quantity". We don't use the Item field as a column on packing slips. Adding it could be done, but in my test the little space wasn't enough to make the members obvious. Our names were too long and wrapped around and there…

I tried all three of these in Excel on a mac... UTF-8 CSV Comma Separated Values CSV MS-Dos Comma Separated CSV All three gave the same error

I sent you the file by private message

I did it via (2) Vendor Record > Financial tab > Items subtab > Import Price List button

We do use the "Basic" and not the Advanced packing slip form. Any idea why it isn't indenting kit components?

I'm trying to import a price list. NetSuite shows this message.. You entered "CPL-3" into a field where a numeric value was expected. Please go back and change this value to a number. The "CPL-3" is the second item's part number. Is it choking on the "-"? Is there a workaround?

We use a customized packing slip form. Two visual solutions would be like this... Bicycle X ... x1 Steering Wheel ... x1 Frame x1 Wheel x2 See how the kit components above are inset? Or, this would also work... Bicycle X ... x1 ...Steering Wheel ... x1 ...Frame x1 ...Wheel x2

We do use a CDN. We use Cloudflare. We are on SiteBuilder. I did make a NS case. It didn't really give us a great plan for reducing server response times..

We consistently get 2100 to 2400 ms server response times. Google says it should be < 200ms

So we were down for 8 hours and NetSuite didn't log the outage? or, Pingdom is reporting fake statistics? I will say that it says we were down from roughly 2pm to 10pm on Saturday. We typically get a dozen orders in that time period (through our WebStore) and this past Saturday during that time period... we got zero orders…

The web store has also be super slow. Look at that 2365 ms response time. some general rules about server response time that I found online: Quicker than 100ms is excellent. 100–200ms is good. Google PageSpeed Insights recommends keeping your SRT under 200ms. 200ms–1 second is acceptable, but there’s room for improvement.…

It is a glitch with Avalara. It is a NS field that can't be mass updated that specifies the tax item in each customer record. We caught most of them with exports/imports... but only updated customers from the past 5 years. So, when a very old customer orders and the tax item isn't set to AvaTax... it causes this error with…

I also made a support case with NetSuite