Through usage data, a user will automatically be brought into the view of the last template that was used. The user can then save the template for use later. When a template is selected, it will be immediately applied to the user. Of the list of these users, when one is selected (from Figure 5), it will show the user what templates that user has created (Figure 6). The target user can then use the 'Retrieve from user' button in Figure 2 to select from a list of users that have other templates for the current form (Figure 5). Since these modifications are unique to the current user, it may be desired to apply the tireless blood, sweat, and tears that went into a custom template from someone else to another user's form. At any time, the current layout can be cleared and reverted back to the target form without any Intellimorph modifications by clicking the 'Reset' button in Figure 2. Not shown in this blog (sorry) is the option right below this 'Hide' option called 'Show' where the fields hidden by the user can be revealed.Ī given user can store multiple different views of a form (via the 'Save' button in Figure 2) and the template layout can be recalled at any given time for use later (via the 'Load' button in Figure 2). This feature will essentially hide the field from the user. Since the forms displays are unique to a given user, this is good for satisfying requirements for form changes are not universal and the security requirements for field access exist.Īs seen in Figure 1 below, by right-clicking on a field or column (in AX, rows are data and columns are fields), there is the option to select 'Hide'. Technically, it stores the changes to the form in the system's Usage data for the user so all changes are user to user. It is incredibly versatile for allowing multiple users to each see different views without needing to bring in a developer. An example of this is when they say 'You can do that through MorphX development, right?' when they really mean 'Our people can do that through Intellimorph, right?'.ĪX's Intellimorph functionality will allow you to customize what fields the user can see and in what location/order. I hear it often where people call this feature MorphX and it creates a whole bunch of confusion when they reference it assertively for various points. This is not to be confused with MorphX which is AX's IDE and fully contained within the AX 2009 application (in AX 2012, Visual Studio 2012 can be leveraged also). AX has functionality in it which allows end users, not developers, to customize their user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |