Create vendor pending invoices for the invoice pool - using batch job in the Accounts Payable Module.

In D365FO - Creating the vendor pending invoice using batch job:

public void process(VendPendingInvoiceContract _contract)

{

       QueryRun                queryRun;

       LedgerJournalTrans      ledgerTrans;

Query                   query = _contract.getQuery();

boolean                 hasError = false;

        query.dataSourceTable(tableNum(LedgerJournalTrans)).addRange(fieldNum(LedgerJournalTrans, AccountType)).value(queryValue(LedgerJournalACType::Vend));

        query.dataSourceTable(tableNum(LedgerJournalTable)).addRange(fieldNum(LedgerJournalTable, JournalType)).value(queryValue(LedgerJournalType::VendInvoicePool));

        query.dataSourceTable(tableNum(LedgerJournalTable)).addRange(fieldNum(LedgerJournalTable, Posted)).value(queryValue(NoYes::No));

      

        queryRun = new QueryRun(query);

       

        while (queryRun.next())

        {

            try

            {

                ttsbegin;

                ledgerTrans = queryRun.get(tableNum(LedgerJournalTrans));

                if (!ledgerTrans.hasPendingInvoice())

                {

                    this.autoApprovalJournal(ledgerTrans);

                }

                ttscommit;

            }

            catch (Exception::Error)

            {

                if(!hasError)

                {

                    error(strfmt("PendingInvoiceError"));

                    hasError = true;

                }

            }

        }

           

    }

The definition of the auotApprovalJouranl method below:

public void autoApprovalJournal(LedgerJournalTrans _ledgerJournalTrans)

{

    PurchFormLetter             purchFormLetter;

    PurchParmUpdate             purchParmUpdate;

    PurchTable                  purchTableOrig;

       

    purchTableOrig = PurchTable::find(_ledgerJournalTrans.PurchIdRange);

       

    Purchformletter = purchformletter::construct(DocumentStatus::ApproveJournal);

    purchformletter.parmParmTableNum(_ledgerJournalTrans.Invoice);

    purchFormLetter.parmSourceTable(purchTableOrig);

    Purchformletter.parmLedgerJournalTrans(_ledgerJournalTrans);

       

    purchParmUpdate = purchformletter.purchParmUpdate();

    purchParmUpdate.SumNum = _ledgerJournalTrans.Invoice;

    purchformletter.initParameters(purchParmUpdate, Printout::Current);

       

    purchformletter.sumBy(AccountOrder::None);

    purchformletter.showQueryForm(false);

    purchformletter.parmProcessAdditional(true);

    purchformletter.createFromLines(false);

    purchformletter.reArrangeNow(true);

    //purchformletter.reArrange();

    purchformletter.specQty(purchupdate::ALL);

    purchformletter.chooseLines(true);

    VendInvoiceInfoTable::moveFromActiveToSaved(VendInvoiceInfoTable::findRecId(purchformletter.parmLastParmTableRecId()));

}

I hope, you will find in some other blogs - how to create vendor pending invoice for the DocumentStatus::Invoice. I have tried but it is not working for the DocumentStatus::ApprovalJouranl. 

Both process will create pending invoice but, there code is different because they are created from different sources. 

D365FO Data management – CustCustomerEntity export/import financial dimensions small setup step:

When using Microsoft Dynamics 365 for Operations (D365O) Data management – CustCustomerEntity for data export/import, and when financial dimensions are involved, there is a small setup step which must be done prior to export/import.

If this step is not done, the following error is displayed when trying to export/import:

“No active format for data entities has been set up. Set up an active format for each dimension format type.”

Here is how to resolve this error message:

To see the customer’s existing financial dimensions, access the customer list page https://.dynamics.com/?cmp=&mi=CustTableListPageDrill into the customer details using the Financial dimensions fast tab.

In this implementation, we are using 5 financial dimensions, as shown above. Not all dimensions are required to be filled.

