Skip to content

[master] [All-e]Fixed asset report 5607 and 4413 showing different results with Declining Balance#8324

Merged
djukicmilica merged 10 commits into
microsoft:mainfrom
neeleshsinghal:bugs/Bug-636727-Fixed-asset-report-5607-and-4413-showing-different-results
Jun 2, 2026
Merged

[master] [All-e]Fixed asset report 5607 and 4413 showing different results with Declining Balance#8324
djukicmilica merged 10 commits into
microsoft:mainfrom
neeleshsinghal:bugs/Bug-636727-Fixed-asset-report-5607-and-4413-showing-different-results

Conversation

@neeleshsinghal
Copy link
Copy Markdown
Contributor

@neeleshsinghal neeleshsinghal commented May 27, 2026

Workitem :

Bug 636727: [master] [All-e]Fixed asset report 5607 and 4413 showing different results with Declining Balance

Fixes AB#636727

Issue: Report 4413 (Fixed Asset Projected Value Excel) calculates incorrect depreciation amounts for Declining Balance assets when projections cross a fiscal year boundary, producing different results than the legacy Report 5607.

Cause: In InsertProjectedEntries, EntryAmounts[3] (depreciation in fiscal year) was reset to 0 before accumulating the current period's depreciation, causing the last fiscal period's depreciation to spill into the new fiscal year and shifting the effective book value base back one month.

Solution: Moved AccumulateProjectionEntryAmounts before the fiscal year boundary reset (EntryAmounts[3] := 0) so the outgoing fiscal year's final depreciation is fully accumulated before the counter resets, matching the order used in Report 5607.

@github-actions github-actions Bot added AL: Apps (W1) Add-on apps for W1 From Fork Pull request is coming from a fork Linked Issue is linked to a Azure Boards work item labels May 27, 2026
@github-actions github-actions Bot added this to the Version 29.0 milestone May 27, 2026
@JesperSchulz JesperSchulz added the Finance GitHub request for Finance area label May 27, 2026
@neeleshsinghal neeleshsinghal marked this pull request as ready for review May 28, 2026 12:05
@neeleshsinghal neeleshsinghal requested a review from a team as a code owner May 28, 2026 12:05
Comment thread src/Apps/W1/ExcelReports/Test/src/FixedAssetExcelReports.Codeunit.al Outdated
djukicmilica
djukicmilica previously approved these changes May 28, 2026
Copy link
Copy Markdown
Contributor

@AleksanderGladkov AleksanderGladkov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@neeleshsinghal please also add description to the PR

Comment thread src/Apps/W1/ExcelReports/Test/src/FixedAssetExcelReports.Codeunit.al Outdated
Comment thread src/Apps/W1/ExcelReports/Test/src/FixedAssetExcelReports.Codeunit.al Outdated
Comment thread src/Apps/W1/ExcelReports/Test/src/FixedAssetExcelReports.Codeunit.al Outdated
Comment thread src/Apps/W1/ExcelReports/Test/src/FixedAssetExcelReports.Codeunit.al Outdated
Comment thread src/Apps/W1/ExcelReports/Test/src/FixedAssetExcelReports.Codeunit.al Outdated
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.


🔄 How to trigger a new status check:

  1. 📤 Push a new commit to the PR branch, or
  2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.

@djukicmilica djukicmilica merged commit 72790a2 into microsoft:main Jun 2, 2026
89 of 91 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AL: Apps (W1) Add-on apps for W1 Finance GitHub request for Finance area From Fork Pull request is coming from a fork Linked Issue is linked to a Azure Boards work item

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants