AX 2012 - Associare un contatto ad un indirizzo

Con questo job possiamo associare un contatto ad un qualsiasi indirizzo:

static void LIL_CreateAddressContact(Args _args)  
{  
    DirPartyContactInfoView          dirPartyContactInfoView;  
    LogisticsContactInfoView         logisticsContactInfoView;  
    LogisticsElectronicAddress       logisticsElectronicAddress;  
    dirPartypostalAddressView        dirPartypostalAddressView;  
    logisticsLocation                logisticsLocation;  
    CustTable              custTable;  
   
    //identificare l'indirizzo a cui associare il contatto  
    select firstOnly dirPartypostalAddressView  
        join CustTable  
        where CustTable.Party == dirPartypostalAddressView.Party  
        && CustTable.AccountNum == "US-002"  
        && dirPartypostalAddressView.LocationName == "TEST03"  
        && dirpartypostalAddressView.ValidFrom <= DateTimeUtil::utcNow()  
        && dirpartypostalAddressView.ValidTo >= DateTimeUtil::utcNow();  
    
    if(dirPartypostalAddressView)  
    {  
        select firstOnly logisticsLocation  
        where logisticsLocation.ParentLocation == dirPartypostalAddressView.Location;  
       
        if(!logisticsLocation)
        {
            logisticsLocation.clear();
            logisticsLocation.initValue();
            logisticsLocation.ParentLocation = LogisticsLocation::find (dirPartypostalAddressView.Location).RecId;
            logisticsLocation.IsPostalAddress = NoYes::No;

            logisticsLocation.insert();
        }
   
        dirPartyContactInfoView.LocationName  = "contatto mail";  
        dirPartyContactInfoView.Locator     = "somarisuax@mail.com";  
        dirPartyContactInfoView.Type      = LogisticsElectronicAddressMethodType::Email;  
        dirPartyContactInfoView.IsPrimary    = NoYes::No;  
        dirPartyContactInfoView.Location    = logisticsLocation.RecId;  
   
        logisticsElectronicAddress.initValue();  
        logisticsContactInfoView.initFromPartyContactInfoView(dirPartyContactInfoView);  
        logisticsElectronicAddress = LogisticsElectronicAddressEntity::initFromLogisticsContactInfoView(logisticsContactInfoView, logisticsElectronicAddress);  
   
        if (logisticsElectronicAddress.validateWrite())  
        {  
            logisticsElectronicAddress.insert();  
   
            info("Contatto creato!");  
        }  
    }  
    else  
    {  
        warning("Indirizzo non trovato!");  
    }  
}  

il risultato sarà il seguente:

AX 2012 - Minefield game

In questo post ho provato a riscrivere il gioco "mine field" presente su windows usando l' X++.

L'idea è nata dalla possibilità di poter costruire una form dinamicamente gestendo gli eventi.

Mi sono basato sull'idea di questo post:

https://somarisuax.blogspot.com/2024/04/ax-2012-d365ffo-aggiungere-controlli-ad.html

e di questo per la gestione delle matrici:

https://somarisuax.blogspot.com/2021/01/ax-2012-matrici.html

"L'esperimento" (che lascia il tempo che trova.. :) ) può essere interessante perchè mostra come poter costruire tutto il design via codice.

Il risultato è il seguente:

L'xpo della form da importare può essere scaricato da quì:

https://drive.google.com/file/d/1BhoToxtStJH6TkGR6rbgVus90zJ49mAr/view?usp=sharing

AX 2012 - Lettura file di un certificato e stampa proprietà

 Questo semplice job mostra come leggere un file di un certificato e stampare le varie proprietà:

 static void LIL_CertificateInfo(Args _args)  
 {  
   int                               version;  
   utcDateTime                           NotBefore,NotAfter;  
   System.Security.Cryptography.X509Certificates.X509Certificate2 cert;  
   System.Security.Cryptography.X509Certificates.PublicKey     publicKey;  
   System.Security.Cryptography.Oid                oid;  
   System.Security.Cryptography.AsnEncodedData           asnEncodeddata;  
   System.Security.Cryptography.AsymmetricAlgorithm        AsymmetricAlgorithm;  
   
   cert = new System.Security.Cryptography.X509Certificates.X509Certificate2(System.IO.File::ReadAllBytes(@'C:\Temp\bob.crt'));  
        
   //oppure   
   //cert = new System.Security.Cryptography.X509Certificates.X509Certificate2();  
   //cert.Import(@'C:\Temp\myCert.pfx', 'password', System.Security.Cryptography.X509Certificates.X509KeyStorageFlags::DefaultKeySet);  
   
   version       = cert.get_Version();  
   NotBefore      = cert.get_NotBefore();  
   NotAfter      = cert.get_NotAfter();  
   publicKey      = cert.get_PublicKey();  
   oid         = publicKey.get_Oid();  
   asnEncodeddata   = publicKey.get_EncodedKeyValue();  
   AsymmetricAlgorithm = publicKey.get_Key();  
   
   info(cert.get_Subject());  
   info(cert.get_Issuer());  
   info(strFmt("%1",version));  
   info(strfmt("%1",NotBefore));  
   info(strfmt("%1",NotAfter));  
   info(cert.get_Thumbprint());  
   info(cert.get_SerialNumber());  
   info(oid.get_FriendlyName());  
   info(asnEncodeddata.Format(true));  
   info(cert.ToString(true));  
   info(AsymmetricAlgorithm.ToXmlString(false));  
 }  

How to check/add Cust/Vend Journal transactions to Sales Tax (Italy) report

In AX2012 and D365 there is a specific Italian report "Sales Tax (Italy) report" named "Libro IVA", it contain all transactions about VAT/Sales tax.

By my point of view, an helpful checkpoint, is to veify for each Sales Tax transactions the Posting-parameters.
I'm meaning: Purchase->Invoice Journals; Sales ledger-> Payment Journal and others.
In case we are facing to some transations missing in SalesTax (Italy) Report, the first check is to verify these TaxTrans data:

mandatory fields

The fields are: TaxTrans. TaxBook and TaxTrans.TaxBookSection.
These fields create the link between transactions and Tax Report.

table fields

Report Example

AX 2012 - Fixed default dimension

 Con questo job possiamo ottenere i valori "fixed" sulla default dimension di un conto:

 static void GetFixedDefaultDimension(Args _args)  
 {  
   Map           map;  
   MainAccountLegalEntity MainAccountLegalEntity;  
   MainAccount       mainAccount;  
   MapEnumerator      enumerator;  
   DimensionStorageSegment DimensionStorageSegment;  
   DimensionAttribute   DimensionAttribute;  
   CompanyInfo       companyInfo;  
     
   companyInfo = CompanyInfo::find();  
     
   select firstOnly MainAccountLegalEntity  
     join mainAccount  
     where mainAccount.RecId == MainAccountLegalEntity.MainAccount  
     && mainAccount.MainAccountId == "200100"  
     && MainAccountLegalEntity.LegalEntity == companyInfo.RecId;  
     
   map = DimensionDefaultingService::getFixedDimensionsForMainAccount(MainAccountLegalEntity.MainAccount,MainAccountLegalEntity.LegalEntity);  
     
   enumerator = Map.getEnumerator();  
     
   while (enumerator.moveNext())  
   {  
     DimensionStorageSegment = enumerator.currentValue();    
     DimensionAttribute = DimensionAttribute::find(enumerator.currentKey());  
       
     info(strFmt("%1:%2 -- %3",DimensionAttribute.Name  
                  ,DimensionStorageSegment.parmDisplayValue()  
                  ,DimensionStorageSegment.getName()));  
   }  
 }  

AX2012/D365- HOW TO EXTRACT ALL MAINACCOUNT ALLOCATION RULES by code X++

This article is a merely starting point.
In AX2012 / D365 we can handle the cost allocation by parameters.

Ledger allocation rules are used to automatically calculate and generate allocation journals and account entries for the allocation of ledger balances or fixed amounts. Allocation methods can be variable or fixed. The allocation is based on the transaction currency value.

• We can split the cost to different/several Financial Dimensions (in percentage); By Company etc...

Microsoft documentation:
AX2012:
https://learn.microsoft.com/en-us/dynamicsax-2012/appuser-itpro/create-an-allocation-rule

D365:
https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/ledger-allocation-rules

Data to extract:

what I would like to extract

JOB x++
By code x++ it is possible. The job below can exttract in a infolog the data:
it be can improve

