Solution Architecture Visit our Focus Rooms Evaluation of Implementation Proposals by Dynamics AX R&D Solution Architecture & Industry Experts Gain further insights on Dynamics AX Industry Solution Offerings Resolution Guidance on Solution Roadblocks Networking Manufacturing Public Sector Services Industries Retail Solution Architecture Risso 6A/B Risso 6C Risso 7A Risso 7B Risso 8A

NICE, FRANCE TECHNICAL CONFERENCE 2011 LEARN | INSPIRE | INNOVATE

Code Upgrade for Developers SESSION CODE : BRK221 Code Upgrade for Developers Andrew Jewsbury Senior Program Manager Microsoft Corporation

Today we will show you… Planning for a successful code upgrade Code Upgrade Checklist Code Upgrade Service for Microsoft Dynamics AX 2012 (Beta) Security Upgrade Advisor (Beta)

Components in action today Industry Sector Applications Manufacturing Distribution Retail Services Sector Public Sector Horizontal Applications CPM & GRC CRM HCM: HR & Payroll SRM Financials SCM Inventory Projects Application Foundation Reference Data Master Data Application Primitives Framework Upgrade Framework Clients Servers Tools Technology Stack

Pains and challenges Nandita – In-house Developer Need to effectively plan for and execute an upgrade Viktor – Business System Developer Isaac – ISV Developer

Concepts & Definitions <List the concepts & definitions required to use & implement the feature(s)>

When to use the Feature Upgrading metadata to Dynamics AX 2012

Planning for a Successful Code Upgrade Investigate your features to see which ones are to carry forward What new features replace your existing ones What features are not used often (UI elements) Be Careful: Do not remove schema (may cause data loss) Be Careful: Lower-layer element may have dependencies in higher layers Understand the Microsoft changes that impact your upgrade Merge layers before you start an upgrade (where possible)

Executing a Successful Code Upgrade Do not upgrade with XPOs – Always use AOD/model files Back up often, both as model files and the database Complete the lowest-layer upgrade first before moving to the next highest layer For form, remove customizations and pull over element from baseline or reapply customizations Do not merge Upgrade in dependency order (Enum -> EDT -> Tables -> Code -> UI) Fix your schema first, then code, then UI Enum EDT Table Code UI

E2E Process : Product Demo (How to Use the Feature) E2E Name : Plan, Import and Upgrade Code DEMO 1: Code Upgrade Checklist Prepare AX for your Code Upgrade Conflict Detection Tool Isolating metadata DEMO 2: Code Upgrade Service for Microsoft Dynamics AX 2012 [Beta] Automatically fix upgrade patterns Group patterns into categories Get suggestions on how to fix code upgrade patterns DEMO 3: Security Upgrade Service [Beta] Quick and secure start on AX 2012 by leveraging existing Security Investments Project Mobilization Analysis Preparation Import Layer Upgrade Code Security Next Layer Test Go Live Configuration

Demo 1 : Code Upgrade Checklist Persona Pain Points and Challenges Features Covered Results and Benefits Issac AX metadata changes across releases and can cause instability during upgrade Setting up AX Baseline Model Store Upgrading layer by layer Structured checklist ensures metadata is correctly set up for an upgrade

AX6.0 Developer Conference January 17-20, 2011 4/24/2017 BASELINE Model Store Microsoft Dynamics AX 2009 database Microsoft Dynamics AX 2012 database 2009 ISV 2012 ISV 2009 ISV 2009 ISV Add cylinder for 6.0 model and label them Replace cylinder with box Readonly baseline – talking point 2009 SYS 2009 SYS 2012 SYS BASELINE DATABASE © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Conflict Detection Tool Persona Pain Points and Challenges Features Covered Results and Benefits Issac Understand the Microsoft changes that impact your customizations Isolating metadata via a 3-way compare Compare form allows analysis of old and new layers Isolate your specific customizations and merge them into AX 2012

Demo 2 : Code Upgrade Service for Microsoft Dynamics AX 2012 [Beta] Persona Pain Points and Challenges Features Covered Results and Benefits Issac Repetitive upgrade patterns No suggestions on how to fix upgrade patterns Tasks are grouped into one large activity Running tool on table and class methods Grouping patterns in an AX project Fixing patterns based on the Description provided Auto-fixing patterns via the customized Compare form Adding new rules Automatically fix code to save manual work Provide suggestions on code patterns Segment tasks by category Extensible by 3rd parties

