Best Of

Thank you @Ramu Komireddy_9891 @Tigran Shahnazaryan for your help.

Can't thank you enough @Ramu Komireddy_9891 !

Hi @User_DFQMH, this happens because Go To Record needs the Internal ID of the current Sales Order. Using {id} often resolves to the transaction number, so NetSuite can’t find the record and opens a new one.

Try this:

• Set your workflow field to {internalid} (not {id}), or reference Current Record if available.
• In Go To Record: Record Type = Sales Order, Record ID = {internalid}, Mode = Edit.

Note: Workflows can’t truly do a “Reject → prompt for reason → submit” in one step. For that UX you’d typically use a custom button + Suitelet/client script to capture the reason.

Did I miss the 2025 Annual New Release Quiz? I don't want my certifications to lapse.

Thanks

Kevin

Hello @Wishal44 ,

Good day to you

Short answer: No — Suitelet fields don’t support built-in “filtering” like standard/custom field sourcing does. The source parameter only pulls from a list/record type, but it doesn’t support conditions/filters.

But you can absolutely replicate this behavior — you just need to do it manually in SuiteScript.

First you add the field, then you create a saved search, then you push the values through a loop and you can assemble on how you want it took like. Similar to something like this:

//adding a new field without a source value
var periodField = form.addField({
    id: 'custpage_period',
    type: serverWidget.FieldType.SELECT,
    label: 'Accounting Period'
});

//creating a search that would have the accounting periods, adjust filters if needed
var periodSearch = search.create({
    type: search.Type.ACCOUNTING_PERIOD,
    filters: [
        ['isclosed', 'is', 'F']
    ],
    columns: ['internalid', 'periodname', 'startdate', 'enddate']
});

//pushing the values on the select option with you customized results
periodSearch.run().each(function(result) {
    var name = result.getValue('periodname');
    var start = result.getValue('startdate');
    var end = result.getValue('enddate');

    // Customize however you want
    var customLabel = name + ' (' + start + ' - ' + end + ')';

    periodField.addSelectOption({
        value: result.getValue('internalid'),
        text: customLabel
    });

    return true;
});

Let me know if you need further clarification.

No I believe I'm trying to use SuiteAnalytics Workbook

Hi @User_5FWNK, 

Here's how you can create a saved search to identify Bills with Duplicate Reference number:

1. Reports > Saved Searches > All Saved Searches > New
   
2. Choose Transaction search.
   
3. In Criteria tab, set the following:
   
   1. Type = Vendor Bill
      
   2. Main Line = T
      
   3. Document number: is not empty (
      to exclude blanks)
4. In Criteria tab > Summary subtab, add the following:
   1. Summary Type: Count
   2. Field: Internal ID
   3. Description: is greater than 1
5. In Results tab, add the following:
   
   1. Document Number (set Summary Type to Group)
      
   2. Internal ID (set Summary Type to Count)
   3. Name (set Summary Type to Group)
      
6. Save and run.

Let me know if this works. Thank you!

Hi @David Achkar since these were intentionally or accidentally unmatched, you simply need to match them again.

1. Bank Data: In your matching screen, look for the corresponding imported bank statement line(s) that represents this deposit (it may be a single lump-sum bank line of 1,544,660.95 or two separate lines).
2. Select the Transactions: Check the empty boxes next to DEP17388 and DEP17389 in the Account Transactions list.
3. Select the Bank Line: Check the corresponding box(es) in the imported bank data section.
4. Verify: Ensure that once all boxes are checked, the Difference at the bottom right shows 0.00.
5. Submit: Save or submit the match to clear them from this queue.

Every matched transaction can be unmatched, and it appears this was done intentionally.

You have to match them again with the related Bank Statement entries.