Str1260 mainAccount_Name, DimFinanancial_Name;
MainAccount account;
DimensionAttributeValueSetItem valueSetItem;
DimensionAttributeValue dimAttrValue;
DimensionAttribute dimAttr;
Str1260 dimensionAttributeNames;
LedgerAllocation allocation;
DefaultDimensionView dimensionView;
DimensionAttribute dimensionAttribute; 
   
 while select allocation
 {
     select Name, MainAccountId from account where account.RecId ==    allocation.FromMainAccount;

        mainAccount_Name = account.Name; // to chek the value
      
     while select dimAttr
        exists join dimAttrValue
            where dimAttrValue.DimensionAttribute == dimAttr.RecId
        exists join valueSetItem
            where valueSetItem.DimensionAttributeValue == dimAttrValue.RecId
                && valueSetItem.DimensionAttributeValueSet == allocation.ToDefaultDimension
        {

            DimFinanancial_Name= dimAttr.Name; // to check the value
           
                    select firstOnly dimensionView
                    where dimensionView.DefaultDimension == allocation.ToDefaultDimension
                join dimensionAttribute
                    where dimensionView.Name == dimensionAttribute.Name
                    && dimensionView.Name == DimFinanancial_Name;
      // OUTPUT
            info(strFmt("%1;%2;%3;%4;%5",
            mainAccount_Name, account.MainAccountId,
            DimFinanancial_Name,dimensionView.DisplayValue,allocation.Value));

        }       
    } 

RESULT:

AX 2012 - D365FFO - Aggiungere controlli ad una form dinamicamente e gestire gli eventi (registerOverrideMethod)

In questo post vediamo come aggiungere a run time dei controlli ad una form e gestire gli eventi dei controlli. 

La form di base conterrà un button group a cui aggiungeremo tre pulsanti ed un gruppo a cui aggiungeremo un enumerato ed una stringa. 

Dei tre pulsanti gestiamo l'evento mouseDown (in D365 l'evento mouseDown è deprecato) per capire se il pulsante è stato premuto col pulsante destro oppure col sinistro; dell'enumerato gestiamo l'evento selectionChanged e del campo stringa l'evento modified.

Sia l'aggiunta dei controlli che gli event handler vanno aggiunti nella init della form:

 public void init()  
 {  
   int         i;  
   FormButtonControl  button;  
   FormComboBoxControl comboBox;  
   FormStringControl  stringControl;  
   
   super();  
   
   for(i = 0; i < 3; i++)  
   {  
     button = ButtonGroup.addControl(FormControlType::Button, strFmt("button_%1",i+1));  
     button.text(strFmt("%1",i+1));  
     button.registerOverrideMethod(methodStr(FormButtonControl, mouseDown), identifierStr(buttonMouseDown), this);  
   }  
     
   comboBox = ControlGroup.addControl(FormControlType::ComboBox, "InventCustVend_Combo");  
   comboBox.enumType(enumNum(ModuleInventCustVend));  
   comboBox.registerOverrideMethod(methodStr(FormComboBoxControl, selectionChange), identifierStr(ComboSelectionChange), this);  
     
   stringControl = ControlGroup.addControl(FormControlType::String, "Description_Text");  
   stringControl.extendedDataType(extendedTypeNum(Description));  
   stringControl.registerOverrideMethod(methodStr(FormStringControl, modified), identifierStr(modifiedString), this);    
 }  

I tre event handler vanno aggiunti a livello di form:

 public void buttonMouseDown(int _x, int _y, int _button, boolean _Ctrl, boolean _Shift,FormButtonControl _btn)  
 {  
   switch(_button)  
   {  
     case 1:  
       info(strFmt("hai premuto il bottone '%1' col pulsante %2",_btn.name(),"sinistro"));  
       break;  
   
     case 2:  
       info(strFmt("hai premuto il bottone '%1' col pulsante %2",_btn.name(),"destro"));  
       break;  
   }  
 }  

 public int comboSelectionChange(FormComboBoxControl _comboBox)  
 {  
   info(strFmt("L'enumerato è cambiato %1",_comboBox.selection()));  
     
   return 1;  
 }  

 public boolean modifiedString(FormStringControl _stringControl)  
 {  
   boolean ret = true;  
     
   info(strFmt("nuovo valore '%1'",_stringControl.text()));  
     
   return ret;  
 }  

Tutti i metodi per gestire gli eventi prendono il controllo come parametro. Se l'event prevede altri parametri standard, come nel caso mouseDown, il controllo và aggiunto come ultimo parametro.