You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Acumatica弹窗模型中自定义字段更新问题求助

Hey there! Let's troubleshoot the issue you're having updating your custom UsrCustomerNote field in an Acumatica popup. Based on the DAC extension you shared, here are the most common fixes and checks you should run through:

1. Verify the Popup's Data View Configuration
  • Make sure the popup's data view is bound to the BAccount DAC (and includes your extension) and is set to allow updates. If using a PXPopupView, confirm the CommitChanges property is enabled in the ASPX markup:
<px:PXPopupView ID="pxPopupView" runat="server" DataSourceID="ds" CommitChanges="True" ...>
  • Double-check that your graph's data view explicitly includes the UsrCustomerNote field in its select statement. For example:
public PXSelect<BAccount, Where<BAccount.bAccountID, Equal<Current<SomeCurrentField>>>> CustomerPopupView;
2. Validate the Popup's Field Control Setup
  • Ensure the field control in the popup is correctly bound to your custom extension field. The ASPX should reference it using the extension syntax (no extra prefix needed if the DAC extension is properly registered):
<px:PXTextEdit ID="edUsrCustomerNote" runat="server" DataField="UsrCustomerNote" />
  • If using a PXFormView inside the popup, confirm its DataMember property points to the correct data view that includes your UsrCustomerNote field.
3. Confirm the DAC Extension is Properly Registered
  • Even though your extension code looks correct, verify it's recognized by Acumatica:
    1. Open your customization project in the Customization Project Editor
    2. Navigate to Data Access > DAC Extensions and check if BAccountExt is listed under the BAccount DAC
  • If you added the extension manually (not via the editor), ensure its assembly is deployed to the Acumatica site's Bin folder and included in your customization project.
4. Fix Popup Save/Close Logic
  • If your popup uses a custom button to close, make sure it triggers a save before closing. For example, configure the button's AutoCallBack to commit changes:
<px:PXButton ID="btnSaveClose" runat="server" Text="Save & Close" 
  AutoCallBack-Target="pxPopupView" 
  AutoCallBack-Command="Save" 
  AutoCallBack-Behavior="Close" />
  • If using custom graph code for the button, explicitly persist the changes:
public PXAction<YourGraph> SaveClose;
[PXButton]
[PXUIField(DisplayName = "Save & Close")]
protected void saveClose()
{
    Base.CustomerPopupView.Cache.Persist(PXDBOperation.Update);
    Base.Actions.PressSave();
    // Close the popup logic here
}
5. Debug with Trace Logs
  • Enable Acumatica's verbose trace logs to catch hidden errors:
    1. Go to System Management > System Maintenance > Trace
    2. Set the trace level to Verbose
    3. Perform the update action in the popup, then check the log for exceptions related to UsrCustomerNote
6. Check Field Permissions
  • Ensure your user role has Write access to the UsrCustomerNote field:
    1. Go to System Management > Security > Roles
    2. Select your role, then navigate to Permissions > Data Access
    3. Find the BAccount DAC, expand it, and confirm the UsrCustomerNote field has Write permission enabled

If you're still stuck, share more details like:

  • The exact behavior (e.g., field doesn't save, error message pops up, popup closes without updating)
  • The full ASPX markup of your popup
  • Any custom graph code tied to the popup

内容的提问来源于stack exchange,提问作者Bikash Lama

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.25 03:36:46