|
12.08.2008, 19:05 | #1 |
Участник
|
gatesasbait: "Go to the Main Table Form" differences between Axapta 2.x and Dynamics AX 4
Источник: http://gatesasbait.spaces.live.com/B...B9F5!242.entry
============== Good morning, The "Go To Main Table Form" functionality in Axapta used to filter on the child form for the calling record, as well as update as the parent form changed record. In AX 4 that is no longer the case, though child forms opened through menuitem buttons do still behave this way. What happens is that in AX 4, the calling record is no longer passed in args.record() (therefore, linkActive() is no longer triggered on the child datasource); the args members lookupField() and lookupValue() are populated instead with the calling control's information. If for some reason you want to get back to the jumpref() behavior of Axapta 2.x, add the following code to the SysSetupFormRun class new() method. You may want to create a per-user parameter to enable/disable this feature: void new(Args args) { (...) SysSetupFormRun formRun; ; if (!args.record() && args.lookupField() && SysUserInfo::find().MyNewJumpRef2xNoYesParameter && SysDictClass::is(args.caller(), classnum(SysSetupFormRun))) { formRun = args.caller(); if (formRun.objectSet() && formRun.objectSet().cursor()) { args.record(formRun.objectSet().cursor()); } } super(args); (...) } Источник: http://gatesasbait.spaces.live.com/B...B9F5!242.entry
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|