Share
ReportWe are currently implementing D365 F&O for XXX Company, this company requiring high-precision decimal handling for unit pricing and quantities.
We have identified a technical challenge regarding decimal precision that requires your technical expertise.
**Current Situation:**
- Database schema supports number(32,6) for QtyUnit and UnitPrice fields
- Standard EDT (Extended Data Type) in SaaS limits precision to 2 decimal places
- User input of 4 decimal places (e.g., 1.2345) is being rounded to 2 decimals before database storage
- EDT customization is not available in D365 F&O SaaS environment
**Problem Statement:**
We need to preserve 4 decimal places for accurate pricing and quantity management, but the current form controls and EDTs enforce rounding to 2 decimal places during the input-to-storage workflow.
**Proposed Solution:**
We are evaluating a two-part approach:
1. **Form Control Enhancement via X++ Event Handlers**
- Intercept user input at the Modified event level
- Bypass standard EDT rounding and store values directly with 4 decimal precision
- Maintain database compatibility with number(32,6) schema
2. **Extended Table Fields**
- Add new precision-enhanced fields: QtyUnitPrecise, UnitPricePrecise
- Reserve standard fields for backward compatibility with existing integrations
- Enable audit trail and traceability
**Key Questions:**
1. Is X++ event handler customization fully supported in D365 F&O SaaS for form controls?
2. Are there any known limitations or best practices for bypassing EDT precision constraints?
3. Can table extensions with new fields be deployed in a production SaaS environment?
4. What are the recommended approaches for maintaining data integrity during OData/EDI synchronization with non-standard precision fields?
Categories:
I have the same question (0)
All responses (
Answers (
4
