Dynamics NAVAX

The workflow history form is designed in a way where if you are a user in the Admin user group, you get view 1. If you are a user that is not in the Admin group, then you get view 2. Workflow history - for admin Workflow history - for non admin Note:  It checks the user by looking for the first usergroup in their list. If there is a user group which sorts higher than "Admin" then it will think you are not an Admin.

Ola Hallengren has updated his site to take care of SQL2008R2. That is some great work he has done. Specially considering he is giving it out for free. http://ola.hallengren.com

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...

Application consultants Supply Chain Management in Dynamics AX http://blogs.msdn.com/b/dynamicsaxscm/ Dynamics AX Training http://www.dynamicsaxtraining.com/trade-and-logistics-training Dynamics AX (General AX news and tips) http://dynamics-ax.blogspot.com/ Technical consultants MFP’s two cents http://blogs.msdn.com/b/mfp/ Dynamics AX tools and tutorials http://kashperuk.blogspot.com/ Workflow http://workflowax.wordpress.com/ EMEA Dynamics AX Support http://blogs.msdn.com Good AIF articles http://www.ksaelen.be/wordpress/ Dynamics AX Sustained Engineering http://blogs.technet.com Saveen Reddy's blog (good SSRS articles) http://blogs.msdn.com AX Daily (regular small useful tips and tricks) http://axdaily.blogspot.com/ AX Performance http://blogs.msdn.com/axperf Issues concerning x++ http://blogs.msdn.com/x The Microsoft Dynamics AX  Enterprise Portal Blog http://blogs.msdn.com/epblog Useful AIF Links around http://daxdilip.blogspot.com/2010/05/aif-li...

Issue: I tried to setup a workflow configuration based on the Project field on the purchase requisition. For some reason the Project field was looking up the dimensions. I had a look at what dimensions I had in the system and I found the 4th dimension was called Project too. Because the workflow class builds a list on the field names. It only adds 1 field called Project. In other words, only allowing you to select 1 of the two fields labelled Project. Solution: I renamed the dimension to "Project No". Something different.

Today I learned a new class which I think is great. http://msdn.microsoft.com/en-us/library/cc639186.aspx The MultiSelectionHelper class provides an interface to work with multiple selected records on a form data source. Say you want to highlight a number of records and run a function against them. Here is some sample code: public void initFromArgs(Args _args = this.parmArgs()) { MultiSelectionHelper multiSelectionHelper; PurchReqTable purchReqTable; ; if (args && args.caller() && args.record()) { multiSelectionHelper = MultiSelectionHelper::createFromCaller(args.caller()); multiSelectionHelper.createQueryRanges(queryRun.query().dataSourceTable(tablenum(PurchReqTable)), fieldstr(PurchReqTable, PurchReqId)); switch(args.record().TableId) { case tablenum(PurchReqTable) : purchReqTable= multiSelectionHelper.getFirst(); while (purchReqTable) { ...

This error usual happens when you put a large block in the footer section or you have set the footer section height too high. Solution would be to adjust the height of the footer section or remove/reduce what you have on the footer section. Or alternatively move your controls to a programmable section. I would do the latter if I am displaying a large block of text. For example terms and conditions at the end of a purchase order report.