Composite App (Header/Detail) – Popup Detail App Causes Continuous Save When Header Is Saved

Nextworld Platform
1

Context / Objective

We are working with an Expenses Header/Detail application displayed using a 2-step Composite App.

image
image1907×926 129 KB

Our goal is to capture Expense Entry Detail records via a popup application instead of:

  • the native side-by-side detail view, or

  • clicking into the standard detail app (nsNVExpenseEntryDetail).

This is intended to improve data entry UX by enforcing a modal-style entry experience.

image
image1907×926 120 KB

Design / Configuration

  • Created a copy of the standard detail app:

    • nsNVExpenseEntryDetailPopUp

    • Uses the same detail table as nsNVExpenseEntryDetail

  • The popup app:

    • Overrides the standard detail app for record creation and edit

    • Is launched via a Queue Application Link triggered from a logic block when the user clicks “Add New Entry”

  • The popup app uses Save and Exit

  • After closing the popup:

    • The newly created expense detail record appears correctly in the detail list grid with all entered values

Observed Behavior

  1. User clicks Add New Entry

  2. Popup app opens and user enters data

  3. User clicks Save and Exit

  4. Detail record appears correctly in the detail list (values visible)

  5. At this point, the record appears to be partially saved but not fully committed

  6. If the user now clicks Save on the Header/Detail Composite App:

    • The application enters a continuous save state

    • Blue loading spinner appears and never completes

  7. If instead the user:

    • Clicks the green row-level save (flag) icon on the detail row first

    • Then clicks Save on the composite app
      → The save completes successfully and the entire record commits properly

Expected Behavior

After closing the popup detail app and returning to the composite:

  • The user should be able to Save the header/detail composite directly

  • No additional row-level save action should be required

  • No continuous save / infinite spinner should occur

Question

Is there a supported way to:

  • Fully commit a detail record created via a popup application

  • So that the header-level Save on a Header/Detail Composite App does not require an additional row-level save,

  • And avoids the continuous blue loading spinner?

Specifically, is there:

  • A recommended pattern for popup-based detail entry in composites?

  • A configuration, link type, or logic action that ensures the detail record is treated as fully saved/committed before the composite save?

  • Any known limitation or required step when overriding native detail behavior with a popup app?

Additional Notes

  • No custom table structure changes were introduced

  • Issue is reproducible consistently

  • Behavior only occurs when the detail record is created via the popup app (not via native side-by-side entry)

Any guidance or confirmation of expected behavior would be appreciated.