Source Map Explorer
Peppin Kishore
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).
News that Microsoft would provide a hotfix was erroneous. Shortly after we received notice that a hotfix would be provided, Microsoft updated the KB with the resolution being to upgrade to 10.1 when available on April 5th.
Microsoft also provided a screenshot on how to fix the problem ourselves and said it was an easy fix. This leaves me completely baffled. They've done the work to figure out the fix. They can provide a hotfix for 8.1.3, but instead chooses to make everyone do it themselves.
I have not analyze the code in details yet, maybe you know it already, is there anything specific about ASE in PU23 compared to previous versions, that would have impact on performance? Is there anything we could turnoff to speed up generating this data.
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.
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...
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.
For your project specific question, all projects are stored in Projtable and posted transaction's against those projects in ProjTransPosting table which might be joined to subledger using SubledgerVoucher field from GeneralJournalEntry table.
Also to do that don't we need to have the account source explorer schema exposed in the data provider? Because I don't see that in the data provider. I only see plain data entities in the data provider.
I don't know which exact tables are used in the background by head. It is possible to reverse engineer the data provider classes to check how the information is being compiled together for the report.
Thank you @Andr for responding. When you say all relevant tables, is there any way I can get the details of all entities that AccountSourceExplorer is using? Because I'm able find all the details except the ProjectID and ActivityNumber for individual transactions only.
The accounting source explorer is compiled by x++ logic which fills a temporary table. You can export the details from all relevant tables to e.g. Data Lake and use Synapse or other tools to create the view you need or prepare the data in a particular way and then export it to be directly consumed by Power BI.
This article provides information about the Accounting source explorer page, which you can use for detailed analysis of the source information behind general ledger accounting entries.
The Accounting source explorer page shows source information. You can use it either as a stand-alone tool or to analyze the details behind general ledger accounting entries. For example, you can use the page to get the most detailed source information for a balance in the trail balance or for a voucher transaction. You can then use the Export to MS Excel feature to further slice and dice the information in Microsoft Excel (for example, in a PivotTable or on a PivotTable report).
The Accounting source explorer page always shows the same total amount per ledger account as General ledger shows (for example, in a trial balance). As in a trial balance, you can display segments in separate columns. Just select the appropriate financial dimension set.
In version 10.0.39, the accounting source explorer will have a performance boost by having a background process keep the recently posted documents updated and ready for viewing in the accounting source explorer.On the Process automation administration page > Background processes, there is a new process Accounting source explorer background preprocessing. This background process continuously looks for recently posted source document backed documents and keep the data structure used for the accounting source explorer up-to-date.
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
In this article I will describe the difference between these two options and also the effect of the feature 'Accounting source explorer advanced filtering' that is available since D365FO version 10.0.31.
In the trial balance left at the top you have the button 'Accounting source explorer'. When you click on this button, you will see the transaction of the selected main account and the date range of the trial balance.
The result is that the Accounting source explorer will be opened including a filter selection for this main account and the dates used in the trial balance. For these transactions available sub ledger source data will be presented for further analyzing or reporting:
Also in the 'Inquiries and reports' part of the General Ledger module you can find a link to the Accounting source explorer. In this case, if you open the function by the menu, the Accounting source explorer will be empty:
So that's a difference than opening from the trial balance. In the empty accounting source explorer, you can click on 'Update' on the top of the form to get the transactions. Here you find the parameters that you can use to filter the main account transactions that you want to present in the Accounting source explorer.
And this is where the new feature 'Accounting source explorer advanced filtering' can be used. Without this feature by 'Update' you only have the fields available in the form to get the ledger transactions you want to present. When you enable the feature this button 'Update' will be replaced by the button 'Advanced filtering':
So with this new feature you will have more capabilities to get only the general ledger transactions in the list that you really need to analyze. It is not a big change, but can be helpful when you use the Accounting source explorer for analyzing your ledger transactions.
The Data Source Explorer provides a list of configured connection profiles. If categories are enabled, you can see the list grouped into categories, for example, Databases and ODA Data Sources. Use the Data Source Explorer to connect to, navigate, and interact with resources associated with the selected connection profile. It also provides import and export capabilities to share connection profile definitions with other Eclipse Workbenches.
Hi everyone. We have a problem where the financial dimensions in the account structure for a certain legal entity is not being populated when running the accounting source explorer for the trial balance.
The source map explorer determines which file each byte in your minified code came from. It shows you a treemap visualization to help you debug where all the code is coming from. Check out this Chrome Developer video (3:25) for a demo of the tool in action.
--no-root: By default, source-map-explorer finds common prefixes between all source files and eliminates them, since they add complexity to the visualization with no real benefit. But if you want to disable this behavior, set the --no-root flag.
--no-border-checks: Disable invalid mapping column/line checks. By default, when a source map references column/line with bigger index than available in the source source-map-explorers throws an error indicating that specified source map might be wrong for the source.
The promise is rejected when there is a fatal error or all bundles explore failed. Reject reason is either explore result object (the same one returned when promise resolved) or Error object with code property specified.
When gzip option (or --gzip parameter) is specified result size calculated as gzip size. Due to the nature of compression a gzip file size is inaccurate. It means that removing a 1k gzipped file in a bundle may reduce the bundle size by less than 1k. Also it's impossible to calculate unmapped bytes because the sum of spans' gzip sizes isn't equal to gzip size of the source file.
In Google Chrome, you can collect code coverage stats. source-map-explorer accepts path to via --coverage argument (or coverage API option) and attempts to color code the heat map. This allows you to find the code that is not strictly needed for the initial page load and helps to identify the ideal ways to code split.
Red boxes correspond to code that would only be executed if the user took some action, or if some condition was met. For example, it may be a component inside of a dropdown the user never interacted with, or components that are only needed if the user opens a modal. In cases where the parent is green but the boxes inside are red, that means maybe some "initialization" logic ran, but the inner code never ran. Maybe we mounted a button, but not the other components in that module that are only needed if and when the user clicks the button, in that case, I would have the button trigger the rest of the code to load.
c80f0f1006