Merge-data overview

The following merge-data elements can be added in the e-mail template. The merge-data elements can be used to inform the user about various aspects of the case.

Link the e-mail template to the case category

Start sending mails from your Cases, some data of the case will be merged into the generated e-mail message.

Solution

Some X++ modifications are needed in two Forms.

Form EventCreateRule, method modified on Field EventRule.UserId:

public void modified()
{
  super();

  // BEGIN
  eventRule_SendEmailAddress.text(
        SysUserInfo::find(EventRule.UserId).Email);
  // END
}

Form EventRule, method setControlsActive on DataSource EventRule:

...
else if (!canShowPopUpCheckBox)
{
  alertMeBy.visible(true);
  eventRule_ShowPopUp.visible(false);
  eventRule_SendEmail.visible(true);
  eventRule_SendEmailAddress.visible(true);
  // BEGIN
  //eventRule_SendEmailAddress.text(userInfo.Email);
  eventRule_SendEmailAddress.text(
    SysUserInfo::find(EventRule.UserId).Email);
  // END
}
else
{
  alertMeBy.visible(true);
  eventRule_ShowPopUp.visible(true);
  eventRule_SendEmail.visible(true);
  eventRule_SendEmailAddress.visible(true);
  // BEGIN
  //eventRule_SendEmailAddress.text(userInfo.Email);
  eventRule_SendEmailAddress.text(
    SysUserInfo::find(EventRule.UserId).Email);
  // END
}

if (eventRule.UserId == curuserid())
  eventInboxSingleton.enabled(true);
...

Solution

To make your find method work, you need to pass through the reference to the temporary table.

public static TmpAvgCubicMeterPrices find(
         ProjId                    _projId,
         InventDimCombinationName  _inventDimCombinationName,
         TmpAvgCubicMeterPrices    _tmpAvgCubicMeterPrices,
         boolean                   _forUpdate = false)
{ 
    TmpAvgCubicMeterPrices   tmpAvgCubicMeterPrices; 
    ; 

    tmpAvgCubicMeterPrices.setTmpData( 
              _tmpAvgCubicMeterPrices);

    tmpAvgCubicMeterPrices.selectForUpdate(_forUpdate);

    select firstonly tmpAvgCubicMeterPrices
       where tmpAvgCubicMeterPrices.ProjId
                                                   == _projId  
       && tmpAvgCubicMeterPrices.InventDimCombinationName
                                == _inventDimCombinationName; 


    return tmpAvgCubicMeterPrices; 
}

Solution

The cause of the problem was the SysOperationProgress class. This class can be used to inform the user about status, operation and progress of the system. It was initiated before my changecompany call and closed after it. When the progress bar created by the SysOperationProgress class was refreshed during code execution within my changecompany class, a call is done by X++ to the Docu class. This triggers also a changecompany due my original legal entity. Hence some of my code within my changecompany call was executed in the company to which I did the change, some was done in the company I originated from. And this not all of the time, as it only happened if a refresh happened of my progress bar within the changecompany call. I removed the SysOperationProgress and my problem was solved.

Solution

public static void scheduleBatch()
{
    BatchHeader           batchHeader;
    BatchInfo             localBatchInfo;
    YourRunBaseBatchClass yourRunBaseBatchClass;
    SysRecurrenceData     sysRecurrenceData = 
             SysRecurrence::defaultRecurrence();
    ;

    yourRunBaseBatchClass = 
        YourRunBaseBatchClass::construct();

    // retry 3 times   
    sysRecurrenceData = 
        SysRecurrence::setRecurrenceEndAfter(
                        sysRecurrenceData, 3);
    // retry after 1 minute
    sysRecurrenceData = 
        SysRecurrence::setRecurrenceUnit(sysRecurrenceData, 
                             SysRecurrenceUnit::Minute, 1);
    
    localBatchInfo = yourRunBaseBatchClass.batchinfo();
    localBatchInfo.parmGroupId("YourBatchGroupId");
    batchHeader = batchHeader::construct();
    batchHeader.addTask(yourRunBaseBatchClass);
    batchHeader.parmRecurrenceData(sysRecurrenceData);
    batchHeader.save();
}

Solution

Create a new BaseEnum, let’s call it ProjCust, with the different sorting and/or grouping possibilities, for example one to group by ProjId and one to group by CustAccount.

Create the report Class.

Define in the classDeclaration a DialogField and variable to handle the different sorting/grouping possibilities for the report.

public class TutorialGroupReport_GroupReport 
                       extends RunBaseReport  
{
    DialogField             dialogReportBy;

    ADUProjCustDlvDate      reportBy;     
    #localmacro.CurrentList

        reportBy

    #endmacro
}

