Remove consumed credits from Payables Agent setup - #10238
Conversation
4cb4ae6 to
7816510
Compare
Agentic PR Review - Round 1Recommendation: Request ChangesWhat this PR doesThis PR removes the Cost section from the Payables Agent Setup page and deletes the internal codeunit that calculated consumed Copilot credits. The change matches the Slice goal to stop showing consumed-credit totals while leaving the trial and general billing text in place. The functional scope is narrow, but the page controls are removed outright instead of going through the obsolete path. SuggestionsS1 - Obsolete shipped setup controls before removal Risk assessment and necessityRisk: The business logic risk is low because the removed code only reads consumption data for display. The compatibility risk is higher because named controls on Payables Agent Setup disappear without an obsolete period. The deleted codeunit is internal, and no BaseApp event dependency was involved. Necessity: The change is needed for the new monetization model, and the ADO Slice discussion supports removing only the consumed-credit total and Cost section. The scope is right once the shipped UI controls follow the normal obsolete and clean-tag path.
|
|
The entire Suggested fix (apply manually — could not be anchored as a one-click suggestion): codeunit 3319 "PA Cost Estimate"
{
Access = Internal;
InherentEntitlements = X;
InherentPermissions = X;
Permissions = tabledata "Agent Task Consumption" = r;
ObsoleteState = Pending;
ObsoleteReason = 'The consumed credits information is no longer available.';
ObsoleteTag = '29.0';Knowledge:
Line mapping was unavailable, so this was posted as an issue comment. 👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.32.4 |
7816510 to
74c4df3
Compare
74c4df3 to
a103728
Compare
What & why
Removed the consumed Copilot credits section from the Payables Agent setup page. This information will no longer be available as part of the upcoming monetization changes, so the related UI and unused calculation code have been removed.
Fixes AB#646660
How I validated this
What I tested and the outcome
Risk & compatibility
Low risk. The deleted codeunit was internal and used only by the removed setup-page controls.