You’re offline. This is a read only version of the page.
162
A customer currently uses Dynamics NAV 2018 and is planning a reimplementation to Business Central cloud. Within the NAV system they use Items and Lot Tracking for Orders and shipments. As part of the reimplementation they would like to bring across x years of Item Ledger Entries for reporting purposes.
The only way I see of achieving this properly is via an Item Journal, however this wouldn't be accurate as it only displays for positive or negative entries and you would look visibility of this being a receipt etc. I do not want to even consider writing directly into the Item Ledger Entry table copies of the existing entries.
Is there any advice on the best way to essentially bring across transactional history of Item Ledger Entries, or is the proposal to only recreate open Item Ledger Entries via an Item Journal, and advise on storing the existing Item Ledger Entries in another database and a data warehouse to assist on reporting?
I am looking for any suggestions, thank you.
How heavily modified is their 2018 version? If there are not too many customizations you could consider to migrate the complete database. Then you will have all the current history intact,
I would say that this business use case is not new and happens often. However the decision depends on > How flexible is your end-customer in keeping this "historical" data away from their "brand new" Business central system?
If they are flexible then you should suggest them to only import the opening balances via item journal, probably a month detailing is fine but not more than that. Thereafter you can move their old database in a place from where Power BI developers can access this DB and pull reports for the past X years. Now when their BC starts operating, they'll have old data from P-Bi (Extracted in an excel) and also their current data from BC
If they are rigid and they want X amount of data, my friend, you'll be burning the midnight oil to import & reconcile but more than that even if some $ go off here or there, you're screwed big time. In this case I'd suggest the best way you have is Item Journal. I know you don't get to see your receipts and your transfers, I think that's how it works and that's the way you should follow, rather than going for any kind of a manual data insertion into ILE
Note: Most of the time accountants are concerned with what inventory transactions happened within the current FY. To them, what happened 3 years ago, is just for analytical purposes. I'd suggest to the Power-Bi way for historical data analysis and let the old DB stay as is connected with only P-BI. You can also build another report in P-BI which will fetch fresh data from their brand new BC system, this way the customers will have best of both worlds
What I see eventually happening is if you even manage to import X Years of historical data through Item Journals, 3 years down the line when their data becomes ginormous GB's into BC itself, their excels would fall to the knees and they'd be anyways looking for BI tools (Like P-BI, Tableau or jet Reports). It is important to paint this picture in front of the customer that if data analysis is all that matters, it does not matter where the data is stored, as long as it is secure
Sometimes customers can be fussy about their data but that does not mean data is not important nor does it mean that there aren't methods to tackle it. Tackle it wisely, show them the bigger picture
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,134
Super User 2024 Season 2
#2
Martin Dráb
229,928
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (