A seller viewing a lead record tries to directly edit the Predictive Score field to reflect her own judgment. She's told the field cannot be typed into. Why is the predictive score field on a lead record not directly editable by sellers?
Select an answer to reveal the explanation.
Short Explanation
The score field isn't locked because of some permission the seller is missing, it's locked because it's a calculated output, not a data entry field. The model produces that number from what's actually in the record and how the lead has engaged, and letting people type over it would defeat the point, since the field would stop meaning what it's supposed to mean. There's no special elevated access an admin can grant to unlock it, no waiting period after a lead has been open a while that suddenly makes it editable, and no difference between using it on a laptop versus a phone, it behaves the same everywhere. If a seller has a strong hunch about a lead that the data doesn't yet support, the right outlet for that judgment is the separate manual rating field, which exists exactly for cases like this, rather than trying to override the calculated number itself.
Full Explanation
The correct answer is A. The predictive score on a lead record is generated by the scoring model from the lead's data and engagement history, and Dynamics 365 exposes that result as a read-only, system-calculated field precisely so it reflects what the model actually computed rather than a manually typed value that could drift from the underlying calculation. If a seller disagrees with the score, the correct path is to update the Rating field or record additional context, not to overwrite the number itself. Option B is incorrect because there is no workflow in which an administrator grants a temporary elevated role that unlocks direct editing of the score field; the field's read-only behavior is not a permissions setting that can be toggled per user. Option C is incorrect because no age-based rule exists that unlocks manual editing after a lead has been open for a set number of days; the field remains system-calculated regardless of how long the lead has been active. Option D is incorrect because the field's editability does not differ between the web client and the mobile app; it is calculated and read-only across the platform consistently. Sellers who want their own judgment reflected should use the separate manual Rating field instead.