tag:blogger.com,1999:blog-954811220271201663.post3173809614167259677..comments2024-02-27T07:17:38.402+02:00Comments on F.A.Q. for Dynamics AX: SysOperation dialog displaying values from callerAnonymoushttp://www.blogger.com/profile/00924659236536987465noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-954811220271201663.post-79116738650957871672015-09-10T11:47:32.646+03:002015-09-10T11:47:32.646+03:00Hi Martin,
True, it's just that I didn't ...Hi Martin,<br /><br />True, it's just that I didn't want to allocate a new variable in the example; however, the complexity of the code would indeed be reduced if we were to use the as operator.<br /><br />Thanks.Anonymoushttps://www.blogger.com/profile/00924659236536987465noreply@blogger.comtag:blogger.com,1999:blog-954811220271201663.post-91443479683386281452015-09-10T10:13:57.201+03:002015-09-10T10:13:57.201+03:00You could make your code simpler and more readable...You could make your code simpler and more readable with the "as" operator:<br /><br />parentRec = args.record() as ITRParentA;<br />if (parentRec)<br />{<br /> contractA.parmValue(parentRec.Value);<br />}Martin Drábhttps://www.blogger.com/profile/08011302098850273578noreply@blogger.com