Skip to main content
Change-Based Fetch Coverage in NetSuite
Support avatar
Written by Support
Updated over 5 months ago

Change-Based Fetch significantly reduces the time required for fetching, making it highly effective for environments undergoing regular configuration updates. This is because it selectively retrieves only the elements that have changed since the last fetch. However, there are a few exceptions due to constraints imposed by API capabilities:

  1. When executing Change-Based Fetch on Roles, Salto cannot retrieve changes made to the Script ID field. Therefore, after modifying the Script ID field in a Role, performing a Full Fetch in Salto is necessary.
    โ€‹

  2. Whenever a Change-Based Fetch is initiated, the following types are fully fetched, ensuring their changes are represented in Salto once the fetch completes:

    1. addressForm

    2. advancedpdftemplate

    3. bankstatementparserplugin

    4. bundleinstallationscript

    5. center

    6. centercategory

    7. centerlink (added in the latest version of Netsuite - 2021.1)

    8. centertab

    9. clientscript

    10. cmscontenttype

    11. customglplugin

    12. customrecordactionscript

    13. customtransactiontype

    14. dataset

    15. datasetbuilderplugin

    16. emailcaptureplugin

    17. emailtemplate

    18. entryForm

    19. ficonnectivityplugin

    20. fiparserplugin

    21. kpiscorecard

    22. mapreducescript

    23. massupdatescript

    24. pluginimplementation

    25. plugintype

    26. portlet

    27. promotionsplugin

    28. publisheddashboard

    29. restlet

    30. savedcsvimport

    31. scheduledscript

    32. sdfinstallationscript

    33. sspapplication

    34. sublist

    35. subtab

    36. suitelet

    37. transactionForm

    38. translationcollection

    39. usereventscript

    40. workbook

    41. workbookbuilderplugin

    42. workflow

    43. workflowactionscript

Related articles:

Did this answer your question?