{"id":6,"date":"2017-04-04T03:25:04","date_gmt":"2017-04-04T03:25:04","guid":{"rendered":"http:\/\/bakke.online\/?p=6"},"modified":"2017-04-04T03:25:04","modified_gmt":"2017-04-04T03:25:04","slug":"show-environment-bar-in-dynamics-ax-forms","status":"publish","type":"post","link":"https:\/\/www.bakke.online\/index.php\/2017\/04\/04\/show-environment-bar-in-dynamics-ax-forms\/","title":{"rendered":"Show environment bar in Dynamics AX forms"},"content":{"rendered":"

When working with multiple Dynamics AX environments, it’s quite useful to have a visual reminder of which environment you’re working in.<\/p>\n

It is possible to use the instance name in the client configuration to provide this hint, but the instance name is not validated, nor does it indicate to the client which instance to connect to. \u00a0The connection is established only based on the host name, port name and WSDL port. \u00a0It is, in fact, possible to specify anything at all as the instance name:<\/p>\n

\"\"<\/p>\n

My production server does NOT have an instance named MickeyMouse. \u00a0I promise… \u00a0Really…<\/p>\n

Connecting to the AX instance shows this in the status bar:<\/p>\n

\"\"<\/p>\n

This also relies on the user having enabled this information to be shown in the status bar, and even if they have, this will eventually come to bite you when you start copying configurations and configuration files, so a better solution is needed.<\/p>\n

The following shows how to add an information bar at the bottom of each form, like this:<\/p>\n

\"\"<\/p>\n

This has been developed and tested on AX2012R3, but it will most likely work unchanged or with only minor changes on other versions of AX2012, possibly even on AX2009 and older, although more substantial changes are likely to be necessary. \u00a0The general concept would remain the same, though.<\/p>\n

First we need to add a couple of local members to the SysSetupFormRun class:<\/p>\n

\/\/ This is a framework class. Customizing this class may cause problems with future upgrades to the software.<\/em><\/span>\npublic class<\/strong><\/span> SysSetupFormRun extends<\/strong> <\/span>FormRun\n{\n SysWorkflowFormControls workflowControls;\n \/\/ <GEERU>\n \/\/ Event listeners list\n<\/span><\/em> List listeners_W;\n \/\/ <\/GEERU><\/span><\/em>\n\n \/\/ EB 11\/02\/2016: Add environment indicator ==><\/em><\/span>\n FormGroupControl EB_envBottomGroup;\n FormWindowControl EB_envImage;\n FormStaticTextControl EB_envStatic;\n FormButtonControl EB_envHideButton;\n \/\/ EB 11\/02\/2016: Add environment indicator <==<\/em><\/span>\n\n#if<\/strong><\/span>.never\n #define.CurrentVersion(1<\/strong><\/span>)\n #localmacro.CurrentList\n #endmacro\n#endif\n}<\/pre>\n
Next, override the run() method, to make sure that the elements needed for the environment indicator are created every time a form is opened.<\/p>\n
\/\/ EB 11\/02\/2016: Add environment indicator<\/em><\/span>\npublic void<\/strong><\/span> run()\n{\n  str<\/strong> <\/span>message;\n  int<\/strong> <\/span>rgb;\n  str<\/strong> <\/span>dbName;\n\n  super<\/strong><\/span>();<\/pre>\n
The first thing I’m\u00a0going to do is to call super() to let the system initialise the form, before I start customising it.<\/p>\n
Next I’m checking what type of form this is. \u00a0We don’t want to show the indicator on embedded forms such as web parts, drop dialogs, etc. \u00a0This code makes sure it only shows on traditional forms and list pages.<\/p>\n
if<\/strong><\/span>( this.isDetached() && ( this.design().style() != FormStyle::DropDialog ) )\n {<\/pre>\n
In my case, I can determine which environment I’m running in by checking the database name, as we have a consistent naming convention around here. \u00a0I choose a suitable text and colour based on the database name returned.<\/p>\n
dbName = SysSQLSystemInfo::construct().getloginDatabase();\ndbName = subStr<\/strong><\/span>( dbName, strFind<\/strong><\/span>( dbName, \"_\"<\/span>, 1<\/strong><\/span>, strLen<\/strong><\/span>( dbName ) ) + 1<\/strong><\/span>, strLen<\/strong><\/span>( dbName ) );\n\nswitch<\/strong><\/span>( dbName )\n{\n  case<\/strong> <\/span>\"Dev\"<\/span>:\n    message = \"Development environment - Be prepared for weirdness and random crashes\"<\/span>;\n    rgb = WinAPI::RGB2int( 160<\/strong><\/span>, 240<\/strong><\/span>, 255<\/strong> <\/span>);\n    break<\/strong><\/span>;\n  case<\/strong> <\/span>\"Test\"<\/span>:\n    message = \"Test environment\"<\/span>;\n    rgb = WinAPI::RGB2int( 160<\/strong><\/span>, 255<\/strong><\/span>, 160<\/strong> <\/span>);\n    break<\/strong><\/span>;\n  case<\/strong> <\/span>\"Staging\"<\/span>:\n    message = \"Staging environment\"<\/span>;\n    rgb = WinAPI::RGB2int( 255<\/strong><\/span>, 255<\/strong><\/span>, 0<\/strong><\/span> );\n    break<\/strong><\/span>;\n case<\/strong> <\/span>\"Live\"<\/span>:\n   return<\/strong><\/span>;\n }<\/pre>\n
Next I’m going to add the controls to the form through X++ code.<\/p>\n
EB_envBottomGroup = this.design().addControl( FormControlType::Group, \"EB_envBottomGroup\"<\/span> );\nEB_envImage = EB_envBottomGroup.addControl( FormControlType::Image, \"EB_envImage\"<\/span> );\nEB_envStatic = EB_envBottomGroup.addControl( FormControlType::StaticText, \"EB_envStatic\"<\/span> );\nEB_envHideButton = EB_envBottomGroup.addControl( FormControlType::Button, \"EB_envHideButton\"<\/span> );<\/pre>\n
EB_envBottomGroup is a group control that will contain the other controls. \u00a0I size and style it before moving on to the other controls.<\/p>\n
EB_envBottomGroup.widthMode( FormWidth::ColumnWidth );\nEB_envBottomGroup.heightMode( FormHeight::Auto );\nEB_envBottomGroup.colorScheme( FormColorScheme::RGB );\nEB_envBottomGroup.backStyle( FormBackStyle::Opaque );\nEB_envBottomGroup.backgroundColor( rgb );\nEB_envBottomGroup.frameType( FormFrameType::None );\nEB_envBottomGroup.topMargin( 5<\/strong><\/span> );\nEB_envBottomGroup.bottomMargin( 0<\/strong><\/span> );\nEB_envBottomGroup.leftMargin( 5<\/strong><\/span> );\nEB_envBottomGroup.rightMargin( 5<\/strong><\/span> );<\/pre>\n
EB_envImage is just an icon, used to make the indicator bar a bit more interesting. \u00a0Completely optional, of course. \u00a0I am using resource ID 918 here, but if you want a different one, have a look through the embedded resources by using the tutorial_Resources form.<\/p>\n
EB_envImage.width( 15<\/strong><\/span>, FormWidth::Auto );\nEB_envImage.height( 15<\/strong><\/span>, FormHeight::Auto );\nEB_envImage.leftMode( FormLeft::LeftEdge );\nEB_envImage.imageResource( 918<\/strong> <\/span>);\nEB_envImage.imagemode( 1<\/strong><\/span> );\nEB_envImage.backStyle( FormBackStyle::Transparent );\nEB_envImage.showLabel( false<\/strong> <\/span>);<\/pre>\n
Next, EB_envStatic is a static text control where I display the environment indicator text.<\/p>\n
EB_envStatic.alignment( FormAlignment::Center );\nEB_envStatic.fontSize( 10<\/strong> <\/span>);\nEB_envStatic.text( message );<\/pre>\n
The final control is a button which can be used to hide the environment indicator. \u00a0Perhaps it is taking up too much space, or it needs to be hidden in order to do a screen shot. \u00a0For whatever reason, it is good practice to allow the user to hide it when necessary. \u00a0I’m using resource ID 8008 here, which is a small “Close” icon. \u00a0Use whatever other icon you want, but be mindful of the size of the environment bar. \u00a0It should not be too large, or it will take up too much space, and some icons don’t scale that well to small sizes.<\/p>\n
EB_envHideButton.width( 15<\/strong><\/span>, FormWidth::Auto );\nEB_envHideButton.height( 15<\/strong><\/span>, FormHeight::Auto );\nEB_envHideButton.leftMode( FormLeft::RightEdge );\nEB_envHideButton.normalResource( 8008<\/strong> <\/span>);\nEB_envHideButton.buttonDisplay( FormButtonDisplay::ImageOnly );\nEB_envHideButton.backStyle( FormBackStyle::Transparent );\nEB_envHideButton.style( ButtonStyle::Link );<\/pre>\n
Finally, we have to register an override method so we can capture the click event and actually hide the environment indicator.<\/p>\n
    EB_envHideButton.registerOverrideMethod( methodStr<\/strong><\/span>( FormButtonControl, clicked ), methodStr<\/strong><\/span>( SysSetupFormRun, EB_hideEnvButton_Clicked ), this );\n  }\n}<\/pre>\n
That’s it for the run method. \u00a0Now add a new method to the SysSetupFormRun class and call it EB_hideEnvButtonClicked. \u00a0(Of course, the actual prefix is totally up to you and the naming conventions you follow.)<\/p>\n
\/\/ EB 11\/02\/2016: Add environment indicator<\/span><\/em>\npublic void<\/strong><\/span> EB_hideEnvButton_Clicked( FormWindowControl _caller )\n{\n  EB_envBottomGroup.visible( false<\/strong> <\/span>);\n}<\/pre>\n
That’s it. \u00a0Recompile the class and update the CIL code. \u00a0Users will then get the environment indicator at the bottom of their forms.<\/p>\n
Please, make sure you do this in a dev\/test environment first, and test it before loading to production.<\/p>\n
An XPO containing this modification is available here:\u00a0Class_SysSetupFormRun.zip<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
When working with multiple Dynamics AX environments, it’s quite useful to have a visual reminder of which environment you’re working in. It is possible to use the instance name in the client configuration to provide this hint, but the instance name is not validated, nor does it indicate to the client which instance to connect … Continue reading “Show environment bar in Dynamics AX forms”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,1],"tags":[2,3,5],"class_list":["post-6","post","type-post","status-publish","format-standard","hentry","category-dynamics-ax","category-uncategorized","tag-ax2012r3","tag-dynamics-ax","tag-user-interface"],"_links":{"self":[{"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/posts\/6","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/comments?post=6"}],"version-history":[{"count":0,"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/posts\/6\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/media?parent=6"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/categories?post=6"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bakke.online\/index.php\/wp-json\/wp\/v2\/tags?post=6"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}