Oracle Application Express自动生成编辑页空白及数据关联问题咨询

Hey Paulina, sorry to hear you're stuck with these APEX edit page quirks—let's break this down step by step, since this kind of thing is super common when you're just getting started with auto-generated pages!

This is the backbone of your edit page—if this is misconfigured, nothing else will work right:

• Head to your broken edit page in Page Designer, then switch to the Processing tab. Look for the process named something like Process Row of [YOUR_TABLE_NAME] (this is the auto-generated DML process).
  • Double-check the Table/View Name is set to your target table (no typos here!)
  • Confirm the Primary Key Column(s) are correctly mapped to your hidden PK item. APEX needs this to find the exact row you're trying to edit/delete.
  • Make sure Allow Update and Allow Delete are enabled in the Operation Options section—sometimes the wizard disables these if it detects unusual table constraints.

If the auto-generator skipped fields, it's usually for a reason—and manually adding items without linking them properly causes the "empty row" issue:

• The wizard skips columns that are:
  • Marked as read-only/computed at the table level
  • Have default values APEX assumes shouldn't be edited, or custom data types it can't parse automatically
• Instead of adding items from scratch, do this to ensure proper linking:
  1. In Page Designer, right-click the Items section in the left pane → Select Create Page Item → From Column
  2. Pick your target table, then select the columns you need to add. This auto-sets the item's Source Type to Database Column and links it directly to the correct table column.
  3. For any items you already added manually:
     • Check that Source Type is set to Database Column
     • Confirm Source Column Name matches your table column exactly (case-sensitive if your database uses case-sensitive identifiers)

If editing shows an empty row, APEX can't find the row using the PK value passed to the page. Here's how to fix that:

• Check your report page's edit link:
  • Go to your report page, find the edit link column. In its attributes, make sure Item 1 is set to your edit page's PK item (e.g., P2_CUSTOMER_ID) and Value 1 is set to your report's PK column (e.g., CUSTOMER_ID). This passes the row's PK to the edit page via URL.
• Verify the hidden PK item on the edit page:
  • Set its Default Value to &PX_ID. (replace X with your edit page number—this pulls the PK from the URL parameter when you open the page)
  • Ensure its Source Type is still Database Column linked to your table's PK.
• For delete not working:
  • Check your Delete button's attributes: Action should be Submit Page, and Request should be set to DELETE (the auto DML process listens for this request to trigger deletion)
  • Confirm the DML process's Condition is set to Request = DELETE (or matches whatever request value you set on the button)

Since you mentioned some edit pages work, pull up one of those working pages and compare these key settings to the broken one:

• DML process table/PK mappings
• Item source types and column links
• Button actions and request values
• Page security/session state settings (under Page Properties → Security)

If all else fails, just re-create the edit page using the wizard:

1. Go to your app → Create Page → Form → Form on a Table or View
2. Walk through the wizard, select your table, pick the columns you need, and link it to your existing report. This often wipes out any weird misconfigurations that happened when tweaking the page manually.

内容的提问来源于stack exchange，提问作者Paulina L