Accounting Source Explorer - AccountingSourceExplorerTmp error

(1) Share

Report

Posted on by Community Member

We have been testing D365 PU21 and PU23, and have been very impressed with the Accounting Source Explorer. However, on our cloud Production instance of D365FO EE 8.1 PU23, if anyone goes General Ledger > Accounting Source Explorer, then picks any of the "Financial Dimension Set" picklist (such as Main-Project or "All"), we all get is:

"Cannot edit a record in Accounting source explorer (AccountingSourceExplorerTmp). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record."

No dimensions are shown, and then we're in Hotel California trying to get out of that page, that continues to complain it can't move due to lack of needed data. Further, if we'd picked "All", none of those are present (whereas on our test system, all our dimensions show up).

Any ideas how we clear that error condition?

Categories:

Financial Management

I have the same question (0)

All responses (13)

Answers (0)

Sort by

Suggested answer

André Arnaud de Cal... 306,250 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Ian,

There is a hotfix available for this issue. Not sure if this one is suitable for your current environment: KB 4055242 "Cannot edit a record" error when trying to open the Accounting source explorer form.

You can find details and similar known issues on LCS issue search.

Was this reply helpful? Yes No
Mark Schurmann 4 on at

Like
a
(0)

Report
Copy link

Link copied!

We have the same issue. There is a hotfix (KB 4055242) but it dates back to 2017. Surely, that is not what Andre is referring to. I don't see anything recent that would apply. We have 8.1.3 PU23 deployed, I can't imagine there are a lot of hotfixes available for this yet.

Was this reply helpful? Yes No
Mark Schurmann 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Also looked at the hotfixes available for the deployment. There are only 9. None apply.

Was this reply helpful? Yes No
André Arnaud de Cal... 306,250 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

I have tested a 8.1.3 customer environment and PU23. There is no issue on the accounting source explorer. It might be related to data or setup. Before changing the dimension set, try to Update the date selection to a period in the future where you have no transactions. Then try to change the dimension set. When opening the form, do you have a default dimension set selected or is it empty? In my case, a dimension set with only the main account was prefilled.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

It works on our 8.1 PU23 test system but not live on production, which has 7 periods of data on board (Vs 4 for the test system). So it sounds like the same thing that was previously patched - falling over when a description field exceeded 60 characters.

That said, I can't see how to constrain the date range - only the filter and account pieces (or ALL dimensions). On our test machine, all our dimensions show up.

Its one of our big surprises how shallow the reporting is on D365, both from MR and Power BI (the latter of which is okay for aggregations but useless to get down the the underlying detail). Still trying to get under the bonnet of the GL to see tax movements and values by tax code in our unified ledger. 7 months of trying, still not there...

Was this reply helpful? Yes No
Reto Mueller CH on at

Like
a
(0)

Report
Copy link

Link copied!

Hi All,

I have the same issue in an PROD and UAT environment (8.1.3 / PU23), but only for some time periods. January is working and from the 2nd of February i get an error msg.

Have you found a solution?

Thank you.

Was this reply helpful? Yes No
JacksNZ on at

Like
a
(0)

Report
Copy link

Link copied!

Hi all,

We have also joined the queue in regards to this issue.

clients upgraded to Version 8.1.3 (PU23) and the same error around accounting explorer surfaces.

The KB referred by Andre is dated 2017 and therefore I assume it is already included in the code for PU23.
is there any solution for this ?

thanks in advance

Was this reply helpful? Yes No
Suggested answer

JacksNZ on at

Like
a
(0)

Report
Copy link

Link copied!

...and it seems to have resolved once we perform a rebuild of the financial dimension sets .

Was this reply helpful? Yes No
Reto Mueller CH on at

Like
a
(0)

Report
Copy link

Link copied!

"Clear" all balances and "create balances" wasn't solving the issue in our system.

We have still the same error msg.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

For us, some time periods would display data and others would not. We chased it down to being an issue when journal entries crossed companies and there are multiple journal lines per voucher with “Customer” AccountType/OffsetAccountType. Through debugging we found that the MS code in updateCustPartyNumberPartyName() method needs to be reworked.

Working with MS they finally acknowledged this error and opened Issue 292933. The planned fix is expected to be included in version 10.0.2 and no info on if/when it would be backported to 8.1.3.

Thanks, Matt

Was this reply helpful? Yes No