November 3, 2017
ArcherPoint Dynamics NAV Developer Digest - vol 164
The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful. As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.
Too Many Decimals to do Fixed Asset Depreciations?Kyle had to fix a problem with a customer that somehow got Fixed Asset depreciations imported with too many decimals. Enough decimals that you couldn't do disposals or further depreciation. He wrote a small SQL script to fix the entries. use [CORNAVSQL] go declare @EntryNo int declare @FALoop cursor declare @Counter int set @FALoop = cursor for select [Entry No_] from [dbo].[COR - PROD$FA Ledger Entry] open @FALoop fetch next from @FALoop into @EntryNo set @Counter = 1 while @@FETCH_STATUS = 0 begin update [dbo].[COR - PROD$FA Ledger Entry] set [Amount] = ROUND([Amount], 2, 1), [Debit Amount] = ROUND([Debit Amount], 2, 1), [Amount (LCY)] = ROUND([Amount (LCY)], 2, 1) from [dbo].[COR - PROD$FA Ledger Entry] where [Entry No_] = @EntryNo and [Amount] > 0 update [dbo].[COR - PROD$FA Ledger Entry] set [Amount] = ROUND([Amount], 2, 1), [Credit Amount] = ROUND([Credit Amount], 2, 1), [Amount (LCY)] = ROUND([Amount (LCY)], 2, 1) from [dbo].[COR - PROD$FA Ledger Entry] where [Entry No_] = @EntryNo and [Amount] < 0 fetch next from @FALoop into @EntryNo set @Counter = @Counter + 1 end close @FALoop deallocate @FALoop select @Counter
Adding Default Dimensions to the Dynamics NAV Location CardDenise B: Location Default Dimension, has anyone added default dimensions to the Location Card? Trish: Yes. The scope on this type of modification can be huge, but in this case the client limited it to the Revaluation Journal only. A custom action was added to the Revaluation Journal to update the values for a single Dimension Code from the Location Card default dimensions. The user selects the custom action after running the Calculate Inventory Value function, which establishes the Revaluation Journal records. Kyle: You would have to decide on an order that wins (e.g., Customer? Item? Vendor? Or your location?). Matt: You don't have to decide, that's what Default Dimension Priorities are for. As long as you run it through the appropriate places in Dimension Management you should be fine. But there are a lot of places to change that code. Thanks to the ArcherPoint developers, customer service reps, and consultants that make the Developer Digest blog possible! Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center. If you are interested in NAV development, be sure to see our collection of NAV Development Blogs. Read more "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV.
- Login Error: Communication protocol mismatch between client and server
- Creating a Date Table in Power BI
- The Top Eight KPIs Retailers Should Be Tracking (with Formulas) for Your Retail KPI Dashboard
- Difference Between IaaS, PaaS, and SaaS And When You Need to Use Them
- The Microsoft Technology Stack – What It Is and Why You Should Care