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
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 306 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 787 Beast Mode
- 78 App Studio
- 43 Variables
- 743 Automate
- 187 Apps
- 474 APIs & Domo Developer
- 67 Workflows
- 15 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive