D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

D365FO 8.1 PU23 - AccountingSourceExplorerTmp error - how to clear?

  • 1.  D365FO 8.1 PU23 - AccountingSourceExplorerTmp error - how to clear?

    SILVER CONTRIBUTOR
    Posted Jan 29, 2019 04:23 PM
      |   view attached

    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?



    ------------------------------
    Ian Waring
    Finance Special Projects
    Jisc
    Harwell Didcot
    ------------------------------


  • 2.  RE: D365FO 8.1 PU23 - AccountingSourceExplorerTmp error - how to clear?

    MICROSOFT MVP
    Posted Jan 30, 2019 08:59 AM
    Hi Ian,

    You asked the same question on the Dynamics Community. I had provided an answer on that forum: https://community.dynamics.com/365/financeandoperations/f/765/t/308666

    ------------------------------
    kind regards,

    André Arnaud de Calavon
    Solution Architect, Microsoft MVP - Microsoft Dynamics Business Solutions
    ------------------------------



  • 3.  RE: D365FO 8.1 PU23 - AccountingSourceExplorerTmp error - how to clear?

    SILVER CONTRIBUTOR
    Posted Jan 30, 2019 09:23 AM
    We're looking at that patch which was released in Nov 2017. We're on the latest version of D365FO V8.1 PU23 as released Jan 2019, so we thought the patch would already been in there (it's not listed as applicable in LCS - 9 issues since the weekend mainly on stock or retail POS issues). Will report back if this solves it.

    ------------------------------
    Ian Waring
    Finance Special Projects
    Jisc
    Harwell Didcot
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role