Microsoft Dynamics 365 and Power Platform Library

Data security has always been the main concern of every organization, implementing MS Dynamics AX. I will not increase the length of the post by going into details of "How to's" of security setup in Dynamics AX. Attached manual is providing the brief of security and is very useful to understand the basics of security in AX. Microsoft Dynamics Ax Security

This post has been copied from  http://devexpp.blogspot.com/2012/02/refresh-datasource-and-retain-position.html Refresh a DataSource is a very common task to Dynamics AX developers, as you'll most likely perform changes on a record and have to present it to the user, on a form . The most commonly used method to refresh the DataSource to make a form show what you have changed on a record is the research  method. The only problem is that the  research  method doesn't retain the record that was selected, it positions the DataSource on the first record of the result, causing the user to see another record. To resolve this matter, the research method, only in Dynamics AX 2009, has a boolean parameter, retainPosition. Now if you call it by passing true to it, it will sure retain the position of the selected record after the refresh, right? Wrong... This should only work when your form has DataSources linked by Inner Joins in it, what mea...

DataSetViewRow  row; row = AxDatasource.GetDataSet().DataSetViews["DataSetViewName"].GetCurrentRecord(); // Get old value row.GetFieldValue("FieldName"); // Set new value row.BeginEdit(); row.SetFieldValue("FieldName", NewValue); row.EndEdit();

Sometime we are in need of retrieving data from the tables which are not added in form's datasource in EP page. To manipulate the data from tables other than datasource (in EP) or dataset (in AX), following code will work.

Here you can have the list of code sample of Microsoft Dynamics AX, AIF and EP http://archive.msdn.microsoft.com/axcodesamples

It really made the process faster to test the user control without going to EP pages and refresh the AOD and data files again and again. http://msdn.microsoft.com/en-us/library/cc616458.aspx

I found a very comprehensive article on MSDN about the subjected line of the post. http://msdn.microsoft.com/en-us/library/ee677497.aspx