Solution: Add a checkbox custom filter

The solution is elaborated by means of an example. Suppose you want to provide the end user with an easy filtering on the customer form to show only customers with active Projects (Projects not in the Project Stage Completed).

To achive this, you can follow these steps:

1. Duplicate the CustTable form and add a checkbox control ctrlCustActProjs to it for the filtering purposes. Set the AutoDeclaration property of the checkbox to Yes.
2. Add the ProjTable data source to the form and link it to the CustTable data source.
3. Override the executeQuery method of the CustTable data source as follows:
   

   public void executeQuery()
   {
       QueryBuildDataSource qbdsProjTable = 
       this.query().dataSourceTable(tableNum(ProjTable));
       QueryBuildRange qbrProjStatus;
       ;
   
       if (ctrlCustActProjs.value() == NoYes::Yes)
       {
           qbdsProjTable.enabled(true);
           qbrProjStatus = 
               SysQuery::findOrCreateRange(qbdsProjTable, 
                            fieldnum(ProjTable, Status));  
           qbrProjStatus.value(
               Global::queryNotValue(
                                 ProjStatus::Completed));  
       }
       else
       {
           qbdsProjTable.enabled(false);
       }
       super();
   }

   
   

By toggling the checkbox only customers with active Projects will be shown or not.

Enabling the qbdsProjTable QueryBuildDataSource based on the checkbox links or removes the ProjTable to the CustTable in the form query.

The search for only active Projects is achieved by adding or finding the qbrProjStatus QueryBuildRange. Use the Global::queryNotValue to look up values different from a base Enum value.

Solution: Adapt class SalesTableType

A small X++ code fix can solve this problem in class SalesTableType, method syncPurchTable.

if (_salesTable.fieldChanged(fieldnum(SalesTable, SalesType))) 
{ 
    switch(salesTable.SalesType) 
    {

        case SalesType::Subscription    :   
            axPurchTable.parmPurchaseType(
                            PurchaseType::Subscription); 
            break;
  
        case SalesType::Sales           :   
            axPurchTable.parmPurchaseType(
                            PurchaseType::Purch);        
            break;
  
        case SalesType::ReturnItem      :   
            axPurchTable.parmPurchaseType(
                            PurchaseType::ReturnItem);   
            break;
  
        case SalesType::Blanket         :   
            axPurchTable.parmPurchaseType(
                            PurchaseType::Blanket);      
            break;
  
        // BEGIN: intercompany chain for item requirements
        case SalesType::ItemReq         :   
            axPurchTable.parmPurchaseType(
                            PurchaseType::Purch);        
            break;  
        // END: intercompany chain for item requirements


        default : 
            axPurchTable.parmPurchaseType(
                            PurchaseType::Journal);

    }  
}

Upon creating an Intercompany Purchase Order, it won’t be of type Journal anymore and the Intercompany Sales Order in the vendor company account will be created automatically too.