Contents

Lab 1: Configure Electronic Reporting.............................................................................1

Lab 2: Export ER Configuration as XML..........................................................................2
Lab 3: Verify and Test the Electronic Reporting Format...................................................4
Lab 4: Creating and Designing an Electronic Reporting (ER) Format for Sales Orders...5
Lab 5: Defining ER Model Mappings and Selecting Data Sources................................10
Lab 6: Designing a Domain-Specific ER Data Model for Payments...............................15
Lab 7: Identify and Fix Data Mapping Issues.................................................................21

Message to Students: Handling Issues During Labs

As you progress through the labs, you may encounter challenges or unexpected issues
due to the evolving nature of Dynamics 365. It is important to understand that software
platforms like Dynamics 365 undergo frequent updates, which can result in changes to
the user interface or available features. This may occasionally cause discrepancies
between the instructions provided and what you experience during the labs.
If you face any difficulties or inconsistencies:
1. Stay Calm:
It’s natural to encounter hiccups, especially in fast-evolving technologies. Take a
moment to review the steps carefully and troubleshoot the issue.
2. Document the Issue:
Instead of feeling frustrated, take note of the specific problem you're facing. Write
down the step where you encountered the issue and what you see on your
screen.
3. Inform the Instructor:
Bring the issue to my attention. I am here to assist and provide guidance. I will
also ensure that any necessary updates to the labs are made for the benefit of
future students.
4. Keep an Open Mind:
Working through these kinds of challenges is part of the learning process, and
they help build problem-solving skills that will be invaluable in your career.
By approaching the labs with patience and attention to detail, you will maximize your
learning experience. I am here to support you at every step. Let’s work together to make
the most of this journey.

Lab 1: Configure Electronic Reporting

Objective:
In this lab, you will set up the basic functionality for Electronic Reporting (ER) and
create a new configuration provider that will be used in subsequent labs.
Why This Matters:
Before you can use ER to generate reports or export/import configurations, you must
configure the system and create a provider. The provider helps manage where the ER
data comes from and how it is used in the system.
Instructions:
1. Open the Electronic Reporting Workspace:
o Navigate to Dynamics 365 Finance and Operations.
o Go to the Electronic Reporting workspace under Organization
administration.
2. Set Up Electronic Reporting Parameters:
o In the App links section, select Electronic reporting parameters.
o On the General tab, turn on Enable design mode. This allows you to use
the ER design tools.
o On the Attachments tab, define the types of documents used for storage,
such as:
 Office documents as templates for reports.
 File storage for report outputs.
 Storage for configuration output baselines and handling files.
o Question: Why do we need to enable design mode before proceeding?
3. Create a New Configuration Provider:
 o Go to Related links > Configuration providers.
o Select New.
o In the Name field, type Litware, Inc..
o In the Internet address field, type https://www.litware.com.
o Select Save.
4. Activate the Provider:
o Select the provider Litware, Inc..
o Click Set active to activate the provider.
o Question: What happens if we don’t activate the provider?
 Hint: Think about what happens when a provider is inactive.

Follow-up Task:
 Repeat this process to create and activate another configuration provider for a
