Netsuite Saved Search not matching with Domo connector dataset

Netsuite Saved Searches work by applying filters and displaying result fields on a particular Netsuite object. In our case, transactions. The expectation when using Domo's Netsuite connector to import a saved search using a saved search ID is that the number of records would match. Has anyone experienced the number of records not matching between Netsuite and Domo? We have played around with keeping duplicate rows, but we have not been able to have our saved search match. This occurs on a sporadic basis (i.e. only some Saved Searches exhibit this behavior on our instance).
Comments
-
I've noticed this can happen when the Domo integration user has different permissions than the business user. They may both be able to run the search, but the records available can appear differently. Might be worth double-checking that!
0
Categories
- All Categories
- Product Ideas
- 2.1K Ideas Exchange
- Connect
- 1.3K Connectors
- 308 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 662 Datasets
- 118 SQL DataFlows
- 2.2K Magic ETL
- 821 Beast Mode
- Visualize
- 2.6K Charting
- 85 App Studio
- 46 Variables
- Automate
- 193 Apps
- 483 APIs & Domo Developer
- 85 Workflows
- 23 Code Engine
- AI and Machine Learning
- 23 AI Chat
- 4 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 116 Domo Everywhere
- 283 Scheduled Reports
- 11 Software Integrations
- Manage
- 142 Governance & Security
- 11 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 115 Community Announcements
- 5K Archive