Custom Table Insert Does Not Happen for Customer Extension

Thanks for the response.  Yes, the first option is similar to what I’m trying to achieve with a custom table that doesn’t impact the other BAccount types with added UDF fields, but I was looking for a cleaner approach that doesn’t mix the fields together in the CurrentCustomer view.  The blog link is very helpful though.  I see more related posts when using the correct terms. I was hoping that the master:detail approach from T210 would work to link the custom table to ARCustomer; it does as far as I can tell, just not for inserts. I’m sure it will become clearer as to why that is as I get more experience with this framework.  I’ll try this approach for now.  Thanks again.

The PXTable approach worked for inserts.  I can query the underlying custom table and see the records.  However, when going back to the same customer in change mode, the values are not pulled into the view fields for display and any attempt to save results in the message Error: Another process has added the 'Customer' record. Your changes will be lost.

DAC Definition:

using System;
using PX.Data;
using PX.Objects.AR;

namespace CustomerDealerExtended
{
    // Acuminator disable once PX1011 InheritanceFromPXCacheExtension [Justification]
    [PXCacheName(Messages.ZZCustomerDealerExt)]

    [PXTable(typeof(Customer.bAccountID), IsOptional = true)]

    public class ZZCustomerDealerExt : PXCacheExtension<Customer>
    {
        public static bool IsActive()
        {
            return true;
        }

        #region BAccountID
        [PXDBInt(IsKey = true)]
        public virtual int? BAccountID { get; set; }
        public abstract class bAccountID : PX.Data.BQL.BqlString.Field<bAccountID> { }

        #endregion
...
}

Graph Definition (no more view):

using PX.Data;

namespace PX.Objects.AR
{
    // Acuminator disable once PX1016 ExtensionDoesNotDeclareIsActiveMethod extension should be constantly active
    public class CustomerMaintExt : PXGraphExtension<PX.Objects.AR.CustomerMaint>
    {
        public static bool IsActive()
        {
            return true;
        }

    }
}

I will look at the SQL for the join in change mode.

​@bbohn I dont think your require GraphExt for your purposes. Reference to PXTable can be found at DAC Extension Mapped to an Extension Table

Other issue working with Customer DAC could be that it is derived from BAccount DAC. Maybe share full SQL and full DAC code to review and assist accordingly.

Thanks for the response and the link.  True on the need for the graph extension, until I re-add the event handler for RowSelected to conditionally hide the tab. After a bunch of errors, I started over with a clean install and project.  It works for Create and Change but not for Delete.  Whether I use an inner join or left out join in the DAC definition, I get the exception message “The multi-part identifier "Customer.BAccountID" could not be bound.”.  I’m assuming it’s a JOIN issue but I’m not seeing it.  The Trace shows the message and exception but not exactly which SQL operation is failing.

​@bbohn Maybe consider adding CompanyID, DeletedDatabaseRecord and Audit Columns and test again for Deletion
Requirements for an Extension Table Schema

Thanks, I have the CompanyID and DeletedDatabaseRecord fields defined already.  I excluded the standard audit fields as instructed and didn’t elect to rename them because they’re not needed.