Celigo Field Mapping Explained: Dynamic, Static & Lookup Fields (Shopify to NetSuite)

Welcome back to the Celigo Integration Series! In this video, we break down one of the most important concepts in Celigo integrations — Field Mapping. When integrating two applications (here, Shopify and NetSuite), data flows from a source app to a destination app. But how does Celigo know which source field maps to which destination field? That's exactly what field mapping solves. 🤖 Key concepts covered: ✅ Understanding source (Shopify) and destination (NetSuite) fields in the mapping screen ✅ Dynamic Mapping — mapping fields like Customer ID, First Name & Last Name directly from Shopify input data ✅ How dynamic mappings auto-update when source data changes ✅ Static Mapping — assigning fixed values (e.g., a default email ID or customer type) regardless of source data ✅ Two ways to create static mappings: using double quotes vs. the hard-coded option via the gear icon ✅ Why static mapping is useful when NetSuite requires mandatory fields (like email) that Shopify data may not always provide ✅ Introduction to Lookup Fields — dynamic NetSuite search vs. static value-to-value lookups ✅ Setting up subsidiary and customer form as static/hard-coded values 📌 In this demo: We map a Shopify customer record (ID, first name, last name, email, phone, etc.) to the corresponding NetSuite customer fields, showing real-time previews as source data changes. 🔜 Coming up next: We go deeper into Lookup Fields and Nested JSON Mapping — since required fields aren't always at the root level of complex data structures. 🌐 Learn more: integscloud.com 📧 Contact: info@integscloud.com 👍 Like this video, subscribe to Integs Cloud, and follow us for more videos on Celigo, integrations, NetSuite, Shopify, and enterprise automation. #Celigo #CeligoIntegration #NetSuite #Shopify #FieldMapping #iPaaS #IntegrationPlatform #EnterpriseAutomation #NetSuiteConsulting #CeligoTutorial