Configure isPhantom mapping

This setup will cause all new assemblies in NetSuite to be marked as Phantom. Onscreen you will also see any new assemblies (not marked as Phantom) showing with an error.

image

To setup isPhantom, add a Property Mapping with accessor value isPhantom:

IsPhantom Property Mapping Settings

Setting	Value
Primary accessor	(Unmapped) or mapped to a Primary Source accessor if you have one
Secondary accessor	assemblyitem.isPhantom
Update Primary on Submit	unchecked
Update NetSuite on Submit	checked
Rendering Type	Checkbox
Prefer NetSuite value	checked

IsPhantom Property Mapping Rules

Given this input, create the following rules:

• A Text Manipulation import rule for your Primary/CAD source with the following text:

if (rowData.isAssemblyRow === true) {
  return true;
} else {
  return false;
}

• A Text Evaluation display rule that blocks submittal with the following text:

const isNewAssemblyRow = rowData.isAssemblyRow === true && rowData.isMissingInSecondaryDatasource == true && rowData.isFoundInSecondaryDatasource == false;

if (isNewAssemblyRow === true && (rowData.cells.isPhantom === false || (`isPhantom` in rowData.modifications === true && rowData.modifications.isPhantom === false)))
{
  return { status: 'failure', message: `New Assemblies must be set to isPhantom=true` }
}

Notes:

• The assemblyitem field isPhantom and bomcomponentrevision field itemSource are somewhat related fields in NetSuite.

• The isPhantom field takes boolean values

• The itemSource field takes string enum values such as "STOCK" and "PHANTOM".

• With Advanced BOMs, when setting an assemblyitem field isPhantom to false, and later adding this item to a BOM, its related itemSource value will default to "STOCK". When setting the assemblyitem field isPhantom to true, and later adding this item to a BOM, its related itemSource value will default to "PHANTOM"

• The itemSource value can be later changed in the BOM and be different than the isPhantom field value of its related asssemblyitem