NTO has implemented salesforce for its sales users. The opportunity management in salesforce is implemented as follows: 1.Sales users enter their opportunities in salesforce for forecasting and reporting purposes. 2.NTO has a product pricing system (PPS) that is used to update opportunity amount field on opportunities on a daily basis. 3.PPS is the trusted source within the NTO for opportunity amount. 4.NTO uses opportunity forecast for its sales planning and management. Sales users have noticed that their updates to the opportunity amount field are overwritten when PPS updates their opportunities. How should a data architect address this overriding issue?
A.
Create a custom field for opportunity amount that sales users update separating the fields that PPS updates.
B.
Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.
C.
Change opportunity amount field access to read only for sales users using field level security.
D.
Change PPS integration to update only opportunity amount fields when values is NULL.
B.
Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.
Explanation:
To maintain data integrity and clearly delineate responsibility, the best practice is to have separate fields for user-entered and externally integrated data. Creating a custom field specifically updated by the Product Pricing System (PPS) prevents overwriting users’ manual entries and confusion regarding data ownership. Changing field access to read-only (Option C) restricts users unnecessarily. Option D (updating only when null) limits PPS’s effectiveness, failing if manual data already exists. A dedicated custom field clearly communicates the source, improves data quality, maintains user transparency, and aligns best with Salesforce data integration practices.