different organization, such as Contoso Ltd. (https://www.contoso.com).

Lab 2: Export ER Configuration as XML

Objective:
You will learn how to export an Electronic Reporting (ER) configuration as an XML file,
which can be used for backups or importing into other environments.
Why This Matters:
Exporting configurations allows you to reuse them in different environments or share
them with other users. This is especially useful for compliance, reporting consistency,
and system migrations.
Instructions:
1. Navigate to the Electronic Reporting Workspace:
 o Open Dynamics 365 Finance and Operations.
o Go to the Electronic Reporting workspace.
o Select Configurations, then go to Reporting Configurations.
2. Search for the Configuration:
o In the left pane, use the search bar to find Invoice model.
o Under Invoice model, locate Free text invoice (Excel).
3. Select the Configuration:
o Click on the configuration you want to export, such as Free text invoice
(Excel).
4. Export the Configuration:
o In the Versions tab on the right, find and click the Exchange button.
o From the dropdown, select Export as XML file.
5. Download the XML File:
o The configuration will be downloaded as an XML file to your local
computer.
6. Important:
o Make sure the configuration is in Completed or Shared status before
exporting.
o Question: Why do we need the configuration to be in Completed or
Shared status before exporting?
Follow-up Task:
 Export another configuration (e.g., for GST Returns) and ensure it’s saved as
XML. Once done, compare the two XML files and note the differences in their
structure.

Lab 3: Verify and Test the Electronic Reporting Format

Objective:
As the Finance Manager for USMF, you will set up and test the Electronic Reporting
format for vendor payments, ensuring the format matches local requirements.
Why This Matters:
Accurate payment formats are critical for compliance with local regulations and for
ensuring that electronic payments are processed correctly by financial institutions.
Instructions:
1. Set Up File Format:
o In company USMF, go to Accounts payable > Payment setup >
Methods of payment.
o Place your cursor on Electronic in the left navigation bar.
o Select the File formats FastTab.
o Ensure that the Export format is set to NACHA (US).
o Save and close the page.
o Question: Why is it important to choose the correct export format for
electronic payments?
2. Test the Payment Format:
o Go to Accounts payable > Payments > Vendor payment journal.
o Select New.
o In the Name field, select VendPay.
o Save the journal and then select Lines.
o Enter the following data:
 Company: DEMF
 Account: DE-01001
 Description: Payment
 Debit: 175
o On the Payment tab, set Method of payment to Electronic.
o Save the changes.
3. Generate Payments:
 o Click Generate payments.
o Ensure Method of payment is set to Electronic and Bank account is
USMF OPER.
o Select NACHA (US) as the export format and click OK.
4. View the Generated File:
o After the file is created, note the File name and select Open file to view it
in Notepad.
Follow-up Task:
 Repeat the test using a different payment method (e.g., SEPA (EU)). Analyze
the differences in the generated file and explain why these differences exist.

Lab 4: Creating and Designing an Electronic Reporting

(ER) Format for Sales Orders

Objective:
In this lab, you will create a new data model for Sales Orders, add necessary fields
(nodes), design a format for how this data will be presented in an Excel report, map the
fields, and generate the report to see the final output.

Scenario:
You are a business analyst tasked with creating a custom report for Sales Orders in
Dynamics 365. The report should include information like Customer Name, Order
Amount, Order Date, and Sales Order Number. You will build the report using
Electronic Reporting (ER) by first defining a data model, creating a format, and finally
generating an Excel file for review.

Part 1: Creating the Data Model

Step 1: Navigate to the Electronic Reporting Workspace
 1. Open Dynamics 365 Finance and Operations.
2. Go to Organization administration > Workspaces > Electronic reporting.
3. In the Configurations section, click Create configuration.
Step 2: Create a New Data Model
1. Select Root as the type of configuration.
2. In the Name field, enter Sales Orders Data Model.
3. Add a Description, like Data model for exporting sales order details.
4. Choose your Configuration provider (e.g., Harjit).
5. Click Create configuration.

Part 2: Adding Nodes (Fields) to the Data Model

Step 3: Open the Data Model Designer
1. Click on the Sales Orders Data Model configuration that you just created.
2. Click Designer to open the Data Model Designer.
Step 4: Add Root Node
1. Click New and select Add root.
2. In the Name field, type Sales Orders.
3. Click Save to create the root node.
4. This root node will serve as the main container for all the fields (nodes) related to
sales orders.
Step 5: Add Fields (Nodes) to the Model
1. Under the Sales Orders root node, click New > Add to create fields:
o Field 1:
 Name: Customer Name.
 Type: String.
 This will hold the customer’s name in the report.
o Field 2:
 Name: Order Amount.
 Type: Decimal.
  This field will store the total amount of the sales order.
o Field 3:
 Name: Order Date.
 Type: Date.
 This field will store the date of the sales order.
o Field 4:
 Name: Sales Order Number.
 Type: String.
 This will store the unique sales order number.
2. After adding each field, click Save to update the model.

Part 3: Creating the Format Based on the Data Model

Step 6: Create a New Format
1. Go back to the Electronic Reporting workspace.
2. Click Create configuration again, but this time select Format based on data
model.
3. Choose the Sales Orders Data Model that you created in Part 1.
4. In the Name field, type Sales Orders Excel Format.
5. Add a Description, such as Format for exporting sales order details to Excel.
6. Click Create configuration.

Part 4: Designing the Format

Step 7: Open the Format Designer
1. Click on Sales Orders Excel Format to open it.
2. Click Designer to start designing the format.
Step 8: Add a Root Element
1. Click Add root and name it SalesOrderReport.
2. This root element will be the structure that holds all the data fields you defined
earlier in the data model.
Step 9: Add Elements to the Format
1. Under the SalesOrderReport element, click New and add elements to represent
the fields you want to include in the report:
o Element 1:
 Name: Customer Name.
 Type: Text.
 Binding: Map this element to the Customer Name node from your
data model.
o Element 2:
 Name: Order Amount.
 Type: Decimal.
 Binding: Map this element to the Order Amount node from your
data model.
o Element 3:
 Name: Order Date.
 Type: Date.
 Binding: Map this element to the Order Date node from your data
model.
o Element 4:
 Name: Sales Order Number.
 Type: Text.
 Binding: Map this element to the Sales Order Number node from
your data model.
Step 10: Set Properties for Each Element
1. For each field, you can set properties:
o Mandatory: Set to Yes for critical fields.
o Alignment: Choose Left or Right alignment for text or numbers.
o Formatting: Set specific date or number formats, such as MM/DD/YYYY
for dates or #,###.00 for numbers.
Step 11: Save the Format
 1. Once all elements are added and mapped to your data model, click Save.

Part 5: Mapping and Validations

Step 12: Map to Data Source
1. Go to the Mapping tab in the designer.
2. Make sure each format element (e.g., Customer Name, Order Amount) is
correctly mapped to the corresponding data model fields.
Step 13: Add Validations (Optional)
1. You can add validations to ensure the data follows certain rules. For example,
you can ensure that Order Amount is never zero by setting validation rules
under the Validations tab.

Step 14: Complete the Version

1. Go to the Versions tab of your Sales Orders Excel Format.
2. Change the status from Draft to Completed by clicking Change status >
Completed.

Follow-up Tasks:
1. Customize the Format: Add an Excel template for more control over the layout
of the report, such as custom headers, fonts, or borders.
2. Add New Fields: Extend the data model to include additional fields like Payment
Terms, Shipping Address, or Discounts, and update the format accordingly.

Expected Outcome:
By the end of this lab, you will have successfully created a data model, designed a
report format, and generated an Excel report with Sales Order details. This report will be
ready for use by other departments for reviewing and analyzing sales orders.
Lab 5: Defining ER Model Mappings and Selecting Data
Sources

Objective:
In this lab, you will learn how to define model mappings for an Electronic Reporting (ER)
configuration and select appropriate data sources. The example scenario involves
mapping a payment data model for credit transfers.

Part 1: Open the ER Configurations Tree

Step 1: Navigate to the Electronic Reporting Workspace
1. Go to Organization administration > Workspaces > Electronic reporting.
o This is where you manage all electronic reporting configurations.
2. Click on Reporting configurations.
o This takes you to the list of available configurations.

Part 2: Insert a New Model Mapping

Step 2: Select the Payment Model
1. In the tree, select Payments (simplified model).
o You are selecting the configuration related to payment models.
2. Click Designer.
o This opens the designer where you’ll define mappings.
3. Click Map model to datasource.
o This is where you start creating mappings to bind your data model to data
sources.
Step 3: Create a New Mapping
1. Click New to create a new model-to-datasource mapping.
o This allows you to create a fresh mapping configuration.
 2. In the Name field, type CT mapping.
o This gives your mapping a clear name that reflects its purpose (Credit
Transfer).
3. In the Description field, type Payment model mapping CT.
o A description is useful for future reference.
4. In the Definition field, type CustomerCreditTransferInitiation.
o This field specifies the key process related to the mapping.
5. Click Save.
o Save the mapping configuration before adding data sources.

Part 3: Define Required Data Sources

Step 4: Open the Mapping Designer
1. Click Designer.
o This opens the designer to start selecting data sources for your mapping.
Step 5: Add Payment Transactions Data Source
1. In the tree, select Dynamics 365 for Operations\Table records.
o You will now access the data from specific tables in D365.
2. Click Add root to create a root data source.
o Root defines the main data source for the mapping.
3. In the Name field, type Transactions.
o Name your data source for clarity.
4. In the Label field, enter Transactions.
o This label will be shown in the reports.
5. In the Help field, enter Ledger journal lines.
o This description will help future users understand what the data source is
for.
6. In the Ask for query field, select Yes.
o This will allow the user to query specific data from the table.
7. In the Table field, type LedgerJournalTrans.
 o Select the table from which you want to pull the payment transactions.
8. Click OK to add the table as a data source.
Step 6: Create a Calculated Field for Payment ID
1. In the tree, select Functions\Calculated field.
o Calculated fields allow you to create new data points based on existing
data.
2. Click Add to create a new calculated field.
3. In the Name field, type $EndToEndID.
o This will store a unique ID for the payment.
4. Click Edit formula.
o This opens the formula editor for the calculated field.
5. In the tree, select String\CONCATENATE.
o Concatenation joins multiple strings into one.
6. Click Add function.
7. In the tree, expand Transactions and select Transactions\Voucher.
o You will concatenate the Voucher field with other data.
8. Click Add data source.
9. In the Formula field, enter CONCATENATE(Transactions.Voucher, "-",.
o This formula joins the voucher with a dash.
10. Type "-", at the end of the formula to continue the concatenation.
11. In the tree, select String\TEXT and click Add function.
12. Select Transactions\Record-ID(RecId) and click Add data source.
13. Complete the formula as CONCATENATE(Transactions.Voucher, "-",
TEXT(Transactions.RecId)).
 This formula will create a unique identifier by combining the voucher and record
ID.
14. Click Save to save the formula.
15. Verify that no errors appear in the Errors tab.
 Ensure there are no mistakes in the formula.
 16. Close the formula editor.

Step 7: Add the Calculated Field for Payment Amount

1. Click Add to create another calculated field.
2. In the Name field, type $Amount.
o This will hold the calculated payment amount.
3. Click Edit formula to create the formula.
4. Expand Transactions in the tree, and select Transactions\
Debit(AmountCurDebit).
o This formula will subtract credit from debit to get the amount.
5. Click Add data source.
6. In the Formula field, enter Transactions.AmountCurDebit -.
7. Select Transactions\Credit(AmountCurCredit) and click Add data source.
8. Click Save to finalize the calculated field.
9. Close the formula editor.

Part 4: Add Additional Data Sources

Step 8: Add Bank Account Data Source
1. In the tree, select Dynamics 365 for Operations\Table records.
2. Click Add root to create a new root data source.
3. In the Name field, type BankAccount.
o This will store details of the bank account.
4. In the Label field, enter Bank Account.
5. In the Help field, enter Bank Account.
6. In the Ask for query field, select Yes.
7. In the Table field, type BankAccountTable.
8. Click OK to add the data source.
Step 9: Add Company Information Data Source
 1. Click Add root to add another root data source.
2. In the Name field, type Company.
o This will store the company’s information.
3. In the Label field, type Company.
4. In the Help field, enter Company information.
5. In the Ask for query field, select Yes.
6. In the Table field, type CompanyInfo.
7. Click OK to add the data source.
Step 10: Add a Calculated Field for Processing Date
1. In the tree, select Functions\Calculated field and click Add root.
2. In the Name field, type ProcessingDateTime.
o This field will store the current date and time of processing.
3. In the Label field, enter Processing date & time.
4. Click Edit formula.
5. In the tree, select Date/time\SESSIONNOW and click Add function.
o This will return the current session date and time.
6. Click Save to finalize the formula.
7. Close the formula editor.

Part 5: Finalize and Save the Mapping

Step 11: Save the Mapping
1. Click Save to ensure that your mappings and data sources are saved.
2. Close the page when you have verified that all mappings are correct.

Expected Outcome:
You have now successfully created model mappings, defined data sources, and created
calculated fields for the ER configuration. You should be able to use this mapping to
generate reports with credit transfer payment data.
Lab 6: Designing a Domain-Specific ER Data Model for
Payments

Objective:
In this lab, you will design a domain-specific Electronic Reporting (ER) data model for
processing payment documents. You will define structures for parties, banks, and
payment transactions, creating a data model to support credit transfer payments. This
data model will later be used as a data source when formatting payment documents.

Part 1: Create a New Data Model Configuration

Step 1: Open Electronic Reporting Workspace
1. Go to Organization administration > Workspaces > Electronic reporting.
o This is where you manage configurations for electronic reporting.
Step 2: Select or Create a Configuration Provider
1. Select the configuration provider for Litware, Inc..
o If this provider does not exist, create one by completing the steps in the
"Create a configuration provider and mark it as active" procedure.
Step 3: Create a New Data Model Configuration
1. Click Reporting configurations.
o This shows the existing configurations, where you'll create a new one.
2. Click Create configuration.
o This opens a dialog to create a new configuration.
3. In the Name field, type Payments (simplified model).
o This name describes the payment data model.
4. In the Description field, type Payment model configuration.
 o This description helps identify the configuration.
5. Click Create configuration to finalize the configuration creation.

Part 2: Create a Data Model

Step 4: Open the Data Model Designer
1. Click Designer.
o You’ll use this tool to build the data model.

Part 3: Define the Structure of a Party in the Payment Process

Step 5: Add Party Details
1. Click New to open the drop dialog.
2. In the Name field, type Party.
o This node will store the details of a party involved in the payment (creditor
or debtor).
3. Click Add to save the node.
4. Click New to define a sub-node.
5. In the Name field, type Name.
6. In the Item type field, select String.
o This indicates that the party's name is a string.
7. Click Add to save the node.
Step 6: Search for Party Node
1. In the Find field, type Party.
2. Click Find previous to locate the Party node you just created.
o You can now add more details to this structure.

Part 4: Define the Bank Structure

Step 7: Add Bank (Agent) Details
1. Click New to create a new node.
 2. In the Name field, type Agent.
o This represents the financial institution handling the account.
3. In the Item type field, select Record.
4. Click Add.
5. In the Description field, enter Financial institution servicing an account for
the party.
o This provides clarity on the purpose of the node.
Step 8: Add Bank Fields
1. Click New to add a new field to the Agent.
2. In the Name field, type Name.
3. In the Item type field, select String.
o The name of the financial institution is a string.
4. Click Add.
5. Click New to add another field.
6. In the Name field, type SWIFT.
o This represents the bank’s identification code.
7. Click Add.
8. In the Description field, enter Bank identification code.
9. Click New to add a final field.
10. In the Name field, type RoutingNumber.
o This stores the bank’s routing number.
11. Click Add.
12. In the Description field, enter Routing number.

Part 5: Define the Bank Account Structure

Step 9: Add Account Information
1. Click New to create a new node.
2. In the Name field, type Account.
 o This node represents the bank account.
3. In the Item type field, select Record.
4. Click Add.
5. In the Description field, enter Identification of a party’s account in a financial
institution.
Step 10: Add Account Fields
1. Click New to create a field for currency.
2. In the Name field, type Currency.
3. In the Item type field, select String.
o This represents the currency code.
4. Click Add.
5. In the Description field, enter Currency code.
6. Click New to add a field for the account number.
7. In the Name field, type Number.
8. Click Add.
9. Click New to add a field for IBAN.
10. In the Name field, type IBAN.
11. Click Add.
12. In the Description field, enter International bank account number.

Part 6: Define Payment Message Structure for Credit Transfers

Step 11: Add Root for Payment Message
1. Click New to create a new root node.
2. In the New node as a field, select Model root.
3. In the Name field, type CustomerCreditTransferInitiation.
o This node represents the main message for credit transfer payments.
4. Click Add.
Step 12: Add Message Details
 1. Click New to add a field for message identification.
2. In the Name field, type MessageIdentification.
3. Click Add.
4. In the Description field, enter Point-to-point reference identifying the
message.
5. Click New to add a processing date field.
6. In the Name field, type ProcessingDateTime.
7. In the Item type field, select DateTime.
8. Click Add.
9. In the Description field, enter Date and time when the payment message was
created.

Part 7: Define Payment Transaction Structure

Step 13: Add Payment Transaction Structure
1. Click New to add a payment record list.
2. In the Name field, type Payments.
3. In the Item type field, select Record list.
o This will store a list of individual payment transactions.
4. Click Add.
5. In the Description field, enter Payment lines of the current message.
Step 14: Add Payment Fields
1. Click New to add a creditor field.
2. In the Name field, type Creditor.
3. In the Item type field, select Record.
4. Click Add.
5. In the Description field, enter Party to whom an amount of money is due.
6. Click Switch item reference, then Find Party and select it.
Step 15: Add Debtor Field
1. Click New to add a debtor field.
 2. In the Name field, type Debtor.
3. Click Add.
4. In the Description field, enter Party owing money to the creditor.
5. Click Switch item reference, then Find Party and select it.

Part 8: Add Additional Payment Details

Step 16: Add Payment Information
1. Click New to add a description field.
2. In the Name field, type Description.
3. In the Item type field, select String.
4. Click Add.
5. Click New to add a currency field.
6. In the Name field, type Currency.
7. Click Add.
8. In the Description field, enter Currency code.
Step 17: Add Transaction Date and Amount
1. Click New to add a transaction date field.
2. In the Name field, type TransactionDate.
3. In the Item type field, select Date.
4. Click Add.
5. In the Description field, enter Transaction date.
6. Click New to add an instructed amount field.
7. In the Name field, type InstructedAmount.
8. In the Item type field, select Real.
9. Click Add.
10. In the Description field, enter Amount of money to be transferred between
the debtor and creditor.

Part 9: Finalize the Data Model

Step 18: Add End-to-End ID
1. Click New to add an End2EndID field.
2. In the Name field, type End2EndID.
3. In the Item type field, select String.
4. Click Add.
5. In the Description field, enter Unique identification passed unchanged
throughout the payment chain.
Step 19: Save the Model
1. Click Save to finalize your data model.
2. Close the page.

Expected Outcome:
You have successfully created a domain-specific data model for handling payment
information, including parties, bank details, and payment transactions. This data model
can now be used to define formats for generating payment documents.

Lab 7: Identify and Fix Data Mapping Issues

Objective:
Learn how to troubleshoot data mapping issues in an existing ER setup and fix incorrect
or missing mappings between data sources and model components.
Instructions:
1. Access Existing Configuration:
o Go to Organization administration > Workspaces > Electronic
reporting.
o Open an existing configuration, preferably related to sales or payments.
2. Review Data Model Mapping:
o Open the Designer for the selected configuration.
 o Navigate to Map model to datasource.
o Inspect the existing mappings and identify where data is missing or
incorrectly mapped.
o Question: What is the difference between ‘map format to model’ and
‘Model to Datasource Mapping’?
o Question: What is the difference between mapping in the Designer and
the model mapping options in the list view?

3. Troubleshoot Mappings:
o Check if there are any red error indicators next to model components.
o Click on each mapping and verify that the correct data source is selected.
4. Fix Mapping Issues:
o For components with incorrect mappings, remap them to the correct data
sources by selecting the appropriate table or field.
o Save the configuration after making the changes.
Expected Outcome:
You will have identified and resolved incorrect or missing data mappings, ensuring that
all required fields are properly linked to their data sources.