@suitemike In that case, I think you'd need to have separate restricted entry forms for the various roles that show or hide the Price Levels sublist

I tried hiding the field but then the rate field doesn’t work properly

like if I hide the field it removes the function of the field

hmmm....let me go into an account that actually has this and look

Oh wait, you want to disable price level on the transaction?

what transaction type are you looking at?

yep sales order

What's the use case? You want them to not be able to change the price level? Or they really are not even allowed to see the name of the price level?

So, I just spent four hours trying to get a saved search working properly, and I accidentally figured it out, but I'm not sure why what I did worked so I'm looking for a clue as to how what I did fixed things. So I was trying to get a sum of the total value of item fulfillments, with each item fulfillment record having a custom field containing this monetary value. Unfortunately, the value of the custom field was being multiplied by the number of lot numbers in the item inventory detail. So I set about dividing by setting a Formula (Currency) Sum using

{custbody_cntm_fulfill_amount}/COUNT({inventorydetail.inventorynumber})

, but this threw the dreaded Unexpected Error. To make sure I didn't fat-finger the custom field name, I commented out the division, like so:

{custbody_cntm_fulfill_amount}/*/COUNT({inventorydetail.inventorynumber})*/

, and voilà, it worked. Why did commenting the division out cause the correct behavior? Thanks!

Is there a reason that some bundles are available in a production account but not a sandbox account?

@James Morris they don’t want order takers to have the ability to change price levels, we set the price levels at the customer level any changes need to be approved first

@suitemike buddy set the field to inline text or disable in the role specific form make sure to make that form preferred for that role. Also remove the custom form field in that form so they cannot change the form.

@Sam-I-Am That field doesn't give the option to set as disabled. Only remove or show

line level field I guess

default line level field does not have this option

there might be another convoluted way, create a custom line level field source it from the item>price level, set to inline or disabled. Hide the default price level - just a thought dude may work out without scripting

@suitemike see above

i’ll try it out but if it doesn’t work we’ll just have to script it

i try to leaving scripting as a last resort

@suitemike Not great, but security by obscurity? Can you move Price Level all the way to the right? Make it the last field.

Trying to update existing group price levels on customers but everytime I use 'update' or 'add or update' I get back a message that says the price group must be unique.. So instead I have to grab all the current group pricing and re-upload it with the new ones. Anyone had this problem too?

I am using a saved search to return all Sales Orders that have no back-ordered items in them. I finally got the search to work as expected, but when I tried to run it through SuiteTalk I found out that I cannot have any "summary" columns in a saved search. I have spent a lot of time on this, and could really use a tip on how to get these orders in a way that will work using SuiteTalk. The only data I actually need returned is the top 1 Internal Id of the oldest Sales Order with no back-ordered items that are in a specific Location. Thanks for any tips!

@michoel did you end up going BigCommerce?

Yep

which connector?

We looked at quite a few, but ended up writing our own integration. The out of the box (Celigo, FarApp, Folio3 etc.) ones weren't flexible enough for our needs, and the iPaaS options (Boomi, Jitterbit) were above budget

oh wow, ok!

not to go into too much detail, but what were the top line issues where celigo/farapp wasn’t flexible enough?

One of the big ones was mapping NetSuite's pricing matrix to BigCommerce's. BC only supports a single price list per customer, but we needed to handle price levels as well as pricing on the customer level

bugger, there goes that idea straight away