In the dialog method, the possibilities to sort/group the report data is shown.

public Object dialog()

{

    DialogRunbase dialog = super();

    ;

    dialog.addGroup("@SYS1046");

    dialogReportBy  = 
      dialog.addFieldValue(TypeId(ProjCust), 
                                   reportBy, 
                                "@SYS55014");

    return dialog; 

}
 

In the getFromDialog method, store the sorting/grouping option chosen by the end user

public boolean getFromDialog()  
{ 

    ;
    reportBy    = dialogReportBy.value();
     return super ();  
}

Create a method to return the option chosen by the end user.

ProjCust reportBy()  
{  
    return reportBy;   
}
 

Create an updateQuery method, which will adapt dynamically the report Query based on the option chosen by the end user

public Query updateQuery()  
{ 

    Query                   query;   
    QueryBuildDataSource    queryBuildDataSource; 

    QueryBuildRange         queryBuildRange;   
    ;
    query = queryRun.query(); 
  
    queryBuildDataSource = 
             query.dataSourceTable(tableNum(ProjTable));
     switch (this.reportBy())   
    { 

        case ProjCust::ProjId:   
            queryBuildDataSource.addSortField(
                            fieldNum(ProjTable,ProjId)); 

            break;   
        case ProjCust::CustAccount: 

            queryBuildDataSource.addSortField(
                       fieldNum(ProjTable,CustAccount));   
            queryBuildDataSource.addSortField(
                            fieldNum(ProjTable,ProjId)); 

            break;   
        default:    // In default, error. 

            throw error(strFmt("@SYS27147", 
                         this.toString()));  
    } 

    return query;   
}

Call the updateQuery method in the run method.

void run()  
{ 

    ;

    this.updateQuery();
     super();   
}

Add the other appropriate methods to the class, such as a lastValueElementName, pack, unpack, description and main method.

Create the Report and the Design of it.

Add your report Class and the report DataSource to be grouped/sorted dynamically as variable the classDeclaration

public class ReportRun extends ObjectRun  
{ 

    TutorialGroupReport_GroupReport tutorial_GroupReport;   
    ProjTable                       projTable; 

}

Assign the caller to the report Class variable in the init method.

public void init()   
{
    super();
     tutorial_GroupReport = element.args().caller(); 

}

In the fetch method you can change the sorting/grouping dynamically based on the choice of the end user and if necessary add additional design stuff.

public boolean fetch() 

{   
    QueryRun        queryRunProjTable; 

    ProjId          parentProjId;   
    CustAccount     custAccount; 

    ;
    queryRunProjTable = new QueryRun(
                tutorial_GroupReport.updateQuery()); 
  
    this.queryRun(queryRunProjTable);

    while (queryRunProjTable.next()) 

    {   
        projTable = queryRunProjTable.get(
                               tableNum(ProjTable)); 


        switch (tutorial_GroupReport.reportBy())   
        { 

            case ProjCust::ProjId:   
                if (projTable.ParentId != parentProjId) 

                    this.execute(1);   
                    parentProjId = projTable.ParentId; 

                break;  
            case ProjCust::CustAccount: 

                if (projTable.CustAccount != custAccount)   
                    this.execute(2); 

                    custAccount = projTable.CustAccount;   
                break; 

            default:    // In default, error.   
                throw error(strFmt("@SYS27147", 
                             this.toString())); 
        } 
  
        this.send(projTable);   
    } 

    return true;   
}

Solution

Add the new field to the Map PriceDiscResultFields and configure the necessary Mappings with the SalesLine and or SalesQuotationLine table.

In method isTriggerFieldChanged from Map PriceDiscResultFields, add following code for your new field:

…
boolean lineFieldChanged() 
{  
    return _priceDiscResultFields.SalesPurchQty         
             != priceDiscResultFieldsOrig.SalesPurchQty
           || _priceDiscResultFields.SalesPurchUnit      
             != priceDiscResultFieldsOrig.SalesPurchUnit
           || _priceDiscResultFields.CurrencyCode        
             != priceDiscResultFieldsOrig.CurrencyCode

          || _priceDiscResultFields.RecieptDeliveryDate
             != priceDiscResultFieldsOrig.RecieptDeliveryDate  
          || _priceDiscResultFields.Price
             != priceDiscResultFieldsOrig.Price
          // BEGIN
           || _priceDiscResultFields.YourNewField 
             != priceDiscResultFieldsOrig.YourNewField;
          // END  
}

In Class SalesLineType, method validateField, add following code:

// BEGIN

case fieldNum(SalesLine, YourNewField):

    ok = salesLine.runPriceDiscPolicyDialog();

    break;

// END