You can add the "Departments" button in Navigation Page back without losing other customization by following process.. 1. Export Profile to xml file using "Export Profiles" action in Profiles list. 2. find the following node " " in xml file and remove that line and save the xml file. 3. Delete the profile from Profile list in Nav 4. Import the edited profile using "Import Profiles" action from Profiles list. this will add Departments back without losing other customizations.

Hello All, I have integrated Nav 2018 and power bi . By setting up azure directory setup and creating app in azure portal. After the integration i could select report which i created using customers page Odata in customers page of Dynamics Nav. Now i can see the reports, but as per Nav 2018 update. I need to see the interaction betwen customer page of nav and customer power bi report. Say it need to be react and filter the power bi reports when i selct any on record in customer page. But i could'n t see interaction , please help me to solve this, its an urgent requirement.

You are invited to join your peers at User Group Focus North America, located in Houston, Texas, March 13-14, 2019 for concentrated Microsoft Dynamics 365 Business Central & Dynamics NAV education. Register here. User Group Focus is a can't miss, deep-dive training event . Attendees will be able to: Sharpen your skills and learn best practices to further your job role, career, and product investment. Network with peers who are in similar roles and face the same issues on a daily basis. Dig deeper into the topics most pertinent for success in your role. Each 90-minute session is taught by a technical or functional expert and features primarily intermediate-level content. Submit session ideas through December 14 As an event built by users for users, the programming committee relies on the volunteer efforts of the community to provide the most relevant and useful deep-dive session topics. The 2019 BC/NAV role-based tracks are still being determined, but last year's were: CFO/Controller: Advanced insights on how your team can use the application and related tools to achieve your financial and strategic objectives. Developer: Get up-to-speed on the significant changes to the development environment and tools over the past two versions. Distribution/Logistics Manager: Sessions to help you take advantage of the latest innovations in processes and technologies to improve your supply chain effectiveness and efficiency. BC/NAV Administrator: Best practices and tips you should know to be more efficient and productive, while reducing risk and errors. [Submit Session Ideas] SUBMIT You will also be able to attend Power platform deep-dive sessions at no additional charge. Dive in deep and emerge the expert you always knew you could be! Save $100 on User Group Focus registration through January 15. [Register Today] REGISTER LEARN MORE

Maybe a solution for this would be refactoring the code so every time a dimension or value is inserted or deleted, they gets inserted/deleted to other companies as well. I know this does not fix the issue, only the appearance, but that is what I would do. There are multiple issues with Job Queues, and that is mainly the reason why MS has rewritten it to NAV2017 and later versions. Oh, I also came to think one basic thing you could try; if you have not re-compiled all objects after upgrade, you should do it now.

I think that Migration to 2018 is the best solution Urpo. Thanks for answer!

Could you solve this problem? I'm stuck two.. when I create prices from that worksheet the margin is always filled with "0"

