How to Resolve Field Disable Issues When Joining DACs in Acumatica Views

When developing custom screens in Acumatica, it’s common to join multiple Data Access Classes (DACs) in a view to display related data. However, a frequent challenge arises: fields from secondary DACs often appear as disabled (read-only) on the UI. This article will explore why this issue occurs and provide detailed solutions to enable editable fields in joined DACs.

Why Fields in Secondary DACs Become Disabled

In Acumatica, when DACs are joined in a BQL query, the framework designates one DAC as the primary (editable) table and treats the others as read-only. This behavior ensures data integrity, as fields in secondary DACs are not directly bound to the primary entity in the transaction cache.

However, custom implementations often require fields from secondary DACs to be editable. For example, you might need to display and edit production order data (AMProdItem) alongside transaction data (AMMTran), but joined views may disable fields in AMProdItem.

Common Scenarios Leading to This Issue

1. Multiple Joined DACs: Adding multiple DACs to a view, especially with InnerJoin or LeftJoin, causes secondary DAC fields to inherit a read-only state.
2. Primary/Secondary Table Designation: The primary DAC in the query governs editability, while secondary DACs are considered auxiliary.
3. Custom DAC in a Composite View: When integrating a custom DAC alongside built-in DACs, Acumatica's caching logic may not automatically enable fields.

Solutions to Enable Editable Fields in Joined DACs

Here are several approaches to resolve this issue:

1. Use PXProjection for Editable Joins

PXProjection creates a virtual DAC that combines fields from multiple DACs. This allows for editability while maintaining data consistency.

Example:
Define a projection DAC for AMMTran and AMProdItem:

Update your view to use the projection:

public SelectFrom<AMMTranProdProjection>.View HeaderView;

2. Enable Fields Programmatically

You can explicitly enable fields in secondary DACs using the RowSelected event of the primary DAC.

Example:

3. Define Separate Views for Each DAC

Instead of joining DACs in a single view, create separate views for each DAC and manage relationships through delegates or event handlers.

Example:

public SelectFrom<AMMTran>.View HeaderView;

public SelectFrom<AMProdItem>

    .Where<AMProdItem.orderType.IsEqual<HeaderView.Current.orderType>

        .And<AMProdItem.prodOrdID.IsEqual<HeaderView.Current.prodOrdID>>>.View ProdItemView;

This approach gives you finer control over which fields are editable.

4. Verify Field-Level Configuration

Sometimes, field properties in the Customization Project Editor can unintentionally cause issues:

●     Ensure fields are not set to read-only or disabled explicitly.

●     Verify that Field Security settings are not restricting editability.

5. Directly Override Cache-Level Attributes

For finer control, override attributes in the cache to enable specific fields:

Example:

protected virtual void AMProdItem_RowSelected(PXCache cache, PXRowSelectedEventArgs e)

{

    var row = e.Row as AMProdItem;

    if (row == null) return;

    PXUIFieldAttribute.SetEnabled<AMProdItem.prodOrdID>(cache, row, true);

}

6. Modify Join Logic if Possible

Reorder your join to place the editable DAC as the primary table in the BQL query. For example, if you are only storing data in a custom DAC, make it the primary DAC in the join.

Key Takeaways

1. Understand Acumatica's Cache Logic: Secondary DACs are treated as read-only unless explicitly enabled.
2. PXProjection Is a Powerful Tool: Use it to combine DACs into a single editable virtual table.
3. Dynamic Enabling: Utilize RowSelected or cache-level overrides to enable specific fields.
4. Separate Views Offer Flexibility: Linking views programmatically can simplify complex data models.
5. Field-Level Validation: Always confirm that field attributes and security settings align with your requirements.

By leveraging these solutions, you can create robust and user-friendly forms in Acumatica that support editable fields across joined DACs. For more Acumatica development insights, stay tuned to our blog!

Looking to customize your Acumatica screens for better usability and flexibility? Our experts can help you implement editable fields in joined DACs, optimize your BQL queries, and enhance your system’s functionality. Submit your customization request today and take your Acumatica development to the next level!