Ali Raza Zaidi

A practitioner’s musings on Dynamics 365 Finance and Operations

X++ tips

Data Manipulation in Dynamics Ax 2012- Array as Extended Data Type

by

I found a array based field in TSTimesheetLineWeek table, Field TSWeeklyHours

Now challenge is to enabled field based on Array. For example need to disabled on day 6.

Following code snippet help me to enabled disabled fields generated on the base of array extended Type

TSTimesheetLineWeek_ds.object(fieldId2Ext(fieldNum(TSTimesheetLineWeek, Hours), 6)).allowEdit(false);

Reference :

https://msdn.microsoft.com/en-us/library/aa675074.aspx

https://docs.microsoft.com/en-us/previous-versions/dynamicsax-2009/developer/aa592700(v=ax.50)

Relation between VendPackingSlipJour and PurchParmTable Dynamics Ax 2012 R3

by

Couple of days ago, I was helping a young developer. Who was doing some customization. He added some customization in PurchParmtable and want information in VendPackingSlipJour Table.

It was very strange that there is no direct relationship between vendPackingSlipJour and  PurchParmTable.

 

After Exploring I found that There is ParmId field in VendPackingSlipVersion table.

And we can get VendPackingSlipVersion by static method with PurchId and PackingSlipId, DeliveryDate.

 

This ParmId has relation with PurchParmTable.

I wrote down following code snippet to get Value from PurchParmTable, with respect to VendPackingSlipVersion.

 

 

 

display real _netWeight()
{
PurchParmTable _purchParmTbl;
parmid _id;
_id=VendPackingSlipVersion::findFromInterCompanyPackingSlip((this.PurchId),
(this.PackingSlipId),(this.DeliveryDate)).ParmId;
select *from _purchParmTbl where _purchParmTbl.ParmId==_id;
return _purchParmTbl.NetWeght;
}

 

Hopes this help

Select on InventSum vs InventOnHand Class Dynamics Ax 2012 R3.

by

Today I face the very strange behavior of X++ code.

We develop customization. We generate transfer and issuance through X++.

Logic was very simple,If stock is available then transfer  / Issuance or Adjustment journal create otherwise generate error message, We took this decision  based of query on Inventsum. It works fine in most of cases but In one case when stock is zero it fails. We create Movement Journal to generate stock in that Item variant.  The select query always return Zero stock in posted quantity. Even I get the recid in debug mode and placed in table explorer, Quantity is available in table explore.

This case occurs when got Zero stock in Inventsum table and we try to increase stock by movement journal, other wise select on InventSum works fine.

 

The query will be very similar

 

Select * from InventSum where Inventsum.ItemId == line.ItemId && inventSum.invetdimId == line.fromInventiDimId;

 

This will not work. Even Db synch, Inc Cil, Cache clear done, even Restart the Test server AOS.

 

I have to switch code from select query to Class InventOnhand. Very similar to following.

 

InventOnHand inventOnhand

InventDim       InventDim;

InventDimParm inventDimParm;

 

 

inventDimParm.initFormInventDim(_Line.FromInventDimId);

inventOnHand = InventOnhand::newParameters(_line.Itemid,_line.FromInventDimId,inventDimParm);

 

If (inventOnHand.availPhysical() > _line.RequestedQty)

{

Info( ” Quantity Avalible “);

}

Else

{

Info (” Not available “);

}

 

Its works perfectly fine. I think  InventonHand class is better the do direct query on Inventsum table.