In order to successfully export the customer record, we need to set up the format. This is found at General ledger> Chart of accounts> Dimensions> Financial dimension configuration for integrating applications (mi=DimensionIntegrationConfiguration).

1. Add a new default dimension format. In this case, we name it “Customer import”.
2. Use dimension format type “Default dimension format”.
3. Select the financial dimensions which will be exported/imported as part of the Customers data entity.
4. To maintain simplicity, I specifically ordered the financial dimensions in the same sequence (alphabetical) as they appear on the customer details form (shown on previous image).
5. The system will display a format example. This is comprised of the selected dimensions separated by a hyphen.
6. Set the format “Active for type”.

Now, when exporting the customer record, we see that the financial dimension is displayed properly.

Use the same format for entering data into a spreadsheet for import using Data management – CustCustomerEntity.

Important: Note that the hyphen separator is always required, even if no value is provided for a dimension (see first line, where both the first and fifth dimensions are not specified).

Data Management import or export error in D365FO:

Hi All,

In order to fix the below issue in Data Management D65FO:

when i am trying to import or export getting below error 

System.Exception: Exception from HRESULT: 0xC0000033
at Microsoft.Dynamics.AX.Framework.Tools.DMF.ServiceProxy.DmfEntitySharedTypesProxy.DoWork[T](Func`1 work)
at Dynamics.AX.Application.DMFGenerateSSISPackage.`generateFileDataV2(DMFDefinitionGroupExecution _dmfDefinitionGroupExecution, String _defGroupName, DMFFileFormat _fileFormat, DMFDelimiter _rowDelimiter, DMFDelimiter _columnDelimiter, String _codePage, String _locale, NoYes _isFirstRowHeader, NoYes _unicode, String _source, String _textQualifier, DMFXMLStyle _style, String _rootElement, String _filePath, Map _entitySyncVersion, Int32 _previewCount, Boolean @_entitySyncVersion_IsDefaultSet, Boolean @_previewCount_IsDefaultSet) in xppSource://Source/ApplicationFoundation\AxClass_DMFGenerateSSISPackage.xpp:line 1230

Solution: updated  SQL Server Licence in all AOS Machines and SQL Server Machine.  

How to enable access into the environment by specifying which IPs in D365:

Enable access into the environment by specifying which IPs can access the environment for a given service type.

1. Go to LCS for your project.
2. Go to Maintain - Enable access as below.

3. enter the public IP to connect to the RDP.

How to get the User Date Sequence in Axapta2012 / D365OF:

Normally, we specify 123 or 321 sequence in str2Date(). But, in order to get the sequence randomly the below code is useful:

static int userDateSequence()
    {
        int     ds1, ds2, ds3;
        date    d = str2Date('2015/12/18', 321);
        str     s = strFmt('%1', d);


        void datepart(str strDate, str dval, int part)
        {
            if (strEndsWith(strDate, dval))
            ds3 = part;
            else if (strStartsWith(strDate, dval))
            ds1 = part;
            else
            ds2 = part;
        }

        datepart(s, '18', 1);
        datepart(s, '12', 2);
        datepart(s, '2015', 3);

        return ds1 * 100 + ds2 * 10 + ds3;
    }

How to fetch HSNCode in Ax2012 Indian GST Microsoft Hotfix:

In order to get the value of HSN code in Ax2012, we should know where exactly the HSN code is attached?
1. Normally, HSN code is attached to each item on the Item master under Foreign tab.
2. At the sales or purchase order line under Tax information-GST Tab, the HSN code can be manually selected by user.

The list of tables which has reference to other tables below:

TaxDocument has a reference to SalesTable.
TaxDocumentExtension_IN has a reference to TaxDocument.
TaxDocumentRow has  reference to SalesLine.
TaxDocumentRowTransaction has a reference to CustInvoiceTrans, CustInvoiceJour.
SalesLine_IN has a reference to SalesLine.

TaxDocumentRowTransaction_IN has the HSN code, which will have reference to TaxDocumentExtension_IN and TaxDocumentRowTransaction.

The below code is used to fetch the HSN Code:
//Normally, HSNCode if fetched from the InventTable but otherwise, it will also be fetched from salesline level.:

TaxDocumentRowTransaction       taxDocumentRowTransaction;
TaxDocumentRowTransaction_IN    taxDocumentRowTransaction_IN;
SalesTable                  salesTable;
SalesLine_IN                salesLine_IN;

salesLine_IN    = custInvoiceTrans.salesLine().salesLine_IN();
//TmpSalesPurchRegister is my buffer table.

//TmpSalesPurchRegister.Intracode     = HSNCodeTable_IN::find(InventTable::find(TmpSalesPurchRegister.ItemId).HSNCodeTable_IN).Code;
            Select RecId, TransactionJourLineRecId from taxDocumentRowTransaction
                where taxDocumentRowTransaction.TransactionJourLineRecId == custInvoiceTrans.RecId
            join HSNCode, TaxDocumentRowTransactionRecId from taxDocumentRowTransaction_IN
                where taxDocumentRowTransaction_IN.TaxDocumentRowTransactionRecId == taxDocumentRowTransaction.RecId;
            if(taxDocumentRowTransaction_IN)

            /*select * from taxTrans where taxTrans.SourceRecId == custInvoiceTrans.RecId
            join taxTrans_IN where taxTrans_IN.RefRecId == taxTrans.RecId;
            if(taxTrans_IN)*/
            {

                TmpSalesPurchRegister.Intracode = taxDocumentRowTransaction_IN.HSNCode;
                //TmpSalesPurchRegister.Intracode = HSNCodeTable_IN::find(taxTrans_IN.HSNCodeTable).Code;
            }
            else
            {
                TmpSalesPurchRegister.Intracode = HSNCodeTable_IN::find(salesLine_IN.HSNCodeTable).Code;
            }

Import and Export a configuration model in D365(xml file) for custom fields.

Export:

[ExtensionOf(classStr(PcModelVisitorExport))]

final class PCModelVisitorExport_Extension
{
    public void visitStart(Common _record)
    {
        next visitStart(_record);       

        if (_record is EcoResAttribute)
        {
            if ( this.writeComponent() )
            {
                EcoResAttribute ecoResAttribute = _record;

                this.writeFieldValueInt(ecoResAttribute, fieldId2name(ecoResAttribute.TableId, fieldNum(EcoResAttribute, NoPrint)), ecoResAttribute.NoPrint);
            }
        }

        if (_record is PCPriceExpressionValue)
        {
            PCPriceExpressionValue  priceExpressionValue = _record;

            this.writeFieldValue(priceExpressionValue, fieldId2name(priceExpressionValue.TableId, fieldNum(PCPriceExpressionValue, SalesOptionId)), priceExpressionValue.SalesOptionId);
        }

        if (_record is PCPriceExpressionRule)
        {
            PCPriceExpressionRule  priceExpressionRule = _record;

            this.writeFieldValue(priceExpressionRule, fieldId2name(priceExpressionRule.TableId, fieldNum(PCPriceExpressionRule, SalesOptionId)), priceExpressionRule.SalesOptionId);
        }
    }   


}

Import:

[ExtensionOf(classStr(PCImportComponentAttributeHandler))]
final class PCImportComponentAttributeHandler_Extension
{
    protected void importData()
    {
        #define.NoPrint('NoPrint')

        next importData();
               
        ttsbegin;

        attribute.Selectforupdate(true);
        attribute.NoPrint   = this.getIntFieldByName(#NoPrint);
        attribute.update();

        ttscommit;       
    }

}

[ExtensionOf(classStr(PCImportPriceExpressionRuleHandler))]
final class PCImportPriceExpressionRuleHandler_Extension
{
    protected void importData()
    {
        #define.SalesOptionId('SalesOptionId')

        next importData();

        ttsbegin;

        expressionRule.Selectforupdate(true);
        expressionRule.SalesOptionId    = this.getFieldByName(#SalesOptionId);
        expressionRule.update();

        ttscommit;
    }

}