All the people that were on my Dynamics 365 Business Central Development courses for Microsoft Italy (and that will be in the next months) already knows that one of the topic that I always I try to emphasize is related to source code management . Source Code Management  (SCM) is a must to have when working with AL (code is now on files and not inside the database as in C/AL) and you absolutely need to have a good SCM system in place inside your organization. Normally during my courses I provide a practical overview of two systems: GitHub Azure DevOps Normally I emphasize the SCM features of these two platforms (GIT support etc) and how you can manage projects and repositories (pull, push, branches etc) directly from Visual Studio Code. Both are great platforms for SCM with GIT. For free , GitHub provides unlimited public repositories but no private repositories, while Azure DevOps gives you unlimited public and private repositories for teams with a maximum of 5 people (over that number you have to pay for users). When people asks me what I prefer or what I recommend, I’ve no doubts on the answer: Azure DevOps . I think that for working in teams inside a company (so not only for open source projects), Azure DevOps is much better and it offers many more features that GitHub. The main differences in my opinion is expecially related to project management and testing/pipelines. I’m not an Azure DevOps guru for sure, but I want to talk here a bit about many interesting Azure DevOps features that you can start using from today for managing your Dynamics 365 Business Central development projects. To start, first of all you have to open a new project in Azure DevOps, select the project visibility (public or private), the Version Control system (GIT or TFS) and the Work Item Process you want (Agile, Scrum etc): When the project is created, you can go to the project page and start to invite your team’s members: When the project is created, a GIT repository is created online for you (and from here you can clone it locally etc., I don’t talk about that now). As a project manager, the first thing you can do is to click on Backlogs and create a backlog for your project (product backlog corresponds to your project plan, the roadmap for what your team plans to deliver). Here you can create phases and tasks and assign that tasks to users: On the right side of the Backlog page you have the Sprint panel. With Scrum methodology, teams plan and track work at regular time intervals, referred to as a sprint cadence . You define sprints to correspond to the cadence your team uses. You can select a Sprint, define the starting and ending date and then assign activities from Backlog to a specific Sprint by dragging the activities (here for example I assign the Customer Category Development activity to the Sprint 2): After scheduling activities and sprints, you have also other interesting views. If you click on Work Items , you can see the work items status (only work items assigned to you, all work items etc): If you click on Boards , you can have a board of your project (view of your project tasks as card ordered by status where you can move tasks by using drag & drop in order to change their status): If you select Sprints you can see details of every sprint (iteration path) defined in your project. Here you can have a Taskboard view and you can see the sprint backlog and capacity: From here you can monitor the progress of every sprint. Another interesting feature that I use quite often is what is called the Delivery Plan . Delivery plans display work items as cards along a timeline or calendar view and this is very useful to see expected release dates or delivery dates for your team activities. Delivery Plans are not a standard feature and to have them you need to download and install a Microsoft’s DevOps extension from the marketplace (click on the bag icon on top right corner of your page). The extension is the following (Microsoft, please add it as default in a project workspace): When installed, you have a new menu called Plans on the left and by clicking on it you can see your project delivery plan on a timeline: The coolest part is that all these project management features are available in a single tool and are totally integrated with the development tools you use every day (alias Visual Studio Code). Just as a quick example, I can click on Repos and clone the GIT repository to a local folder on my machine: You can choose where to create the repository and in few seconds you have a local GIT repository connected to your Azure DevOps repo: To use Azure DevOps repositories with Visual Studio Code, you need to install the Azure Repos Extension for Visual Studio Code : Yu can connect to your Azure DevOps repository by using the Team:Signin command: For authentication, select the following method: When connected, you can start work with your AL project. You’re working on a GIT repository, so every time you modify a file the GIT icon in Visual Studio code alerts you that you have some pending changes. When you’re ready to go with your work, you can click on the GIT icon in Visual Studio Code, select the 3 dots icon and then click on Associate Work Items : This is not mandatory, but if you work with work items and sprints I recommend to do so because with this feature you can associate your commit to a work item (you can select to the work items assigned to you): When the work item is selected, you can commit your changes (file by file or entirely for every modified files) by clicking the Commit icon (you can see the branch you’re working on in the bottom left corner): Now you can push the modification to the remote repositoy on Azure DevOps: Now, if you go to Azure DevOps and select Repos –> Commits you can see your commit phase: If you have to perform large code modification/implementation, you can work with branches . You can create a new branch directly from Visual Studio Code by clicking on the branch name in top left corner: When you push your code modification on the new branch remotely, a message appears: By clicking OK, your newly created branch is published online. You can see it on Azure DevOps on the Branches page (here you can see your branches and also all the other branches published by other team members): When the work on the branch is finished, you need to merge it to the master branch. To do so, you need to create a pull request and you can do that directly from Visual Studuo Code: This action will open the New Pull Request page in Azure DevOps. Here you can create your pull request: All pull requests are visible in the Pull requests page: You can select a pull request, review it (see code modifications and so on) and then approve it: When the pull request is approved, click Complete . Now you can select to mark linked work items as completed and to delete (or not) the branch that you’re merging to the master: Click on Complete merge to start the merging phase. When the pull request is completed, you receive a notification: Your master branch is updated and the result is graphically displayed on Commits : This is a quick introduction on how to manage a code lifecycle management for your Dynamics 365 Business Central development projects with Azure DevOps. As you can see, all is perfectly automated and managed by a single platform. This works with Visual Studio Code but obviously also with Visual Studio and other project types (like .NET applications etc.). The platform permits a complete team working between developers and project managers/testers/consultants in a single unified platform. I highly recommend to give Azure DevOps a try, it’s really a great tool. With Azure DevOps you can do also other things like Pipelines, Test Plans and Artifacts, but it will be another story…

