I m trying to find additional documentation about the `SCRIP NetSuite Professionals #sdf

I'm trying to find additional documentation about ...

Josh Godfrey

01/10/2022, 11:05 PM

I'm trying to find additional documentation about the

SCRIPT ID

field located on an instance of a custom record type. We are managing instances of custom records across 4 different accounts, and I'm finding it difficult to with these system generated

SCRIPT IDs

(see below). • Does this

SCRIPT ID

field value need to be unique across the entire account, or just unique to the parent object?

Josh Godfrey

01/10/2022, 11:14 PM

Wondering if I can do something like this without causing any issues: Custom Record Type #1

Copy code

<customrecordtype scriptid="customrecord_sample_1">
    ...
    </customrecordcustomfields>
    ...
     <instances>
        <instance scriptid="_119">
            <custrecord_sampletextfield>Here is some sample text.</custrecord_sampletextfield>
            <isinactive>F</isinactive>
        </instance>

Custom Record Type #2

Copy code

<customrecordtype scriptid="customrecord_sample_2">
    ...
    </customrecordcustomfields>
    ...
     <instances>
        <instance scriptid="_119">
            <custrecord_sampletextfield>Here is some sample text.</custrecord_sampletextfield>
            <isinactive>F</isinactive>
        </instance>

What I'm trying to demonstrate is two different custom record types with two different instances sharing the same scriptid value.

Sean Murphy

01/18/2022, 4:04 PM

this is what I know Sample ID val_10025_6465499_sb1_558 val_ 10025 _6465499_sb1 _558 val_ is just text and is NOT required. 10025_ This first segment is sequential to the account , not the record type. 6465499_sb1. — this is the account number that the value was first created in. _558. this I have not found a logic to yet…. could be random or time related. the ID must be unique to the RECORD TYPE and not the account. I was able to reuse the script id “SeanTest” in records of different types but NOT within the same type. I would think very carefully about changing/reusing these id’s though as it seems like a significant risk to inadvertently either grad the wrong value at some point in the process of Importing/merging/Updating data that this ID will change and be very hard to track down. OR that in that same process running into a duplicated ID and having to change it to get the record to import.

3 Views

Open in Slack

Previous Next