Skip to content
SeamSetTalk to us

How it works

From a request in plain words to a screen, export or portal that keeps running

Your admin connects SeamSet to your account and decides what it can access. From there, you get a first version in minutes. Going live takes what it should: a test first, your admin's approval, and a log.

  1. Step 1Describe
  2. Step 2SeamSet builds it
  3. Step 3Test it before it goes live
  4. Step 4Your NetSuite admin approves

  1. Step 1Describe

    You describe the need in plain words: "Every month-end, hold each journal file until every entry passes our checks." SeamSet asks the questions your admin would ask, restates the need for you both to check, and flags gaps and conflicts before anything is built.

    Marta Kovac, controller

    "Every month-end, hold each journal file until every entry passes our checks."

    SeamSet asks

    • Which subsidiaries does this cover?
    • Who can release a held file?

    To check, for you and your admin

    At every month-end, hold each journal file until every entry passes the controller's checks, and give the fix for each failing entry.

  2. Step 2SeamSet builds it

    Native first. If NetSuite already does it (a saved search, a workflow, an approval rule), SeamSet sets that up, through the same approval, and writes no code. If the native route costs more than the need is worth, SeamSet says so. Account features stay your admin's switch.

    When nothing native fits, SeamSet builds only the missing part in SuiteScript, NetSuite's own scripting language: a scheduled script for a recurring export, a custom screen for one job. Outside NetSuite, a portal or a screen NetSuite's pages handle badly. A model writes the code.

    Covered by NetSuite

    The CSV Import Assistant loads the journals and returns the rejected rows with their errors.

    Missing

    An option to hold the whole file until every entry passes, with the fix in plain words.

    Building only that.

  3. Step 3Test it before it goes live

    You see the first version before anything goes live, check it and ask for changes.

    Each change comes with its documentation, and a SeamSet prefix in every object ID, linked to its request. So SeamSet never adds to what one r/Netsuite user described:

    "I can't tell what is standard NetSuite versus something customized for us."

    October journals

    214 entries · 3 to fix · nothing posted

    • Line 12Add a department: account 6120 needs one.
    • Line 57Debits and credits differ by 40.00.
    • Line 131The period is closed: use October.

    Documentation

    Holds the journal file until every entry passes the controller's checks, and gives the fix for each failing entry.

    • customscript_seam_0147_hold
    • custbody_seam_0147_check
    1. v2Fix shown in plain words for each entry3 Oct
    2. v1First version2 Oct

  4. Step 4Your NetSuite admin approves

    Your admin sees each change in plain words, then approves it, sends it back or rejects it. Nobody approves their own request.

    The log records who asked, who approved, what changed and when. You can export it at any time.

    If you stop using SeamSet, what runs inside NetSuite keeps running; portals stop.

    After go-live. Before each major NetSuite release, SeamSet reruns its checks in a preview account and tells your admin what needs attention. Fixes go through the same approval.

    Requested by Marta Kovac, controller · Approver: Daan Achterberg, NetSuite admin

    At every month-end, holds each journal file until every entry passes the controller's checks, and gives the fix for each failing entry. Posts the file once every entry passes. Removes the old "Batch note" field on journal entries.

    • Adds the check "Hold the file until every entry passes" to journal importscustomscript_seam_0147_hold · customdeploy_seam_0147_hold
      Reversible
    • Adds the field "Check result" on journal entriescustbody_seam_0147_check
      Reversible
    • Removes the old field "Batch note" on journal entriescustbody_batch_note
      Removes stored data
    • Posts the file once every entry passescustomscript_seam_0147_post · customdeploy_seam_0147_postPosted journals are corrected by reversing entries.
      Cannot be undone

    Code, folded: 2 scripts · SDF project

    ApproveSend backReject

Inside your NetSuite account by default. Outside for two reasons only.

Reports, imports, exports, approvals, stock views and screens built for one process run in your NetSuite account. When a request falls outside, SeamSet says so before building.

  • Reports
  • Imports
  • Exports
  • Approvals
  • Stock views
  • Screens built for one process

  • People with no NetSuite login. The Customer Center and Vendor Center need a NetSuite login. For customers and vendors without one, the portal runs outside NetSuite, and each sees only their own records.

    The costa second place showing some of your data, and a connection to secure. The portal reads from NetSuite when opened and keeps no copy of your records.

  • A screen NetSuite's pages handle badly. A scheduling board several people drag at once, live, on a shop-floor tablet.

    The costa connection to maintain. Your admin decides.

What SeamSet will not build

  • Go live without approval.

    No exception for small changes.

  • Rebuild what NetSuite already does, without telling you.

    SeamSet tells you what NetSuite covers before it builds.

  • Cut corners.

    Code is SuiteScript 2.1 in SDF projects, and no script edits NetSuite's pages directly, which Oracle's development guidelines rule out.

  • Delete posted transactions.

    Corrections go through credit memos and reversing entries.

  • Calculate commissions.

    NetSuite has its own commission features, and pay needs an owner who can explain every line.

  • Keep NetSuite in two-way sync with another application.

    That is an integration platform's job.

What can be undone, and what cannot

Before your admin approves, each line of a change carries one of these three tags.

Reversible
Screens, reports, workflows and scripts, and custom fields that hold no data yet. Rolling back redeploys the previous version, once your admin approves. What a redeploy cannot remove, SeamSet lists for your admin to delete in NetSuite.
Removes stored data
Deleting a custom field erases its data.
Cannot be undone
Records written and messages sent in production. A rollback changes the code, not what it already wrote or sent.

Requested by Marta Kovac, controller · Approver: Daan Achterberg, NetSuite admin

At every month-end, holds each journal file until every entry passes the controller's checks, and gives the fix for each failing entry. Posts the file once every entry passes. Removes the old "Batch note" field on journal entries.

  • Adds the field "Check result" on journal entriescustbody_seam_0147_check
    Reversible
  • Removes the old field "Batch note" on journal entriescustbody_batch_note
    Removes stored data
  • Posts the file once every entry passescustomscript_seam_0147_post · customdeploy_seam_0147_postPosted journals are corrected by reversing entries.
    Cannot be undone
Approve

Bring one request, and the questions your admin will ask.

Tell us about one request your team still handles by hand. We'll talk it through, from the request to your admin's approval.

Talk to us