Hi Mary,
You can refer VSS integration with Microsoft Dynamics Ax document at partner source. There is a proper setup that one has to do with in Dynamics Ax to make use of VSS in development process. You can also use earlier object locking functionality in Dynamics Ax also but there is a different way around for this. Follow the following steps for object locking functionality: 1) To Enable Object locking/unlocking utility Go to AOTàFormsàSysUtilLocksàDataSourcesàUtilLocksàProperties (Set AllowEdit and AllowCreate as "Yes") 2) Now to lock or unlock any object go to ToolsàDevelopment toolsàApplication objectsàLocked application Objects a. Add new record with details of Element (object type), Name (object name) and userid. Exp: Element - Forms, Name - CustTable, UserID - Admin. Now with this setting CustTable form will be considered locked by Admin. b. To unlock an object delete respective record against respective userid. I know this is a long process but one can also write his/her own script to add respective options in context menu for the same. This was just an alternative way for effective development but better approach is always to go with standards of Dynamics Ax set Microsoft and make use of VSS. Thanks, Vikas Garg Tectura Tel: (+91) 120 3051900 Mobile: (+91) 92431 20951 From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MaryAnn Hand Sent: Wednesday, May 16, 2007 4:45 PM To: [email protected] Subject: [development-axapta] AX4 - no more ability to set locking property on an object? In Axapta 3.0, you could lock objects you are working on. In AX4, this does not seem possible. Is it? And I just cannot see how? Is it now linked to Source Control integration? Mary Ann [Non-text portions of this message have been removed]
