Discussions
It’s that time of the year again! As we embrace the holiday cheer, we want to share an important announcement regarding our holiday schedule. Our dedicated team of NetSuite Support Gurus will be taking a short break to recharge during the holidays, from December 24, 2024, to January 1, 2025. We’ll be back in full swing, ready to assist you on January 2nd. During the break, feel free to explore the wealth of NetSuite resources on our platform.
As we celebrate the season's joys, we are incredibly grateful for your ongoing support and engagement. Have a fantastic holiday break, and let's gear up for an incredible 2025!
Here are some examples to get your creative juices flowing.
"Did I pay vendor John Doe last month?"
"Take me to my largest sales order for this month."
"What invoices haven't been paid yet?"
Trying to understand advantages of jobs vs sub-customer and access limitations
I'm trying to decide on the best approach for handling customers with multiple implementations of my clients product. In some cases they are evals or betas, in other cases they are multiple installations using for different reasons.
I see that Jobs may work for betas and evals since these have a beginning and an end to them, whereas multiple installations are permanent and may make more sense to be treated as sub-customer.
I like the fact that I can assign different contacts access to the customer center using the sub-customer record approach. This would be great for evals where I may want to setup a Eval Customer Center role to handle evals separately from the main customer support cases (eval cases route to sales, production cases route to support).