Collapsible Field in payload default

The Collapsible field is presentational-only and only affects the Admin panel. By using it, you can place fields within a nice layout component that can be collapsed / expanded. Admin Config Example collections/ExampleCollection.ts import { CollectionConfig } from ‘payload/types’ export const ExampleCollection: CollectionConfig = {   slug: ‘example-collection’,   fields: [     {  … Continue reading Collapsible Field in payload default

Global Hooks in payload

Globals feature the ability to define the following hooks: beforeValidate beforeChange afterChange beforeRead afterRead Config All Global Hook properties accept arrays of synchronous or asynchronous functions. Each Hook type receives specific arguments and has the ability to modify specific outputs. globals/example-hooks.js import { GlobalConfig } from ‘payload/types’; const ExampleHooks: GlobalConfig = {   slug: ‘header’,… Continue reading Global Hooks in payload

Proposal For Automated Management of Main and Intercompany Purchase Orders in NetSuite

Proposal Summary    This proposal outlines implementation of an automated system within NetSuite that streamlines the creation and management of Intercompany Purchase Orders (POs) based on a manually created Main Purchase Order.   The estimated effort for implementing the customization in the Sandbox and Production is 46 hours.   The scope and the provided estimate are based… Continue reading Proposal For Automated Management of Main and Intercompany Purchase Orders in NetSuite

Optimizing NetSuite Performance – First Load of a Record

Optimizing NetSuite Performance – First Load of a Record To provide the best customer experience, NetSuite leverages multilayer caching to speed up performance on frequently used operations. For the first execution of a record and action combination (for example, viewing a sales order), the system needs more time to load and perform the action. For… Continue reading Optimizing NetSuite Performance – First Load of a Record

Customize extension-related HTML and Sass files

To customize extension-related HTML and Sass files, you must use the override method. This involves placing copies of source HTML and Sass files from your Extras directory into your theme directory and making your customizations there. When you deploy your changes, the theme development tools detect the new files and initiate an override within the… Continue reading Customize extension-related HTML and Sass files

Issue of adding If in Sass files

void if constructions using exposed Sass variables. For example: @if $sc-color-secondary == $12345 { background-color: $sc-color-primary;} @else { background-color: $56789;} The problem with this is that the frontend does not know the else condition. Passing values within or grouping variables as mixins causes a similar issue. All of these issues are solved during the backend… Continue reading Issue of adding If in Sass files

User-Defined Function Calls in Sass

Avoid user-defined function calls. For example, assuming that $sc-primary-color is also: $sc-color-secondary: myfunc($sc-primary-color) /*editable(…) In this example, you set the result of an exposed variable, such as $sc-color-secondary, to a custom function, myfunc($sc-primary-color). Assuming $sc-primary-color is also declared as editable, when the SMT administrator changes the primary color value, the primary color value compiles quickly… Continue reading User-Defined Function Calls in Sass