Forum Discussion
MichaelBerling1
6 years agoQrew Trainee
Hey thanks for replying. It's not as simple as it appears. If users were expected to click "Add New Test" it would be very simple because the parent record would save and the child would be created with the CDD.
I however want my users to use one form to add the child records all at once, then save. This can be 10+ children all with different [Test Names]. The complexity lies in the fact that when you create a new parent record, it doesn't immediately create a [Record ID#] or the parent [Test Category] until you save. In addition, using a grid-edit embedded report, doesn't drop the [Test Category] to the child record until that child record is created itself. You would have to add a field (let's say [Test#]) to initialize the child record before the CDD would work. If the child is not initialized first QB throws a "This Field is dependent" error. Thus I would have to instruct my users to fill out the sample information, save, edit, add child in grid-edit using the [Test#] as the first field. I don't want them to have to save then edit.
I however want my users to use one form to add the child records all at once, then save. This can be 10+ children all with different [Test Names]. The complexity lies in the fact that when you create a new parent record, it doesn't immediately create a [Record ID#] or the parent [Test Category] until you save. In addition, using a grid-edit embedded report, doesn't drop the [Test Category] to the child record until that child record is created itself. You would have to add a field (let's say [Test#]) to initialize the child record before the CDD would work. If the child is not initialized first QB throws a "This Field is dependent" error. Thus I would have to instruct my users to fill out the sample information, save, edit, add child in grid-edit using the [Test#] as the first field. I don't want them to have to save then edit.