The enhanced experience for adding Opportunity Products creates silent failures and ignores admin settings. Required fields can be left blank, and when saving is blocked, no error message appears—users have no guidance. The system confuses “OpportunityId” (schema name) with “opportunityid” (logical name), making it impossible to add the correct column to the view. Additionally, columns like “OpportunityProductName” appear even though they are not included in the view, breaking configuration consistency. This behavior risks data integrity. The system must enforce required fields, provide clear validation messages, respect view/form configurations, and harmonize naming. Enterprise users need predictable, validated, and configurable product add flows—this is essential for trust and usability.