1. Implementing and Upgrading to AX7 Steve Mortland
September 15, 2016

2. Agenda Introduction Background of project Data Entities
Excel Data Connector & Excel Workbook Designer
Cross Company Data Sharing
Questions

3. AX 7 Project Client is a weight loss plan with 25 retail locations.
Combination of company owned and franchisee locations.
Owned by a large healthcare organization that currently runs Lawson for ERP.
Project includes Dynamics CRM, AX 7 Retail, AX 7 financials, procurement, and inventory management.
Utilizing Scribe for bi-directional integration between CRM and AX 7
Anticipated go-live is scheduled for December 1st.

4. What is a Data Entity?
Data entity provides conceptual abstraction and encapsulation (de- normalized view) of underlying table schemas to represent key data concepts and functionalities.
A data entity has the following capabilities:
It replaces diverging and fragmented concepts of AXD, Data Import/Export Framework (DIXF) entities, and aggregate queries with single concept.
It provides a single stack to capture business logic, and to enable scenarios such as import/export, integration, and programmability.
It becomes the primary mechanism for exporting and importing data packages for Application Lifecycle Management (ALM) and demo data scenarios.
It can be exposed as OData services, and then used in tabular-style synchronous integration scenarios and Microsoft Office integrations.

5. Entity Example
Current normalized model
Customer entity

6. Data entities demo

7. Excel Data Connector & Excel Workbook Designer
Excel data connector is a plug-in
Difference between Open in Excel vs Export to Excel
Excel Workbook Designer
Used to design an “editable” customer export workbook that contains an entity and a set of fields.
All key fields of the entity must be included to publish data edits.
Document templates
Used for adding Excel workbook to Open in Excel list

8. Excel data connector & workbook designer demo

9. Cross-Company Data Sharing
Cross-company data sharing lets you replicate (share) reference and group data among companies.
Examples of uses:
The same payment terms and payment day definitions are used across 15 legal entities.
The same terms of delivery are used across seven legal entities in three countries/regions.
Limitations:
It can’t be used to share transactional data between companies.
Only reference and group data can be shared.
It supports replication of fewer than one million total records per job. (This total is calculated as the number of shared records × the number of shared companies.)
Only one level of child relationships is exposed. To protect data consistency, replication doesn’t occur if another level is required.

10. Financial data sharing template
Bank parameters
Ledger journal names
Payment days
Payment schedules
Payment terms
Tax exempt codes

11. Supply chain data sharing template
Barcode parameters
Barcode setup
Buyer group
Charges group
Commission
Destination code
Non-conformance type
Order entry deadline group
Order origin code
Order pool
Production group
Production pool
Reason for delivery
Supplementary item group
Terms of delivery
Work time calendar

12. Cross-Company data sharing demo

13. Questions?

14. Stoneridge Software AX Blog https://stoneridgesoftware