Security Upgrade Advisor TechReady13 4/24/2017 Security Upgrade Advisor What entails upgrading security settings to AX 2012? Overview of security in AX 4.0/2009 and AX 2012 Comparison of security artifacts between two versions Security Upgrade Advisor Demo Why do we need to talk about security upgrade? Security architecture has been altered in this version, any security settings you previously had will NOT automatically migrate to this version. So, our main goal here is to ensure you are comfortable with understanding of security upgrade. The goal is to automate as much as possible. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Security Model: AX 4.0 and AX 2009 TechReady13 4/24/2017 Security Model: AX 4.0 and AX 2009 e.g. “Branch Manager”, “Europe” e.g. “CustomerTable” User Group/Domain Security Key Security Key e.g. “CustomerTable”, “Read” Security in AX 2009 for a user starts with his or her membership in a user group. By adding a user to a group, you grant that user all the permissions assigned to that group. Domains enable you to restrict permissions to user groups to a single company, or to set up user groups that have permissions to data across companies.   Furthermore, access of users to system elements (such as forms, menu items, and tables) is controlled using security keys. These settings are set by managing user group and domain combinations. Lastly, the security keys themselves can have child security keys. Ultimately, they control access to a securable object, set with an access level. Access Level Securable Object Access Level Securable Object © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Security Model: AX 2012 Roles (80) Duties (767) Privileges (5777) Group of duties for a job function e.g. “Branch Manager” Group of related privileges required for a job function e.g. “Basic Duties” Duties (767) Process Cycle Group of entry points with associated access levels e.g. “View Customer Records” Privileges (5777) Group of base objects and required permissions e.g. “CustomerTable” Permissions (20,000+)

Security Model: Side By Side TechReady13 4/24/2017 Security Model: Side By Side Branch Manager Basic Duties View Customer Records Role Duties Privilege Permissions for CustomerTable User Permission CustomerTable, Read We are not even looking at securable objects. Only entry points User Group/Domain Securable Object Access Level Branch Manager/Europe © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Security Upgrade: Approach and Goal TechReady13 4/24/2017 Security Upgrade: Approach and Goal Generate custom roles for each user group in legacy system Find privileges for menu items to which user groups were granted permissions on legacy system Analyze data at every step Iterate through the process to fine-tune results Quick and Secure start on AX 2012 by Leveraging existing Security Investments Access to data within the system for an AX user flows through an entry point like a menu item. The algorithm essentially looks for entry points in the legacy system, looks at it access level and find privileges that map to the entry point and access level. Best practices and key implementation considerations: for eg. Always customize the security settings in a model. Add a predictable prefix to the roles that you are developing to allow for simpler tracking etc. Follow best practices and key implementation considerations © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Security Upgrade Steps TechReady13 4/24/2017 Security Upgrade Steps AX 4,AX 2009 Source 1. Export Export legacy security settings from AX 4.0/2009 2. Match Match out-of-box privileges to legacy security settings Target AX 2012 Systems (Dev, Test, Prod) 3. Create Privileges For missing settings, create custom privileges Iterate How do you go about fine tuning the upgraded settings? - Iterative process Steps some of the ISV have take. 4. Review/Fine-Tune Review new security suggestions and fine-tune 5. Generate Custom Roles That map to legacy User Groups © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Match Process AX 4.0/2009 AX 2012 Advance Buyer (Role) CustTable TechReady13 4/24/2017 Match Process Advance Buyer (Role) AX 4.0/2009 AX 2012 Matches Privilege Advance Buyer (User Group) CustTable CustTable Exact CustTableView View View Contact Person Contact Person Similar ContactPersonMaintain Full Control Create Review match Asset Addition Asset Addition No Privilege AssetAdditionView Create new privilege View Emphasize that user group is being moved to “Custom Role” Suggest – “If you find direct mapping between user group and “out of box” role that’s even better. By this time you should have equivalent security settings compared to legacy systems. The goal - User has same access level compared to AX 2009 CCMActive Price Not Found No Entry Point NA View Create entry point and privilege, if needed Address Format Full Control Removed Entry Point Deprecated NA © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Security Upgrade Advisor Tool (Beta)

Demo 3 : Security Upgrade Service [Beta] Persona Pain Points and Challenges Features Covered Results and Benefits Isaac, Simon Difficult to upgrade to new role-based security framework Generate custom roles for each user group in legacy system Finds privileges for menu items to which user groups were granted permissions on the legacy system Follows best practices Quick and secure start on AX 2012 by leveraging existing Security Investments

Top Tips from the Session Do not upgrade with XPOs – Always use AOD/model files Back up often, both as model files and the database Complete the lowest-layer upgrade first before moving to the next highest layer For form, remove customizations and pull over element from baseline or reapply customizations Do not merge Upgrade in dependency order (Enum -> EDT -> Tables -> Code -> UI) Fix your schema first, then code, then UI Security upgrade comes after Code Upgrade

What we showed you today… How to plan for and execute a successful Code Upgrade Process and steps required for a upgrade Tools available to accelerate code upgrade

Related sessions BRK 220: Data Upgrade Tools for Developers and Administrators

Solution Architecture Visit our Focus Rooms Evaluation of Implementation Proposals by Dynamics AX R&D Solution Architecture & Industry Experts Gain further insights on Dynamics AX Industry Solution Offerings Resolution Guidance on Solution Roadblocks Networking Manufacturing Public Sector Services Industries Retail Solution Architecture Risso 6A/B Risso 6C Risso 7A Risso 7B Risso 8A