Hi All, In order to better meet client needs I whould like to sell Dynamics NAV 2018 subscription at a fixed price billed every 2 years. Is it possible? Best Regards, John

Regarding Microsoft, it's not possible (you need to pay as per official agreement). I don't know if you can change the policy of how customers pays you...

It seems correct to me, this is an array of objects: [ { "Height":60, "Width":100, "Lenght":55 } ]

I dont think so. The problem is the trailing slashes \ and the quote A valid array would be { "itemAttributes": [{................. }] } but in my case I get { "itemAttributes": "[{.....................}]" }

You’re right, missed the “. I think it’s because your itemAttributes field is a text field. You should do like the baseUnitOfMeasure field, so in the API Page a field with a tablerelation. Check how that field is managed.

ok thanks. I will try this and get back to you

Dear Team i have one scenario related to Service Order ,i need solution on that. Customers come to repair his computer ,Technician check and he find RAM issue ,this RAM in company assets hence he created PO using that Particular fixed assets its approved and released . now i need to convert this item to as inventory Item and register in service order .because in service order no option to select fixed assets .what is the best practice to solve this case please help me .its in Navision 2018 Thanks and Regards Akhil

Hallo vrtlog, no unfortunately I did not. We did not follow this topic further. I think you have to develop a Codeunit with C/AL inside NAV and connect a Webservice to it.

