D365 portfolio projects you can explain in an interview

What a useful portfolio contains

Give the reader a problem, your scope, the work, the tests, and the result. State whether the example is built, partly built, or a design exercise.

Use invented data. Get permission before sharing employer work, customer names, screenshots, code, or records. Removing a name may not remove confidential detail.

The assignments below are illustrative exercises. They are not real customer case studies or proof of production readiness.

Functional consulting: purchase approval

Design a process for a fictional company that needs approval for larger purchases. Define users, approval rules, and an exception for an absent approver.

Produce a process map, requirements, configuration notes, and test cases. If you have suitable product access, build the agreed scope and record the results.

Explain who decides the approval limits and how the process owner would accept the change.

Business Central development: a small extension

Choose a simple validation or information field for a fictional business. Use a supported AL extension approach in an approved environment.

Include the requirement, code, permissions, tests, and deployment notes. Explain how you would check behaviour after a product update.

If you lack environment access, provide the design and test plan. Do not describe untested code as a working extension.

Dataverse development: service request validation

Build a small service request example with invented records. Define one rule that must hold when a record is saved.

Test valid input, missing data, and a user with limited permissions. Explain where the rule runs and how an error reaches the user.

Include solution packaging and a short support note. Keep the scope narrow enough to explain each decision.

Integration: order transfer

Design a connection from a mock order system to a mock receiver. Define the message fields and the owner of each record.

Test a repeated request, a timeout, and an invalid order. Record how the process detects and recovers from each failure.

Show a support log and reconciliation check. A working transfer needs evidence that records arrived correctly and only as intended.

Data migration: customer records

Create a small fictional file with duplicate, incomplete, and invalid records. Write the mapping and clean-up rules before processing it.

Produce accepted and rejected records, a reconciliation summary, and a rehearsal plan. Explain who would approve uncertain matches in a real project.

Show the original data alongside the final result so a reviewer can trace the changes.

Present the work

Keep the main explanation to one page and link supporting files. Include the date, tools, access limits, and one improvement you would make next.

In an interview, explain a decision and a failed test. These show how you think and use evidence.

Practice task