We upgraded to NS 2023.1 last week and immediately noticed several SuiteAnalytics reports showing incomplete data. The saved searches with custom formulas aren’t displaying results correctly-some return partial data while others are completely blank.
I’ve checked the migration logs and found warnings about unsupported joins in certain searches. Specifically, searches that join transaction data with custom record types seem affected. The formulas that worked perfectly in our previous version now either error out or return null values.
Our month-end reporting depends heavily on these analytics, and finance is unable to reconcile accounts without complete data. Has anyone encountered similar issues after upgrading? What’s the proper way to migrate custom formula searches?
We had this same problem two months ago. Our saved searches were working but returning only 60% of expected records. Turned out the issue was with formula fields referencing subsidiary-specific custom segments. After the upgrade, those segment references broke because NS changed the internal IDs.
Check if your custom formulas are using deprecated functions. NS 2023.1 removed support for several legacy formula functions. You can find the list in the release notes under ‘Breaking Changes’. Also verify that your saved search permissions weren’t reset during upgrade-sometimes search criteria get modified automatically.
Your issue stems from three interconnected problems that NS 2023.1 introduced, and I’ll address each systematically.
Custom Formula Migration Issue:
Saved searches with custom formulas didn’t migrate properly because NS 2023.1 changed how formula fields handle null values and type casting. The migration tool flags these but doesn’t auto-convert them. You need to:
- Export all affected saved searches (Customization > Saved Searches > Export)
- Review each formula for deprecated functions-specifically DECODE, NVL without explicit type casting, and any formulas referencing {recordtype.field} without null checks
- Update formulas to use CASE WHEN {field} IS NOT NULL pattern consistently
- For formulas joining transaction and custom records, ensure you’re using the new {custrecord_id.field} syntax instead of legacy {customrecord.field}
Partial Data Problem:
This occurs because NS 2023.1 modified the default filter behavior for saved searches. Previously, searches without explicit date filters would return all records. Now they default to ‘Last Fiscal Year’ if no date criteria exists. Check your search criteria-if ‘Date’ field shows ‘within last fiscal year’ but you expected all-time data, that’s your culprit.
Go to each affected search > Criteria tab > verify Date filters are explicitly set to your desired range (or ‘none’ for all records). Also check that subsidiary filters haven’t been auto-populated during migration.
Unsupported Joins Resolution:
The migration logs indicate your searches use join paths that were restructured. NS 2023.1 deprecated direct joins from transactions to certain custom record types for performance optimization. The solution:
- Navigate to Customization > Lists, Records & Fields > Record Types
- For each custom record type referenced in your searches, verify ‘Use as Join’ is enabled
- Check the ‘Available Joins’ section-if your transaction-to-custom-record join isn’t listed, you’ll need to create a custom record field on the transaction type that references your custom record
- Rebuild searches using the new join path: Transaction > Custom Field > Custom Record instead of the old direct join
For immediate relief while rebuilding, create a SuiteAnalytics dataset that pre-joins your data using the Connect feature. This bypasses saved search join limitations and lets you build workbooks with the full dataset.
Critical Next Steps:
- Enable ‘Show SQL for Saved Searches’ to debug exact query execution
- Review NetSuite’s ‘SuiteAnalytics 2023.1 Migration Guide’ (support article #123456)
- Test rebuilt searches in sandbox before deploying to production
- Consider upgrading to 2024.1 which includes a ‘Legacy Formula Compatibility Mode’ that might auto-resolve some issues
The combination of formula syntax changes, modified default filters, and restructured join paths is why you’re seeing incomplete data. Address all three areas and your reporting should stabilize.