If you, like me, have been part of the Navision community since 1990, then you have seen a lot. 10,000's of members of Dynamics User Group (prev. Navision.net/NOLUG) have come and gone again. Some stick around and with time becomes dinosaurs like me. But a lot of them, we only see 1-3 months, then never hear about again. And while I don't know the exact percentage, but my guess that a lot of them, are no longer working with NAV. At NAV TechDays 2018 two weeks ago, my friend David Singleton and had a session about The future for NAV developers and consultants . One of the things we talked about, was how our channel will need to double the number of developers within the next five years. If you didn't watch our session, then let me recommend it. Just remember to turn up the volume, as the sound is very low. If we need to 10 double the number of customers and only double the number of developers, then a lot needs to happen. Most importantly then our industry needs to mature and do it fast. Especially we the developers, we need to become even better at our work. Everything we code in the future must be written with both repeatability and extendibility in mind. We all need to become "real developers", not continue as mostly self-learned amateurs, who barely knows what a design pattern is. C/Side – a blessing and a curse Navision and Dynamics NAV have always been unique. C/Side has been both a blessing and a curse. When Navision 3.0 was released in 1990 it's integrated development environment (IDE) was the very first of its kind. Here we had a platform where could customize all parts of the standard application, primary by just changing or adding properties in objects. And in some places, we could also program code. For this purpose, PC&C had created a development language (AL), which they had based upon the Pascal language. In the 1980'ies this was one of the most popular development languages in the PC world. Most "developers" did not have a formal IT or development education or background and being a "Navision developer". And those who did, could not apply much of that knowledge to Navision. Everything in IDE was unique for our application, everything had to learned again. That made it more common to take an end user, accountant and turn them into a Navision developer, than it was taking an experienced developer and turn them into a Navision Developer. Business and accounting knowledge where more important that actual programming skills. That again let to a lot of consultants also changing the code. Many, including me, started their career as consultants, and gradually became developers. It didn't mean that partners didn't know what they were doing. IBM Business Centers Besides having a superior accounting package for the "new" PC's, then one of the main reasons why Navigator got both rapid growth a very good reputation in Denmark was that it was sold by IBM Denmark through a network of IBM Business Centers. These business centers were the only partners, who could sell both IBM PC's (PS/2's) and IBM-Navigator to Danish businesses. And they did it well. To become an IBM Business Center, the partner had to undergo a rather long certification process. Their sales people, technicians, consultants and developers had to participate in week-long training, before they could go for the actual certification tests. Developers where not called developers, but system engineers and where basically trained to become Navigator specialists. We had to know everything from installing, setup, migration, training to development. It was neither easy, nor cheap to become a Navision partner at that time. The program worked great and was a very trusted. And most IT managers knew, that if they just stayed with IBM, then they would never get fired for choosing a bad brand. Everybody trusted IBM back then. Are certifications the answer? Certainly not! It was not the certifications in the IBM Business Centers which made the difference. It was the week-long trainings , it was the way that IBM Denmark helped implementing a complete methodology covering all aspects of the partner – full package. It gave the whole company a boost in professionalism, compared to most non-IBM business centers, who instead had to sell the Navision "copy" XAL (XAL = e X tended A pplication L anguage from Damgaard). Microsoft stopped certifying Dynamics NAV professionals a couple of years ago (2013?), when they dropped this requirement from their partners. Next year Microsoft will bring them back, according to announcements at Directions. If these certifications are going to be the same type of test with typical multiple-choice questions, then they are worth nothing. Sure, it will require that you either study or go online and find someone who sells the answers for the test and then just memorizes the answers. Other than showing that you can memorize, then they really show nothing. The only thing that truly works is training, mentoring and real-life practice. C/Side retirement In 1-2 years, Microsoft is going to retire C/Side. It will then no longer be possible to use C/Side or C/AL to make changes. We can then only use Visual Studio Code and the new AL language to program our changes. That does not mean C/Side is dead. According to their terms, then they will continue to maintain it five years from its last release. If C/Side is retired in two years, then there will still come updates until 2025, even if no new functionality may be available. And there will for sure still be customers running it in both 10 and 15 years. Just was there is still customers running the DOS version, here 23 years after the Windows version was released. That is going to be an important factor for Microsoft, to be able to get from 330,000 NAV customers to 3,300,000 BC customers. For many years C/Side has been one of the reasons, why it has been difficult to attract new professional developers in the market. Methodologies and practices, like Agile, Scrum, SCM/versioning, object-oriented design, clean code, design patterns, test-driven development and CI/CD, have been known and used in other parts of the IT industry for decades. That's what students learns at the universities these days. Sure, Agile and Scrum has made its way into our world, and we have visionary NAV community members like Luc van Vugt, Mark Brummel and many others current and former MVP's, who have showed that it can be done in our world too. I'm looking forward to C/Side's retirement. What once was a blessing, has turned into a curse, that eventually, would have meant the dead of Navision. I just hope that more people in our channel had already embraced these new standards and methodologies. Dinosaurs wake up! Most NAV and BC developers do it the way they always did. No use source code management (SCM), DevOps or Docker, no focus on clean code, design patterns or test codeunits. Maybe on some projects, but not on everything. "Who would pay for it?" they ask. To them it is just means more costs, more stuff preventing them from billing out hours. They need to see beyond that. We cannot make great high-quality software build for repeatability, extendibility and maintenance, if we do it the way we have always done. We have the tools, we need to stop seeing it as an extra cost, when all studies have shown differently. Even if you only do once-off projects, then it does cost more to do it right. From before they were born Why would graduate's, who studied 2-5 years to become professional IT developer's, want to forget almost everything and go to work in an industry, where almost everything is based upon the almost 25-year-old user interface in C/Side? Very likely from before they were born! With a development environment in Visual Studio Code, that is no longer. Not only a (familiar) modern user interface you can use both on Windows and Mac, and no matter if you code JavaScript's or AL code. We get build-in Git/Github SCM, easier CI/CD with Azure DevOps, Pipelines, Containers and much more. All these "standard" tools, that we now have available, will make it easier to attract new developers. Except that alone will not do it. Even if they have the right tools, as soon as they find out that the projects and the development is done the way it was done 25 years ago, then they will accept the next job offer they get. We either change the way we look at our profession or forget about attracting the best graduates and candidates. And forget making Business Central a success. A Navision developer was not a real developer I started as a NAV consultant/project manager in 1990 and first became a Navision developer in 1992. Still it took many years, before I started seeing myself as a real developer. I even studied programming in college, and I have over the years used over 10 different programming languages, excluding AL, C/AL and the new AL. In Navision most of our changes were simply changing a property or inserting a new field. Or a new report, with a few lines of code. Not a lot of "real" programming. We didn't have to care about frameworks or all sorts of things to create UI or access our database. Instead we had all sorts of integrated tools to help to most of the actual code for us. Unless we exported as text, then we never saw the actual code. We didn't have the tools to do it the right way, nor did we mis them. A new developer may initially have requested new tools, but we quickly learned them, they didn't need those tools for NAV development and that they just slowed us down. We mostly did once-off projects and didn't have to care (much) about future upgrades. Eventually in 4-5 years that would be an issue, but not now. So, who would write test codeunits for anything? Today we know we were wrong, writing code we did, always ends up being spaghetti. If I look back at those days, then although much have changed, then we still need to consider our-selves more as real developers. We do not follow best practices As Business Central developers we need to learn to respect our profession, to follow the same basics, standards, rules or whatever you will call it. Most other professions do have some set of basic standards they must follow. You don't have to be a doctor, electrician, lawyer etc. for that to be the case. For developers, especially NAV developers, that is not the case. We have no set standards, except the implicit "follow-the-money"-rule with often a very shortsighted perspective. We are not required to follow best practices or do our job to our best abilities. But back in the early days our methods and practices where best practice, should I say best possible practices. Today we know that it is possible to write source code in a much higher quality, without using more time. Doing that would be "to our best abilities". We accept buggy software It is generally accepted that we deliver software containing bugs. Sure, as developers, we test it to our best abilities, but it's not really going to be acceptance tested until the "test phase", eventually by the consultant or when installed with the customer. Our input, our requirement may only have been a few lines and a screen shot, often with plenty of opportunities for our own interpretation, sometimes good, others not. Acceptance tests may not even have been described and signed off by the user/owner. If we find a bug, and we will, then we write it in our Error Log, we have systems where customers can register their errors online. If we were better at our job, then there would not be errors Developers are expected to make software with bugs, and other people are expected to find and report them. It is not something we like, but everybody (?) knows that software has errors, so it is accepted. We should not accept to have to deliver sub-standard, sub-quality software, when we know that there is a better way. If we are told, not to do our best , then how can we respect our own profession. And if we, the developers, do not respect our own profession, how would anyone else, including new candidates? Except of course, making it un-ethical to create bugs and unclean code, then I am not the one to dictate these standards. Uncle Bob has come up with his suggestion to a Programmers Oath (see link below), which could be a great place to start. It should NOT be something that Microsoft is dictating to their partners and developers. What should Microsoft do? Microsoft have their #ReadyToGo program for partners, providing videos and training and more. They continue to improve our tools and make the industry standards available for us. I would hope that they put more focus upon promoting methodologies and best practices for Business Central. Their NAV (C/Side) design pattern site did not get updated for a very long time and no new site for BC. Why not do this in a closer relationship with the community, the MVP's? Blogs are great, but they often get lost in the web. And don't limit it to design patterns. And forget the certifications. If anything, then certifications is a hinderance from the required growth in our industry. It will move the focus on passing a test, instead of really becoming better and more professional. They need to make developers feel that they can do everything with BC and AL, that they can do with any other platform. But better and easier. Business Central and the development platform must become even sexier, to attract the best professionals. What should partners do? Nothing really happens without them. It is them who must see that Business Central is not NAV, and that extensions and Visual Studio Code is a much bigger change, than just a new language and development environment. Its an opportunity to grow. Developing everything as generic as possible, with test codeunits and CI/CD, is not an extra cost, but a way your software can be sold to many customers, instead of just one. Even if you are not building it (initially) for AppSource, then if you already have tests etc., then getting there will be much easier. And once Test-Driven Development, test codeunits, clean code and design patterns have been worked into your developers, then not only will the code be much better with less errors and much easier to maintain, but it will end up costing you less. If they are hiring new developers directly out of college, then they should not introduce these to C/Side, much better that they focus on one environment. The partners need to figure out how many of their dinosaurs they need in BC. Even if learning AL is not a real challenge to most current NAV developers, and that we for sure are going to need dinosaurs in AL too, they are better of keeping them in C/Side. The dinosaur developers need training in the modern way of developing, even if they have written code for 15 years or more. And they may need time to become just has effective with the new methods. Or keep your dinosaurs on NAV, only bringing over a few as architects and mentors, and hire new developers familiar with the new methodologies and practices. And don't forget that successful test-driven development, requires the developer, issue/feature-owner and analyst to define/describe the tests/requirements together, before any code is written. It requires the whole team to be familiar with the "new" processes. The changes effects everybody, not just developers. What should developers do? I hope that all of us will find more pride in what we are doing, that we become better and more professional NAV and BC developers. We all need to invest hours of learning, its no excuse that your employer does not provide it for you in your work hours. There is an old saying, which says "You get paid to work from 9-5. What you do after work get your promoted?". While this may not get your promoted, then it will allow you to keep your job, if you want to make in the BC world. Practices like TDD, is a whole new way of writing source code. It's almost like learning to write a bike again. At first you will feel that it slows you down, you may fell a few times, you may curse, before you finally get it. And when you do, you are not going to understand, how you ever been able to write software in any other way before. You are going to hate how code looked just short time again. If you don't really care about all this and you just want to continue to do things has you have done "always", then stay in NAV. As said before, then you will still have plenty do the next many years. If you still want to embrace the "new" development methods and practices, if you think it is important that we become more professional developers, then it's really easy. Start to study everything on clean code, design patterns and refactoring. Most here is rather generic, even if not all design patterns can be done with AL, so there are 100's of hours of video on YouTube. I can recommend anything by Robert C. Martin, Kent Beck, Martin Fowler. There are also many blogs about NAV design patterns and even TDD with C/Side. Recommended for more information : Youtube: The Programmer's Oath by Robert C. Martin (Uncle Bob) YouTube: The future for NAV developers and consultants (David Singleton and Erik Ernst) Blog: Luc van Vugt's dynamiXs , about automated tests, test driven development etc. Blog: Mark Brummel , clean code, design patterns etc. Site: Dynamics NAV design patterns

Stefano, Is there a link to the process of importing on-premise NAV to BC 365? Thank you.

Hi Dzung, i tried to both way to figure out high RAM consumption but no trace found at that point of time. is there any other way to decrease RAM consumption? Thank you.

Hello there. I have created a codeunit to handle eventSubscribers. I have these functions among others. What the below does, is take a custom field and pass value from the Purchase header to the vendor ledger entry. So 2 events (one Purchheader to GenJnl and the other event from GenJnl to Vendor ledg). This works great in my SBX environment running locally on Docker, however does not work on the client environment. The client is running BC365 on Premise. This codeunit has other EventSubscibers but they use table Events and they work great. Any idea why the code below does not work on the client's environment ?

Hi At the Rapidstart service, I am trying to create a Export package. I have no issue up to assign package code. At the Configuration Packages, when I tried to do a export packages, it processes half way and pop up an error message as shown below. Does anyone knows how to resolve this? Any help is much appreciated.