Discussions

Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

Parent/Child relationship with custom records

edited Dec 3, 2019 9:11AM in SuiteCloud / Customization 4 comments

I have 2 custom records, call them "Parent" and "Child".  I've successfully established the relationship between the two.  I can enter a Parent record, save it, then view or edit it and enter one or more Child records associated with it.  But, I do not like this edit-twice approach.  Is there any way to enter the Child records during the creation of a Parent record as a single-step process?

My real-world issue is that I'm trying to create a "Collateral request form" for employees to fill out to request printed materials from our production group.  I don't really want to flow these through the system as orders for security (and other) reasons.  So, I'm trying to build a custom construct for this.  The catch is that one person might request 20 or more different collaterals at a time on a single form and I'd rather not create 20 quantity fields and 20 collateral fields to facilitate this.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders