NetSuite Analytics troubleshooting
Q. My NetSuite Analytics pipeline is stuck in a pending state. What should I do?
A. This can occur due to a known limitation in the NetSuite SuiteAnalytics Connect platform. The oa_fkeys system table — used to automatically detect primary and foreign keys — may become unresponsive in NetSuite2.com environments with complex schemas. When this happens, the Data Flow hangs indefinitely in a pending state.
NetSuite acknowledges this behavior in SuiteAnswers (Answer IDs 44721 and 44724):
Due to the complexity of the NetSuite2.com schema, the oa_fkeys table may return inaccurate information about foreign keys for the NetSuite2.com data source. Some foreign keys may be missing or incorrectly identified as such. Consider the information about foreign keys for NetSuite2.com as a reference only.
To resolve this issue:
- Cancel the stuck Data Flow run.
- Open the Data Flow settings and go to Tables Definitions.
- Disable the Auto Detect Table Relationships checkbox.
- Go to the Schema tab and manually select the primary key for each table.
- Save the Data Flow and re-run it manually, or wait for the scheduler to trigger the next run.
After you save a manually selected primary key, a Reset button appears next to the field. This confirms that the key is stored on the Boomi side and no longer depends on the NetSuite metadata service.
Primary key requirements by loading mode
The importance of defining a primary key depends on the loading mode you use:
| Loading mode | Primary key required | Notes |
|---|---|---|
| Upsert/Merge | Yes | Primary keys are used to match existing records and determine whether to update or insert. Without correct primary keys, you may get duplicate records or missed updates. |
| Overwrite | No | The target table is fully replaced on every run. |
| Append | No | Records are appended without deduplication logic. |
