Best Of

Hello User_N1Q40,

Yes, we have recently experienced a similar issue with both the Routine Scheduled Maintenance and the Planned Upcoming Upgrade Emails.

i.e., The scheduled time on the notification emails does not match the Customer-Scheduled Maintenance page. The time on the Customer-Scheduled Maintenance page is correct.

Note that our recent Routine Maintenance was processed at the Date and Time listed on the Customer-Scheduled Maintenance page.

Thank you,

Todd Niedringhaus

Hi guys!

How can i create a saved search returning the vendors or customers for specific/selected subsidiaries of the environment?

Because some may be set as primary subs or selected in the subsidiaries subtab in vendors and customers, what criteria should work to get all the customers/vendors working for specific/selected subsidiaries?

Thank you Angel! There was a department restriction on the folder that did not match the employee record!

Now I just have to find out who changed the employee record and why…. the joys of Admin detective work!

Thank you everyone for your suggestions.

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