The Microsoft Dynamics 365 Business Central management solution for small and mid-sized organizations continues to expand after its launch, becoming available in new locations. Microsoft is investing a lot, and the product has improved significantly in the transition from Project Madeira (the first one) to Finance & Operations Business Edition to its current form. The product now contains all the existing features in Dynamics NAV 2018, with the remaining constraint (acceptable, in my view... Read the full text.
↧
Blog Post: Why organizations will choose Microsoft Dynamics 365 Business Central - and what users still need
↧
Forum Post: Lifespan of a temporary table variable and events
I guess I should know this already, and I thought I did, but having problems with a temporary table. I think it's related to it being called via an event. I have a requirement in which I have a purchase order, which is generated from order planning. The function has been changed so that instead of creating a separate purchase line for each purchase demand in order planning, it is create a single line with a reservation against the original demand (job planning lines). When a warehouse receipt is created against this purchase order, then the purchase line is split into a line per original demand. So if a purchase order line was created based on demand from 4 different job planning lines, then it will also create 4 different warehouse receipt lines all referring to the same purchase line. So far so good! Unless I did more code, then it standard would only update the first receipt line, so I need to loop each purchase line to insert the temporary receipt line records. Codeunit 90 (Post) Codeunit 5760 (Update temp rec) Codeunit 90 (Finalize) Codeunit 5760 (Find temp rec) I did this by creating a new event, which is calling a new codeunit, which again calls the same codeunit and function to insert the posted receipt lines and update the temporary records. Codeunit 90 (Post) Event> Codeunit 50000 Codeunit 5760 (Update temp rec) Codeunit 90 (Finalize) Codeunit 5760 (Find temp rec) The problem now occurs when finalizing purchase order. When trying to find the temporary records using CU 5760, then the temporary table is empty. So the question is really, how to keep the update Temporary table and keep it "alive" in memory, so that I'm still able to finalize the posting.
↧
↧
Forum Post: RE: How TO Implement Bar Code in Tax Invoice in Navision 2016
Please refrain from posting email addresses directly in posts!
↧
Forum Post: RE: Printer takes A4 size instead of custom size that I have defined in report layout
Then you need to select the correct size both inside the RDLC report layout and also selecting the correct printer and papersize from Windows.
↧
Forum Post: RE: VAT Receivables report including CPV and BPV?
Nothing to do with the localization. We want the report in one piece. As of now they are 3 reports and the accounts dept clubs it together .
↧
↧
Forum Post: RE: Posted BPV invoices not in G/L registers
I got the answer for this Erik P. Ernst ex. a Entry with no. 100056 has ten entries till 100065. Then i can find the entry 100060 in the G/L Register of entry no. 100056. Thats it
↧
Blog Post: Three key factors of a successful Microsoft Dynamics NAV project
My last project was unusual. We were able to replace an existing ERP system with Microsoft Dynamics NAV in time and under budget. In this article, I will highlight three key factors which were responsible for this success, that are applicable to any other Dynamics NAV project. Looking back from a personal perspective, this project was not so unusual in certain ways. It was a success for all parties involved. There are many elements in any project which determine its success... Read the full text.
↧
Blog Post: Inspire 2018: Microsoft expects to add sixteen more countries for Dynamics 365 Business Central in 2018
Microsoft and its partners plan to bring at least sixteen more countries onto Dynamics 365 Business Central through the end of 2018. Reporting from Inspire 2018, Microsoft MVP Alexander Ermakov of Awara IT has documented several details of the Business Central roadmap , including the (already planned) brand unification with NAV for on-premises deployments starting in fall 2018 and a new effort to position the theme of "Intelligent Edge" in the context of (presumably new and improving... Read the full text.
↧
Forum Post: RE: VAT Receivables report including CPV and BPV?
[quote userid="202184" url="~/nav/f/users/94580/vat-receivables-report-including-cpv-and-bpv/498356"]Nothing to do with the localization.[/quote] Well it does! The acronyms CPV, BPV, PPI, PSI, TRN etc. are not part of the world wide version, or my Danish localization for example. They may be in your localized version of NAV or they could have been added as part of an add-on or customization. So without knowing this, then it's hard to say what you need to do, as it may have been implemented differently. Also if it's part of YOUR localized installation, then some of our other members could know the answer, if they run the same localization.
↧
↧
Blog Post: Caution: Your program license expires in xx days.
We recently updated our SPA agreement with Microsoft, and after signing the agreement, we were able to download brand new development license with extended expiration date, which is always nice. Our customer development databases have always File/Database/Alter, Integration, "Save license in database" set within the Development environment. This ensures that if you happen to have different NAV versions in the same database server, you will not accidentally use a license from another NAV version when you are developing new interesting features to your customers. I started updating the development licenses to databases, and almost all environments that were older than 2018 went as nicely as expected. One NAV version however gave the error twice , and after installing the new license I still kept receiving the error, this time only once though. The reason appeared to be that someone (ehm, probably me) had replaced Cronus.flf with our old development license. This was easily fixed by copying the Cronus.flf back to its right place In the old days you could achieve the same thing with "Export license" functionality in Development environment (and probably unintentionally replaced your Cronus.flf with whatever license happened to be installed on the SQL server). Luckily Microsoft has since removed the unneccessary buttons from the License view, and there is nowadays only Upload and Change buttons visible. But then, first NAV 2018 database and upload new license, and the expire error did not disappear . I was baffled, and checked the Alter database section, everything was fine there, Save license in database set as usual, but the error still kept appearing. Next I checked the Master database, there was the usual $ndo$srvproperty table, but there was an entry with some license binary . It seems like NAV checks first the Client folder, then Master database for license, and only after that the NAV database for license. Ok, I deleted the record, it was the old license anyways. Boy, was that a mistake . Next error I received was a bit more serious: --------------------------- Microsoft Dynamics NAV Development Environment --------------------------- The NAV2018_CU06 database on the DEVNAVSQL2017 server does not contain Microsoft Dynamics NAV Development Environment system objects and cannot be opened. --------------------------- OK --------------------------- What? did I break it for good? Not a single one database on that server agreed with me after that. At this point I started sweating a bit (well, it is unusually warm in Finland this summer), and continued investigations. I remembered that I had seen something with $ndo$srvproperty table earlier, and checked my old blogs. I found the blog, but that did not help much. I could not connect the Development environment to upload the license to database this time. Finally, I took a backup of the Master database, and deleted the whole $ndo$srvproperty table from Master, tried reconnecting and phew! It worked. The moral of the story? NAV sometimes stores license to Master database even when it is not supposed to, and if that happens, you have to delete the $ndo$srvproperty table in order to recreate it next time you connect Development environment to that SQL server. For those who wonder where NAV stores the license if License per database option is set, it is located in NAV_Database/ $ndo$dbproperty table, license field. Edit: Fix some typoes
↧
Forum Post: RE: How to deploy disassembly in nav
We have a customer that was into disassembly of battery and they want NAV so they want disassembly of battery as a production order in NAV so how can I implement it
↧
Forum Post: RE: How to deploy disassembly in nav
We also have customer that was demanding for a real estate module on NAV so what are the tables, pages and codeunit that will required and how to implement it
↧
Forum Post: RE: How to deploy disassembly in nav
Hi Sakiru, I would normally recommend that you contact your partner about such questions. But then I saw that you write in your profile that you work as a technical consultant at a Dynamics partner!! If you as a Microsoft Dynamics partner need an add-on then you can search your normal channels. Microsoft has an online portal of ISV's solutions for NAV. Don't know about a "disassembly" add-on, but I would not be surprised if one existed. Or contact your local Microsoft office? Same with the real estate, but here I know there are some ISV products "out there". But not sure if they are in your country?
↧
↧
Blog Post: From the Microsoft Dynamics 365 Business Central/NAV Blogs: Dimension combinations; GL account; Extensions/apps; Production scheduling
This week on the Microsoft Dynamics 365 and NAV blogs: How to block dimension combinations in Dynamics NAV or Business Central To create or not to create a GL account Developing Business Central extensions or apps in team Production scheduling with NAV: Keep material availability in check How to block dimension combinations in Dynamics NAV or Business Central On the Encore Business Solutions blog, Iaroslav Pankovskyi focused on how to block certain combinations... Read the full text.
↧
Forum Post: RE: Job Invoicing
Hi, We run NAV 2016 as well and do our monthly maintenance invoicing in a batch. This was a requirement when we implemented NAV 2016, so not sure if there is out of box functionality or it was something we had modified to make it happen.
↧
Blog Post: Why we went to NAV 2018 CU 06
Start of this year we upgraded our NAV 2016 installation to NAV 2018 RTM. And February 26 we were live. It was a relative smooth and fast upgrade and we were quite pleased with it. We ran however into a couple of performance issues of which one them exposed itself immediately after go-live. We were pointed to it by one of our sistering team's consuming a number of NAV web services in their application. But unfortunately we couldn't get a hold on what was exactly happening, so it was lingering until a month or so later we were confronted with a seemingly different issue, but with the similar pattern. Our sistering team reported that, while sending data to NAV through a web service the following exception occurred frequently: For search engines sake, let me phrase the essential part of this even viewer screen: The sql connection doesn’t have a database instance attached. This must not happen if the connection comes from the pool. We had no idea whatsoever on where to find the cause (and solution!) and we let it be for the time being. It was not a showstopper in the operation as the major part of the web service calls were successful. Until some 6 weeks later, when a new project had started with an external partner connecting to a new web service, experiencing a same kind of issue. Roughly every 10th call connecting to NAV failed resulting in a 1000 longer waiting time and timeout: “ Apr 25 07:33:01 Update box: Time: 273 ms Apr 25 07:34:02 Update box: Time: 278 ms Apr 25 07:35:01 Update box: Time: 285 ms Apr 25 07:36:01 Update box: Time: 274 ms Apr 25 07:37:02 Update box: Time: 282 ms Apr 25 07:38:01 Update box: Time: 279 ms Apr 25 07:39:01 Update box: Time: 288 ms Apr 25 07:40:02 Update box: Time: 355 ms Apr 25 07:41:01 Update box: Time: 272 ms Apr 25 07:42:02 Update box: Time: 272 ms Apr 25 07:43:01 Update box: Time: 266 ms Apr 25 07:44:22 Update box: Time: 21.40 sec Apr 25 07:45:02 Update box: Time: 291 ms Apr 25 07:46:01 Update box: Time: 280 ms Apr 25 07:47:02 Update box: Time: 285 ms Apr 25 07:48:01 Update box: Time: 274 ms Apr 25 07:49:01 Update box: Time: 268 ms Apr 25 07:50:02 Update box: Time: 290 ms Apr 25 07:51:01 Update box: Time: 291 ms Apr 25 07:52:01 Update box: Time: 272 ms Apr 25 07:53:02 Update box: Time: 288 ms Apr 25 07:54:01 Update box: Time: 283 ms Apr 25 07:55:01 Update box: Time: 284 ms Apr 25 07:56:02 Update box: Time: 276 ms Apr 25 07:57:01 Update box: Time: 282 ms Apr 25 07:58:02 Update box: Time: 270 ms Apr 25 07:59:23 Update box: Time: 22.29 sec “ Our request for help on this issue towards MS was answered very fast resulting: Our team investigated the exception The sql connection doesn’t have a database instance attached. This must not happen if the connection comes from the pool. and discovered that we have fixed a bug for Dynamics 365 Business Central titled Connection pool - concurrency issues when disposing NavSqlConnectionScope that has not been backported to NAV2018 (and the exception trace that you provided looks similar to the one we saw when fixing this bug) We have created a backport bug to have this fixed in an upcoming CU for NAV2018, preferably CU 06 And indeed it was released in CU06 for NAV 2018 as hotfix 267998. Once installed it did indeed fix the issue. No hiccups when disposing NavSqlConnectionScope . Thanx to the MS team that helped us out.
↧
Blog Post: Dynamics 365 Business Central: object prefix for AppSource extensions Q&A
Answers to a post-course question regarding object prefixes in extensions for AppSource: Object prefix must be registered with Microsoft (at least 3 digits) and must be unique (it’s globally reserved for you) It can be a prefix or a suffix (you can call an object XXXMyTable or MyTableXXX ) You have to use it for every objects in your extension This is case insensitive (you can call an object XXXMyTable or xxxMyTable ) You can use the prefix in any format you want ( XXX_MyTable , XXX-MyTable , XXX.MyTable , XXX MyTable etc. are all valid names) You can register more than one prefix (you can have a prefix for app but I think this is not a good way to do, I prefer a prefix for company) Functions in your extension objects cannot have the prefix/suffix in names (the prefix is in your object name, so you can have something like XXX-MyCodeunit.MyWonderfulFunctionNameLongAsIWant() ) If you have extension A that depends on extension B and extension C, and both B and C adds a function MyFunction to a standard table (Customer table for example), if you call Customer.MyFunction you receive an error on compilation (ambiguous call) This is all what I know regarding prefix/suffix rules. Feel free to add if you know more P.S. My absolutely personal opinion: I’m not a fan of object prefix/suffix. I think this is something not very “elegant” and clean and for me it’s only a simple workaround against a big lack in the actual AL framework: the missing of namespaces. A namespace is designed for providing a way to keep one set of names separate from another. The class names declared in one namespace does not conflict with the same class names declared in another. I think we have to copy something from C#: using System; namespace name1 { class MyClass { public void func() { Console.WriteLine("Inside name1"); } } } namespace name2 { class MyClass { public void func() { Console.WriteLine("Inside name2"); } } } class TestClass { static void Main(string[] args) { name1.MyClass class1 = new name1.MyClass(); name2.MyClass class2 = new name2.MyClass(); class1.func(); class2.func(); Console.ReadKey(); } }
↧
↧
Forum Post: RE: Job Invoicing
Hi Steve =
↧
Forum Post: RE: Job Invoicing
Hi Steve =
↧
Forum Post: RE: Job Invoicing
Hi Steve - If you are using Jobs you create sales invoice from Jobs and you can do batch invoicing from Sales which is out of box NAV, no customization is required.
↧