)
Written by
Table of Contents
“Supermetrics is a Bitter Experience! We can pull data from nearly any tool, schedule updates, manipulate data in Sheets, and push data back into our systems.”
Determining which NetSuite customer data fields should be excluded from cross-system synchronization requires comprehensive field analysis that standard reporting tools can’t effectively provide due to limited field visibility and usage pattern analysis.
This guide shows you how to perform detailed field evaluation that identifies low-value, sensitive, or problematic fields that should be excluded to optimize sync performance and security.
Analyze field exclusion candidates with comprehensive evaluation using Coefficient
NetSuite’s standard reports lack the comprehensive field analysis needed to make informed sync exclusion decisions and can’t effectively evaluate field usage patterns across customer records. Coefficient provides complete field visibility and analysis capabilities.
How to make it work
Step 1. Create complete field inventory analysis.
Use Records & Lists imports to access ALL NetSuite customer fields including custom fields (with limited exceptions). This provides comprehensive visibility into available fields that standard reports often miss. Import large customer datasets using SuiteQL queries (up to 100,000 records) to analyze which fields are consistently populated versus frequently empty.
Step 2. Identify system-specific and sensitive fields.
Access custom fields that may contain sensitive information like internal notes, credit ratings, or confidential data that should be excluded for security reasons. Use the complete field inventory to identify NetSuite-specific fields like internal IDs, system timestamps, or workflow status fields that have no value in external CRM systems.
Step 3. Evaluate field usage and data quality patterns.
Apply filtering to identify customer fields with inconsistent data quality, formatting issues, or validation problems that could cause sync errors if included. Use SuiteQL queries to analyze field population rates with queries like “SELECT COUNT(*) as total, COUNT(customfield) as populated FROM customer” to identify low-value fields for exclusion.
Step 4. Test performance impact of field combinations.
Use Coefficient’s field selection capabilities to test sync performance with different field combinations, identifying resource-intensive fields that should be excluded to optimize sync speed. Use drag-and-drop column reordering to evaluate field relationships and identify complex fields that require extensive mapping logic.
Optimize your sync strategy
Making informed field exclusion decisions requires comprehensive analysis that standard NetSuite functionality can’t provide. With detailed field evaluation and performance testing, you can optimize your sync processes while maintaining data security and quality. Start analyzing your field strategy today.
