Dynamics Community Forum Thread Details

Good morning, afternoon, or evening depending on your location!

Below is an approach that many have found useful when dealing with this classic issue in free text invoice accounting distributions.

The Core Issue
When you generate accounting distributions programmatically (via X++), the system’s built‐in “Distribute Amount” form re-runs its logic when it loads. That means it re-imports or regenerates the default distributions based on header/line data—overwriting your custom entries. In effect, unless you “finalize” or flag your distributions as complete, the form thinks nothing has been done and thus rebuilds everything.

The Proper Approach
To have your custom accounting distributions persist, you’ll need to work WITH the distribution framework rather than bypassing it. Consider these guidelines:

Leverage Built-In Methods and Business Logic
Instead of manually inserting records, call the same X++ classes/methods that the “Distribute Amount” button uses.
- For example, methods in a class like DistributeAmounts (or similar, based on your release) help you compute and then finalize distributions.
- These methods often include logic that sets flags (or statuses) on the header or line records once distributions have been produced.
- By calling these methods (or following their pattern), you can allow your custom modifications to be integrated into the final distribution set.
Mark Your Distributions as Finalized
One common pattern is to update a status field on the free text invoice header (or on the distribution records) that signals distributions are “finalized” or “submitted.”
- For example, if your header or line has a field such as AccountingDistributionStatus, you must set it (for instance, to a value like Finalized) after you create your custom distributions.
- This finalization tells the system “don’t recalc my distributions” when the form loads.
Prevent Regeneration on Form Load
You might also consider overriding (or subscribing to) the event/method that fires during the “Distribute Amount” form’s init routine.
- Here, check if your distribution records already exist in a finalized state, and if so, bypass the regeneration logic.
- This might mean writing a small event handler in X++ that suppresses the automatic rebuild if your custom flag is detected.

A Pseudo-Code Example
Below is a simplified example to illustrate the pattern:
// Retrieve the free text invoice header and associated lines
FreeTextInvoiceHeader   invoiceHeader = ...;
FreeTextInvoiceLine     invoiceLine   = ...;
// Compute the default distributions using the supported method (adjust per your version)
AccountingDistribution[] distributions = DistributeAmounts::computeDistributions(invoiceHeader, invoiceLine);
// Loop through the distributions and apply custom modifications
for (int i = 0; i < distributions.length(); i++)
{
    // Example: update distribution percentage, main account, or financial dimensions
    distributions[i].MainAccount    = 'XXXXXX';
    distributions[i].DistributionPct = 50;
    // ... any other custom logic
}
// **Important:** Mark the invoice as having its distributions finalized to prevent re-generation
invoiceHeader.AccountingDistributionStatus = AccountingDistributionStatus::Finalized;
invoiceHeader.doUpdate();
// Optionally, call a method to "finalize" the distributions
// (this can also commit the custom distributions to the ledger interface)
DistributeAmounts::finalizeDistributions(invoiceHeader);
Note:
The actual class/method names and status field values may differ based on your D365FO version and configuration. Always refer to your version-specific documentation and test thoroughly in a non-production environment.
Summary

Use the supported X++ methods: Call the business logic that Powers the “Distribute Amount” form.
Finalize your distributions: Set a status (or a similar flag) so that the system won’t auto-regenerate them.
Control form behavior: If necessary, override the form’s event logic so it respects your custom distribution records.

By following these guidelines, your accounting distributions should persist as intended after you create them via X++.

Please note: I teamed up with CoPilot AI to research and craft the best response to your question!
Hope this helps some!