Overview & Summary
ZoneExtract 3.4.6 was released on 16th October 2026 and delivers key enhancements to legacy Tactical Connect migration imports, alongside critical fixes to export recurrence scheduling:
Saved Search Name Resolution on Migration: Enhances migration import logic to resolve Saved Searches accurately even when legacy deployment titles were truncated by NetSuite's 60-character limit or contain cache prefixes.
Daily Export Recurrence Scheduling: Resolves an issue where time zone discrepancies caused daily recurring exports to enter a continuous execution loop every 30 minutes.
Enhancement (1)
Saved Search Resolution on Legacy Migration Import: Enhanced the configuration import engine (
ZoneExtract_Import_MR) when importing legacy Tactical Connect exports. Previously, if a Saved Search script ID could not be found, secondary resolution by name performed an exact string match. Because NetSuite truncates script deployment titles exceeding 60 characters with middle truncation (e.g.,Cache: Satori Reporting: Tran...rtial) Sub Currency F), exact name matching failed to associate the search in the target environment. The matching logic has been refined to strip legacy prefixes and resolve truncated deployment titles, ensuring migrated export configurations link successfully to their corresponding Saved Searches. (ZR-2651)
Maintenance/Bug Fix (1)
Daily Export Recurrence Scheduling Loop: Fixed a time zone conversion discrepancy in daily recurrence scheduling (
interval = DAYS). When combining date and time inputs across differing server/company time zones, the schedulednextDatecould be calculated in the past relative to UTCnow(), causing the pending export request's expected run time to immediately evaluate as overdue. This led to exports triggering repeatedly on every Map/Reduce scheduler run (~every 30 minutes). Daily recurring exports now accurately account for time zone offsets, scheduling next runs for the intended calendar time. (ZR-2647)
Frequently Asked Questions (FAQ)
1. Does the migration import fix require re-exporting configurations from Tactical Connect?
No. The fix improves the import engine (ZoneExtract_Import_MR). Existing export JSON files containing truncated deployment titles or Cache: prefixes can be re-imported directly without needing new exports.
2. How does ZoneExtract resolve truncated Saved Search titles during import?
When an exact match on the Saved Search script ID is unavailable, ZoneExtract cleanses the deployment title by removing legacy prefixes (such as Cache:) and accommodates middle-truncated titles (...) to match against full Saved Search names in the target NetSuite account.
3. Were hourly recurring exports affected by the scheduling loop?
No. Export Definitions configured with hourly intervals (e.g., every 24 hours) bypass time-of-day and calendar date re-combination and were not subject to the timezone offset issue. The fix specifically addresses daily interval configurations (interval = DAYS) tied to specific execution times.
4. Do existing daily Export Definitions need to be updated or rescheduled?
No manual adjustments are required. Existing daily Export Definitions will automatically compute their subsequent execution date and time using the corrected timezone offset logic.