Share
Report
58Hello,
As part of a NAV to Business Central data migration using RapidStart configuration packages, I'm preparing a client training session and would like to nail down/formalize the following points:
1. Sales prices (T7002) and purchase prices (T7012)
- What is the recommended import order between items, customers, UoM, and prices to avoid reference errors?
- Which fields cause blocking import errors vs. silent ones (import succeeds but the price isn't applied on the order)? E.g., missing/incorrect UoM code, missing price group/customer price group code.
- What are the exact rules of the best-price selection engine (sales type/code, item, UoM, date range, minimum quantity)? Is there official documentation detailing the priority order?
- Empty date fields: is it confirmed they're treated as "always valid" (no blocking)?
2. General RapidStart best practices for a reliable migration
- Recommended table dependency order (e.g., contacts before customers, financial ratings before customers) to avoid duplicates automatically created by BC.
- Real-world use cases for the "Delete existing records before import" option: precautions in a production environment (risk of irreversible data loss).
- Lessons learned on the most common errors during bulk imports (dates stored as text, field length violations, special characters, duplicate key errors).
3. Post-import validation
- Is there a standard Microsoft tool or method to validate data integrity after import (aside from building custom scripts)?
Thanks in advance for your field experience, especially on pricing, which seems to be a sensitive point (import succeeds without error but the price doesn't display on the order).
Categories:
I have the same question (0)
All responses (
Answers (
