RFID with Microsoft Dynamics: Connect Reads to Warehouse Transactions
Working record | Updated October 3, 2026
Guide: https://yenra.com/rfid-microsoft/

Purpose: Map reader middleware to a documented Dynamics integration route and test transaction results, retries and reconciliation.

Instructions
1. Save a separate copy for each site, job or configuration. Use test aliases where records concern people or payments.
2. Fill each field with a result and its evidence reference. Mark unknown items UNRESOLVED; do not infer a pass.
3. Record the configuration, document revision and date behind each result. Keep credentials and sensitive records in approved systems rather than this worksheet.
4. Assign unresolved items an owner and next action. Sign off only within the scope actually verified.
5. Recheck affected fields after the configuration, supplier or requirements change.

Evaluation name: 
Date and reviewer: 
Scope and intended decision: 

1. Dynamics product/version and warehouse mode: 
   Evidence/reference and result: 

2. Business operation and required starting state: 
   Evidence/reference and result: 

3. Chosen interface and current documentation: 
   Evidence/reference and result: 

4. Reader/middleware versions: 
   Evidence/reference and result: 

5. Identity, unit and location mapping: 
   Evidence/reference and result: 

6. Event reference and message reference: 
   Evidence/reference and result: 

7. Supported status/replay behavior: 
   Evidence/reference and result: 

8. Expected versus actual application result: 
   Evidence/reference and result: 

9. Unknown identity/unit mismatch/rejection tests: 
   Evidence/reference and result: 

10. Interrupted-response and repeat-submission results: 
   Evidence/reference and result: 

11. Monitoring, cleanup and reconciliation owners: 
   Evidence/reference and result: 

12. Production acceptance decision: 
   Evidence/reference and result: 

Illustrative example from the guide (fictional, not a test result)
Invented recovery scenario Middleware accepts one movement of handling unit DEMO-P17 and submits request DEMO-MOVE-041. The application processes it, but the response is lost. The integration marks the outcome uncertain and checks the supported processing record. Once it confirms the original result, it records that result against DEMO-MOVE-041. It does not invent a new movement reference merely because the response was interrupted.

Decision: ACCEPT / REVISE / HOLD
Decision scope and rationale: 
Unresolved item / owner / next action / due date: 
Approved by and date: 
Change that requires review: 

Primary references (verify applicable revision and scope)
https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/mhax
https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/wms-only-mode-exchange-data