Analysis of NetSuite Customer Sales Team Update Method

If you want to isolate the sales team from customer data in NetSuite, the method used is to " define the sales team on the customer and perform Employee Restrictions on the access roles of the sales team members ."

Among them, we have published several articles on the topic of Employee Restrictions in the past, which you can refer to.

NetSuite Data Isolation Employee Restrictions Function_NetSuite Knowledge Club's Blog-CSDN Blog We know that data isolation is actually a problem that every project will face. On a larger scale, sometimes customers will ask for data isolation between different Subsidiaries; From a small perspective, different Employees under the same role may also need data isolation. The actual case we encountered recently is that different warehouse managers with the same role want to realize that after "my" inventory documents are saved, "others" cannot modify or take the next step. In this case, without using workflow Can we achieve it next time? https://blog.csdn.net/remottshanghai/article/details/127691371 A small test of the Employee Restrictions function of data isolation_Testing data isolation_Vicky-Min's Blog-CSDN Blog The "small pit" of the Employee Restrictions function in NetSuite, Have you ever encountered this? _Test data isolation https://blog.csdn.net/m0_60782905/article/details/127687912

Now, let’s talk about the four operations of “ defining the sales team on the customer ” and make a comparison.

The so-called "defining the sales team on the customer" means maintaining the "Sales Team" on the customer master data, and by binding the relationship between the customer and the Sales Rep, it is simple to realize that "a specific Sales Rep can only see specific customers" data. need.

The following will list four commonly used "customer-sales team" data maintenance methods.

Method 1: CSV Update – Sales Team Member

Create a multi-column Sales Rep CSV template.

During CSV Update, select "Overwrite sublist".

Establish the Mapping relationship of Sales Rep. Create mapping relationships for as many Sales Team sub-records as there are Sales Reps.

Method 2: CSV Update – Choose Team

Create a Sales Team and add Sales Rep to it.

During CSV Update, the Mapping object is the "Choose Team" field.

Method 3: Mass Update – Add new sales member

Select Add Sales Team Member in Mass Update for batch update.

Add a new Sales Rep to the target Customer.

Next is the regular operation of Mass Update. Select the update object and perform the update.

Note that the contribution of the new Sales Rep can only be 0 . This is a limitation of this method.

Method 4: Territory Update

The logic of this method is to assign customers to the corresponding Territory by establishing Territory. Then, update the Sales Team responsible for the corresponding Territory to the customer. Realize the association between Sales Rep and customers in Sales Team.

Therefore, first we must ensure that each customer has a corresponding Territory.

Territory is associated with Sales Team.

When a new Sales Rep joins the Sales Team, Territory Reassignment is performed.

Alternatively, update via "Reassign Using Territories" on the client.

The above is a list of the four methods. Let’s compare them:

 If you have any questions about NetSuite, please feel free to chat. Email: [email protected]

Guess you like

Origin blog.csdn.net/remottshanghai/article/details/132790603