Creating Advanced Settings Screens

(I was having a hard time posting this in one message so I broke it out into 2 )

This can be very poor user experience on a screen like a preference screen, where there is no innate link between the master and detail. I will show you how to do this without ruining the PXSave action. Consider the following graph:

using System;
using PX.Data;

namespace Blog
{
  public class DemoGraph : PXGraph<DemoGraph>
  {

    public PXSave<MasterTable> Save;
    public PXCancel<MasterTable> Cancel;


    public PXSelect<MasterTable> MasterView;
    public PXSelect<DetailsTable> DetailsView;
  }
}

Both the MasterTable and the DetailsTable contain a field “Prepayment Percent” The major change is in the aspx as shown below. The first view ‘MasterView’, which is the primary view is not used to create a form. Rather, the dataview is bound to the PXTab directly and the "prepayment percent" field control is created directly without a form. The second view, ‘DetailsView’ is then bound to a form within the tab.

Here any change to the fields that are bound to ‘DetailsView’ not only enables the save button but also save the values on click of the save button. Therefore, the user can edit and save values on either tab, with no link between the DACs, and have a proper user experience.

Happy coding!

-Kyle

Thank you for sharing this information with the community @Kyle Vanderstoep!