Welcome to Convergence Day Three. Yesterday’s keynote and general session were phenomenal, with great attendance, enthusiasm and some exciting customer stories and news about Microsoft Dynamics NAV. Let’srecap:
The General Session was loaded with information and inspiration. We saw some great demos, videos, examples of new functionality and learned how customers are using Microsoft Dynamics NAV 2013. We also learned more details about the expected June 2013 availability of Microsoft Dynamics NAV 2013 hosted on Windows Azure through partners. And, we were given a peek under the hood of what to expect in the upcoming Sicily release scheduled for later this calendar year. Finally, the General Session unveiled a really awesome Convergence offer to try Microsoft Dynamics NAV 2013 on Azure for a limited time – for free! Exciting! In short, the future looks great for Microsoft Dynamics NAV!
That was yesterday. Today, there are plenty of opportunities to focus on your business with Microsoft Dynamics NAV. Consider attending these or any of the many sessions available today:
You can also take part in an Interactive Discussion, a Deep Dive Session, or one of the many exciting Microsoft Dynamics NAV-focused sessions between now and 6 pm.
Or grab a seat, put up your feet and try one of the virtual Hands-on Labs. Launch a lab anytime – during the day or night, on your own machine or on the onsite Communications Kiosks. To launch a lab, visit the Convergence website, login to My Convergence, and utilize Schedule Builder to locate the labs of your choice.
Enjoy!
The Microsoft Dynamics NAV Team
Great to see so many of you at the reception last night!
Convergence 2013 kicks into high-gear today. First stop: look for some exciting Microsoft Dynamics NAV-related announcements and a very cool Microsoft Dynamics NAV customer story in the keynote at 9:00 am.
Afterwards, you’ll want to grab a good seat for the General Session at 11:00 am. This must-see session, Microsoft Dynamics NAV - Opportunities for Your Business, is a great opportunity to come and see the product in action, hear feedback from other customers, and be inspired to improve productivity and build your business.
After lunch, there’s plenty of time to network face-to-face in the Expo and Microsoft Solutions Experience Center. Here you can get answers to your burning Microsoft Dynamics NAV questions – free of charge :-) - from Microsoft support engineers. You can see live product demos and feed your inner geek in the Expo.
There are also three great Microsoft Dynamics NAV concurrent sessions beginning at 3:30 pm that you don’t want to miss while you’re here:
Finally, make Convergence your event – and share your experiences with your network - using Convergence Mobile App, and check out one great social media mash-up at the #CONV13 live wall.
Tell us what you’re up to on Twitter: @MSFTDynamicsERP #MSDNNAV #CONV13.
Have a great day!
Welcome to Convergence 2013! The Microsoft Dynamics NAV team is ready and waiting to welcome you with incredible content and a world of opportunities to discover the full potential of your Microsoft Dynamics NAV solution.
Yes, Convergence 2013 starts today, and there is plenty going on right now to help you get warmed up for the full Convergence experience tomorrow, including User Group Sessions, Roundtable Discussions, and the Expo Experience. You can also volunteer your time and make a difference in the local community by taking part in the many onsite and offsite community outreach activities.
Otherwise, registration opens today at the conference center from 11:00 am. Then it’s off to the EXPO and Microsoft Solution Experience area. With hundreds of featured exhibitors from the global Microsoft Dynamics community, it’s the perfect place to begin. Get your bearings with this overview.
You can catch some great Microsoft Dynamics NAV content at the Microsoft Dynamics NAV User Group sessions from 12:00 noon and 1:30 pm or participate in one of the two Roundtable discussions starting at 3:00 pm. And, don’t forget the Convergence reception this evening. This year the reception will be held in the hub of it all – the Convergence Experience Center. The fun, food and festivities begin at 6:00 pm.
Make it an early night. Kirill Tatarinov will be up bright and early to deliver the opening keynote tomorrow at 9:00 am sharp. Kirill will kick things off with the vision for A World Ahead, plus a look at what you can expect to experience at Convergence 2013. The Microsoft Dynamics NAV General Session and breakouts follow from 11:00 am.
What else? The next few days are packed with valuable Microsoft Dynamics NAV 2013 sessions, interactive discussions, tips and tricks, and user group activities. This year, the hands-on labs will be online – so you can access them at any time during your stay. And, as always, in the true spirit of Convergence, there will be many opportunities to meet other members of the Microsoft Dynamics NAV community and share experience and insights.
Feeling a bit overwhelmed about where to start? Check out this session overview. Or find out what's new for Convergence 2013.
As J.R.R. Tolkien wrote, "Home is behind, the world ahead, and there are many paths to tread...".
In other words: Convergence 2013 is here and and there’s a world of opportunity ahead for you and your business with Microsoft Dynamics NAV. Use this unique opportunity to set the course for your business.
So, put your best foot forward, and step out into Convergence 2013. See you there!
For your viewing and learning pleasure, we have released a set of new videos on Microsoft Dynamics NAV 2013 to MSDN. Check out the latest offerings:
To see all offerings, choose the following link, http://msdn.microsoft.com/en-us/bb629407.aspx, and scroll to the Microsoft Dynamics NAV 2013 section.
To keep up with the video releases, subscribe to the video feed: http://www.microsoft.com/feeds/msdn/en-us/videos/dynamics_NAV.xml.
If you install the CRM Connector for Microsoft Dynamics NAV 2013 you will find that you cannot read the “Record ID” value directly in the Integration Record table as you used to in Microsoft Dynamics NAV 2009 R2. If you try to look at the contents of this table you will see the following:
This can make troubleshooting a CRM Connector problem difficult as the Record ID is often required to associate a change transaction with a specific row in the relevant NAV table. The solution is to create a Dynamics NAV Page to enable you to format the Record ID into human readable format. The steps below will give the desired result:
1. Create a new Page in the Microsoft Dynamics NAV Development Environment.
2. Specify the page should be built on table id 5151 (Integration Record).
3. Select “Create a Page using a wizard” using the List option:
4. Add all table fields to the new Page and click the “Finish” button:
5. In the Page Designer, amend the SourceExpr, Name and Caption as shown below to ensure that the Record ID value is formatted correctly:
6. Save the Page and run it to see the Integration Record data as required:
7. Note that you can now filter on the Record ID which is a common requirement when troubleshooting CRM Connector issues:
Gerard Conroy
Microsoft Escalation Engineer.
This week I did work on a support case where the partner mentioned that adding an attachment from a stream does not always work. The partner delivered a code unit that we used to further analyze the issue. As it was not necessary to further develop a fix for this, we decided to just post the outcome of that support request on a Public blog. You can read the original posting on the following blog: http://nav-magno.be/index.php/2013/02/add-attachment-stream-on-smtp-not-always-working/
On that blog you can also download the code unit we used for debugging purposes.
Credit should go to Joachim Carrein, working for iFacto who reported the issue to us.
Regards,
Marco Mels CSS EMEA
This posting is provided "AS IS" with no warranties, and confers no rights
=== Blog updated on March 4th ====
Updated with the good news that we now have a hotfix for this for Windows Server 2008 R2:
Visual elements are displayed incorrectly etc... - KB 2768741.
===== end of update ===========
In NAV 2013, if you run the Windows Client via a Terminal Server or Remote Desktop Connection (RDC) or some common 3rd party application host technology, reports may be difficult to read when you print them. Preview looks fine.
A report could look like this in preview (OK):
But in Print Layout rendering or when printing to paper it would look like this - notice it looks like the fonts have been scrunched and it's hard to read:
It happens when
A) you run NAV 2013 via a Terminal Server or via Remote Desktop Connection (RDC), and
B) the screen resolution on the connection is not 4/3, and
C) the Terminal Server machine is running Windows 2008 including Windows 2008 R2.
The screen resolution is the important thing here. If we use a screen resolution of 4/3 (=1.33333) then all works fine. So if my RDC looks like this then I don't have this issue:
On this connection the screen resolution in my connection is 1024 by 768. 1024 / 768 = 1.33333, and everything is OK.
But if I set the screen resolution on my RDC like this:
Then my screen resolution = 1366 / 768 = 1.779.
1.779 <> 1.33333 and then I have the problem.
The root of the problem lies in graphics rendering (GDI) in Windows 2008 when it tries to scale from a screen resolution which is not 1.33333. In Windows 2012, rendering was redesigned to take advantage of hardware acceleration and ActiveX as described in this article:
Windows 8 graphics: Microsoft has hardware accelerated all the things
So we do not have this problem if the host machine is running Windows 2012.
NAV 2013 uses a newer version of Report Viewer which relies more on Windows GDI than previously, which is why we have only started seeing this problem on NAV 2013 installations.
Based on the above there are three ways out of this problem:
1) Ensure that all users use a screen resolution of 4/3
2) Avoid a host machine trying to scale a client's resolution. For example:
- Save the report to PDF, then print from the PDF document. PDF rendering is not affected by this issue.
- Use server-side printing - for example make use of the Job queue and let NAS print reports. Then the server can ignore what resolution the client has.
- Use other ways than Terminal Server to simplify client installations, such as ClickOnce or possibly "Remote Apps". In this way the client runs on the local machine and not on a host machine.
3) Upgrade the Terminal Server / RDC host machine to Windows 2012. Client machines do not need to be upgraded.
Workarounds 1) and 2) could be hard to enforce in some cases. But knowing about this issue, hopefully the option of using Windows 2012 can be considered.
We will post updates here if and when we find any further details around this issue!
It has been a while since I last wrote a posting about the SMTP Server component that we first shipped with Dynamics NAV 5.0. Let’s recap the older posting first as it does list a complete list of patches that one should have applied already and let me take the opportunity to also discuss some previous support cases that were filed at our support service regarding specific Italian localization that only applies to Italian partners / customers. Last but not least some support cases were filed at our support service in regards to Office 365. Let’s also discuss these.
The previous posting can be found here: Double impersonation within a three tier environment and the SMTP Server setup in Microsoft Dynamics NAV. A later patch did came out as well: 2811780 where we added some code to code unit 400 to allow a timer to be configured via C/AL. Previous support cases were filed by Italian partners requesting if they could use our SMTP Server component with Posta Elettronica Certificata which is an alternate connection configuration via SMTP/SSL over port 465. More information about PEC can be found here: IETF and Wikipedia
The SmtpClient.EnableSsl property is responsible for this and is discussed on MSDN. Here you can read the following:
An alternate connection method is where an SSL session is established up front before any protocol commands are sent. This connection method is sometimes called SMTP/SSL, SMTP over SSL, or SMTPS and by default uses port 465. This alternate connection method using SSL is not currently supported.
Last but not least Microsoft Support received several requests from partners how they should configure Dynamics NAV SMTP Server component in combination with Office 365. The good news is that this is possible, but there are some challenges, especially when you use the SMTP Server component in combination with Document Approval system that we shipped with Dynamics NAV. Let’s assume the latter. The prerequisites are:
Let’s show you how this does work. When you start the PowerShell, a box is shown to you with the following line: “PS C:\Windows\system32>”. After that line, you can type the commands one at a time.
First command:
PS C:\Windows\system32> Set-Executionpolicy -ExecutionPolicy Unrestricted
Execution Policy Change The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose you to the security risks described in the about_Execution_Policies help topic at http://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
Second command:
PS C:\Windows\system32> $LiveCred = Get-Credential
cmdlet Get-Credential at command pipeline position 1 Supply values for the following parameters: Credential
Third command: PS C:\Windows\system32> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
WARNING: Your connection has been redirected to the following URI: "https://pod51014psh.outlook.com/powershell-liveid?PSVersion=3.0 " WARNING: Your connection has been redirected to the following URI: "https://db3prd0411psh.outlook.com/powershell-liveid?PSVersion=3.0 "
Fourth command:
PS C:\Windows\system32> Import-PSSession $Session
ModuleType Name ExportedCommands
---------- ---- ----------------
Script tmp_2b2tb1qp.44s {Add-AvailabilityAddressSpace, Add-DistributionGroupMember, Add-Mailb...
Fifth command:
PS C:\Windows\system32> Add-RecipientPermission "Kevin Mels" -AccessRights SendAs -Trustee "Marco Mels"
Confirm Are you sure you want to perform this action? Adding recipient permission 'SendAs' for user or group 'Marco Mels' on recipient 'Kevin Mels'. [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): Y
Identity Trustee AccessControlType AccessRights Inherited -------- ------- ----------------- ------------ --------- kevinmels marcomels Allow {SendAs} False
Sixth command: PS C:\Windows\system32> Add-RecipientPermission "Sean Bentley" -AccessRights SendAs -Trustee "Marco Mels" Confirm Are you sure you want to perform this action? Adding recipient permission 'SendAs' for user or group 'Marco Mels' on recipient 'Sean Bentley'. [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): Y
Identity Trustee AccessControlType AccessRights Inherited -------- ------- ----------------- ------------ --------- seanbentley marcomels Allow {SendAs} False
PS C:\Windows\system32>
Document Approval setup looks like this:
PS C:\Windows\system32> Remove-PSSession $Session
To summarize, Marco Mels (marcomels@bergmanz.onmicrosoft.com) configured in the SMTP settings is the trustee and you need to add SendAs recipient for all users that are in the Approval User Setup form.
Some other commands to verify the setup if needed:
PS C:\Windows\system32> Get-RecipientPermission "Sean Bentley" -AccessRights SendAs
Identity Trustee AccessControlType AccessRights Inherited -------- ------- ----------------- ------------ --------- seanbentley NT AUTHORITY\SELF Allow {SendAs} False seanbentley marcomels Allow {SendAs} False
The Windows Powershell must be started via “Run as Administrator”and you need to specify user credentials within Office365 that does have Administrator permissions. Truly hope this does help you to configure SMTP Server component in Dynamics NAV in combination with Office 365.
I recently talked to Microsoft partner ChargeLogic about their own in-house implementation using Microsoft Dynamics RapidStart Services for Microsoft Dynamics NAV. I found the story inspiring and wanted to share it with you here.
ChargeLogic recently spun off from their parent company and needed their own ERP system. As solution experts, the decision to use Microsoft Dynamics NAV was obvious because they knew the product inside and out. Yet, according to Jon Cooper, President at ChargeLogic, they still faced one big challenge: lack of time.
“With our already busy schedules, combined with all the work involved in starting a new company, finding time to actually sit down and work on our own internal systems was a challenge,” Cooper says. “We wanted implementation to be quick and painless.”
This is where RapidStart Services for Microsoft Dynamics NAV came into the picture. It is an integrated tool and a native part of Microsoft Dynamics NAV that helps speed up the implementation process and facilitates better control of the whole process.
It includes Project Overview, Questionnaires, Master Data Import and Configuration Packages. Using the basic configuration package for the implementation of Microsoft Dynamics NAV 2013 made implementation straightforward for Cooper and ChargeLogic right from the start.
“When I installed NAV 2013 on our new server and logged in, it brought up the RapidStart Role Center, which was enormously helpful. Not having used RapidStart before, I started filling out the G/L Questionnaires. I quickly finished and moved through the Sales, Purchasing, and Inventory Questionnaires. I was able to leave most of the settings at their default values and only changed a few values along the way.”
Another aspect of RapidStart Services for Microsoft Dynamics NAV that made things easier was the data import aspect.
“Once I had finished answering all the questions, I moved on to the Configuration Worksheets. All of our data from the old company was in a NAV 3.60 database, so I simply filtered on the data that was applicable to our new company and copied and pasted it from NAV 3.60 into Excel. I created worksheets for my Item and my Customer masters. I also pulled Customer and Item ledger entries into a worksheet.”
Cooper exported the Customer and Item masters and journals as templates, made some slight adjustments to the fields in NAV 2013, and created an updated template. He then simply copied and pasted the data from their old system into the templates and imported it into Microsoft Dynamics NAV 2013. RapidStart identified some validation errors, which were quickly corrected and reprocessed.
“My Customers, Items, and their respective histories were in my new NAV 2013 system, and I didn’t have to data-enter a thing,” Cooper says.
Cooper admits that he had anticipated that the implementation would take ten to fifteen days and he would need to make use of three people in that time.
“With RapidStart, I performed the entire implementation myself in less than two days. I’m a developer, and I know NAV very well, but this was my first implementation. I was very impressed with how easily RapidStart Services got me going and walked me through the implementation process,” Cooper says.
ChargeLogic is an Independent Software Vendor providing the PCI-Compliant solutions integrated with Microsoft Dynamics NAV. ChargeLogic’s suite of products include ChargeLogic Payments, the PCI-compliant payment processing solution for NAV, ChargeLogic Connect, the cloud-based service for easy e-commerce integration with NAV and secure payment management, and ChargeLogic Shipping, the most intelligent, integrated shipping solution with NAV. ChargeLogic is Certified for Microsoft Dynamics (CfMD) and is a Validated Payment Application as certified by the PCI Security Standards Council. ChargeLogic sells, distributes, and supports their software through a partner channel comprised of Microsoft Enterprise Resource Planning partners with a high degree of technology competence and expertise. As a Microsoft partner, ChargeLogic uses this knowledge to build the highest quality solutions for Microsoft Dynamics NAV.
Jannik Bausager
Director – Microsoft Dynamics NAV product marketing
RapidStart Services for Microsoft Dynamics NAV is an integrated tool and a native part of Microsoft Dynamics NAV that helps speed up the implementation process and facilitates better control of the whole process. It includes Configuration Packages, Project Overview, Questionnaires, and Master Data Import.
TRIMIT gains complete control of the implementation process
RapidStart Services for Microsoft Dynamics NAV helps TRIMIT Fashion provide a complete setup of a new company. TRIMIT use it to configure the application. It gives them an overview of which areas are being processed and which are already completed, who is responsible for setting up an application area and what else will be affected by the specifics of the setup.
Better overview promotes better communication
Kitty Bisseling, Partner Supporter at TRIMIT, finds that “using the Project Overview, the customer is able to get a better overview of the setup work that still needs to be done.”
According to Alexander Pontoppidan Thyssen, Business Consultant at CORNATOR, RapidStart Services streamlines communication: “RapidStart Services has helped improve communication both internally as well as externally because people tend to be more aligned with the “why” and the “how” when they address the issues and challenges that they come across when implementing,” Thyssen says.
Standardization saves time
RapidStart Services comes with a standardized Configuration Package with out-of-the-box general setup data, such as currency codes, posting groups, VAT templates, chart of accounts, payment terms, and countries.
For their TRIMIT Fashion solution, TRIMIT has also extended it with Configuration Packages specifically for Fashion Wholesale companies. This extends the pre-set data with fashion-specific data templates of Matrices for Color and Sizes. The standardized Configuration Packages shortens the implementation time for TRIMIT’s customers by providing them with predefined fashion-specific colors, sizes, washing label descriptions and more.
“Especially for smaller companies, the whole setup of a new Company can be adopted, so the customers can start up very quickly; this really saves time for the customer and for the consultant,” says Bisseling.
The standardized Configuration Packages have improved efficiency for CORNATOR’s customers: “Knowledge and thereby efficiency is in general improved across departments and between consultants, because we use the same data foundation across implementations”, says Thyssen.
Shorter learning curve
RapidStart Services also includes Questionnaires, which TRIMIT has used to ask specific questions about the fashion company being setup. By offering out-of-the-box questionnaires, RapidStart Services makes it possible for everyone to start up their own company with only minimal training required.
“It is also a great tool for guiding the customers to what they need to do; even when the consultant is not present,” Bisseling says.
Greater flexibility for the future
RapidStart Services for Microsoft Dynamics NAV is a native part of the product, which means that it is available both on-premise and in the cloud, giving customers more flexibility. Bisseling believes that in the future, when more companies start to adopt the SaaS concept as a way of working with more standard and less customized functionality, RapidStart Services will help guide their customers through the implementation process.
TRIMIT is an ISV (Independent Software Vendor) and a Gold Certified Microsoft Dynamics NAV Partner specialized in fashion, furniture, product configuration, and trade and distribution. TRIMIT, an industry solution designed and built within Microsoft Dynamics NAV, enhances the ERP solution with a wealth of industry-specific functionality to manage design, cuts, colors, sizes, and more. The ERP system also integrates with Microsoft Excel for reporting and business planning and with Microsoft Word for importing customer information automatically into forms, letters, and marketing communications. The TRIMIT Solution helps fashion and furniture Companies handle a greater number of product variants by simplifying product configuration. Together, Microsoft Dynamics NAV and the industry solution, TRIMIT help companies run their business by providing them with configured Master Data Templates, including Matrices for Color and Sizes.
In 2008, the company CORNATOR divided into two independent companies, CORNATOR and TRIMIT. CORNATOR continued to support the Danish market as a VAR (Value Added Reseller), and TRIMIT continued to develop "state of the art" functionality for TRIMIT solutions and to build an international partnership strategy that focuses on the fashion and furniture industries. All 70 employees of CORNATOR work with Microsoft Dynamics NAV.
We are proud to announce that Microsoft Dynamics NAV 2013 is compatible with Microsoft Windows 8 and Microsoft Windows Server 2012.
We support the following versions of Microsoft Dynamics NAV with Microsoft Windows Server 2012 and Microsoft Windows 8:
For more information about requirements, see System Requirements for Microsoft Dynamics NAV 2013.
Based on partner feedback and the increasingly important goal of automating processes around a Microsoft Dynamics NAV installation, we’re pleased announce that we have added company-related and database-related command-line options to finsql.exe, in addition to the existing options. Introduced in hotfix 2791548, you can use the following commands to perform development tasks without using the Microsoft Dynamics NAV Development Environment.
Note
To use the new and changed command-line options, you must install hotfix 2791548 (requires access to PartnerSource/CustomerSource).
You can start the Microsoft Dynamics NAV Development Environment by running finsql.exe at the command prompt. By default, finsql.exe is located at C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\. The extended full syntax is:
Finsql.exe [command=<command> | designobject=<object type> <object ID>,] [servername=<server>,] [database=<database>,] [collationname=<collation>,] [company=<company>,] [newcompany = <new company>,] [filter=<filter>], [logfile=<logfile>,] [username=<user name>,] [password=<password>,] [ntauthentication=<yes|no|0|1>]
The full documentation is available on the MSDN Library. Additional documentation is available at Development Environment Commands.
The following list describes the parameters that you can use with finsql.exe.
collation
The collation to use when you create a new database. The value must be one of the following:
Use this optional parameter when you create a database with the command=createdatabase parameter.
command
The development command that you want to run. The possible values include:
If you specify this parameter and run a command, then the development environment does not open.
For more information, see Development Environment Commands.
company
The name of the company that you want to create, delete, or rename.
A company name cannot be more than 30 characters.
If you create, delete, or rename a company with the command parameter, then the company parameter is required.
database
If you use the command=CreateDatabase parameter, then the database parameter specifies the name of the new database that you want to create. In this case, the database parameter is required.
For all other commands, the database parameter specifies the database that you want to open.
If you do not specify both the servername and the database parameter, then the database server and database that are stored in the .zup file are used. If you do not specify the database parameter but you do specify the servername parameter, then the Open Databasewindow opens so that you can specify the database name.
For more information, see Saving Setup Parameters in the Zup File.
designobject
The type and ID of the object that you want to design. The possible values of the object type include:
The possible values of the object ID are 0 and any ID of an existing object. If you specify 0 for the object ID, then you open a new object to design.
For more information, see DesignObject.
file
The path and file name. Use the file parameter for the following:
For more information, see ExportObjects and ImportObjects.
filter
A filter on the Object table.
Use this parameter if you use the command parameter to compile, export, or import objects.
id
Specifies the ID of the .zup file. By default, the setup parameters are stored in and retrieved from the fin.zup file. If you specify the id parameter, then the setup parameters are stored in and retrieved from a file that is named <id>.zup.
By default, the fin.zup file is located at C:\users\<user name>\AppData\Roaming\. To change the location of the .zup file, specify the path and ID in the id parameter.
logfile
Specifies the path and file name for the file that contains error messages that result from running finsql.exe with the command parameter. If there are no errors, then a log file is not created.
newcompany
The new name of the company that you rename.
If you rename a company with the command parameter, then the newcompany parameter is required.
ntauthentication
Specifies if you want to use NT authentication. The possible values are yes, no, 1, or 0. If you specify the username and password parameters, then you must specify ntauthentication=no or ntauthentication=0.
objectcache
Specifies the size of the object cache, in kilobytes. Objects such as code, descriptions, and windows that are used on the computer that is running the development environment are stored in the object cache.
The default value is 32000.
password
Specifies the password to use with the username parameter to authenticate to the database. If you do not specify a user name and password, then the command uses the Windows user name and password of the current user to authenticate to the database.
servername
Specifies the name of the database server.
If you do not specify both the servername parameter and the database parameter, then the database server and database that are stored in the .zup file are used. If you do not specify the servername parameter but you do specify the database parameter, then the Open Database window opens so that you can specify the database server name.
temppath
Specifies the path of the location to store temporary files that are created while Microsoft Dynamics NAV runs. These files are automatically deleted when Microsoft Dynamics NAV is closed.
By default, these files are put in the Temp folder for the user, such as C:\Users\user name\AppData\Local\Temp\
username
The user name to use to authenticate to the database. The user name must exist in the database. If you do not specify a user name and password, then the command uses the Windows user name and password of the current user to authenticate to the database.
Warning
If User Access Control (UAC) is turned on and you do not specify to run the Command Prompt window as Administrator, then the Command Prompt window runs as a standard user. In this case, if you do not specify the username parameter and the current Windows user is an Administrator, then the command is run as the standard user.
If you specify the username parameter, then you must also specify the password parameter and the ntauthentication parameter must be no or 0.
For more information about database users and permissions, see Setting Database Owner and Security Administration Permissions in the MSDN Library.
Best regards from the NAV Management Tools team
Windows PowerShell is becoming ever more used in the professional IT organization, and in Microsoft Dynamics NAV we are continuously extending and improving the set of administration management PowerShell cmdlets.
With hotfix 2791548, we introduce these additions and updates, all fully backward compatible with cmdlets shipped with Microsoft Dynamics NAV 2013:
To use the new and changed cmdlets, you must obtain the relevant hotfix through your Microsoft Dynamics NAV support contact. For more information, see the KnowledgeBase article for the hotfix (requires access to PartnerSource/CustomerSource).
The rest of this blog post describes the cmdlets at a summary level. The full documentation is available on the MSDN Library. Additional documentation is available at Microsoft Dynamics NAV Windows PowerShell Cmdlets.
Creates a new Microsoft Dynamics NAV Server instance.
Parameter Set: __AllParameterSets
New-NAVServerInstance [-ServerInstance] <String> -ManagementServicesPort <ServicePort> [-ClientServicesCertificateThumbprint <String> ] [-ClientServicesCredentialType <String> ] [-ClientServicesPort <ServicePort> ] [-DatabaseInstance <String> ] [-DatabaseName <String> ] [-DatabaseServer <String> ] [-ODataServicesPort <ServicePort> ] [-ServiceAccount {<LocalService> | <NetworkService> | <LocalSystem> | <User>} ] [-ServiceAccountCredential <PSCredential> ] [-SOAPServicesPort <ServicePort> ] [ <CommonParameters>]
Use the New-NAVServerInstance cmdlet to create a new Microsoft Dynamics NAV Server instance. You must specify a name for the instance, in addition to values for the four port parameters. All other configuration values for the new instance are based on default values. Make sure that you verify the DatabaseServer and DatabaseName values after the instance is created, to ensure that the instance can accept client requests.All permissions that are required for the instance to start are configured automatically.
For more information, see New-NAVServerInstance on the MSDN Library.
This example creates a new Microsoft Dynamics NAV Server instance. It configures the necessary firewall exceptions and performs the necessary Access Control List registrations.
// Copyright © Microsoft Corporation. All Rights Reserved.
// This code released under the terms of the
// Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)
C:\PS>New-NAVServerInstance NewInstance -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 –verbose
VERBOSE: NavCommand.BeginProcessingVERBOSE: NavCommand.ProcessRecordVERBOSE: Creating Instance directory C:\Program Files (x86)\Microsoft Dynamics NAV\70\Service\Instances\NewInstanceVERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServerVERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServerVERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServerVERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServerVERBOSE: NavCommand.EndProcessing
This example prompts for ServiceAccount credentials and then creates a new Microsoft Dynamics NAV Server instance.
C:\PS>Get-Credential | New-NAVServerInstance NewInstance -ServiceAccount User -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 –verbose
Creates a new Microsoft Dynamics NAV Web Server instance and binds this instance to a Microsoft Dynamics NAV Server instance.
Parameter Set: Default
New-NAVWebServerInstance -Server <String> -ServerInstance <String> -WebServerInstance <String> [-ClientServicesCredentialType <String> ] [-ClientServicesPort <String> ] [-DnsIdentity <String> ] [ <CommonParameters>]
Use the New-NAVWebServerInstance cmdlet to create a new Microsoft Dynamics NAV Web Server instance and bind this instance to a Microsoft Dynamics NAV Server instance on the same computer or on a remotecomputer. If you call this cmdlet multiple times then multiple instances of the Microsoft Dynamics NAV Web Server are created. Each instance of the Microsoft Dynamics NAV Web Server is created as an IIS Web application under a generic Microsoft Dynamics NAV Web Server web site.
For more information, see New-NAVWebServerInstance on the MSDN Library.
Creates a new Microsoft Dynamics NAV database from a backup file.
New-NAVDatabase [-FilePath] <String> -DatabaseName <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]
Parameter Set: MultipleDestinations
New-NAVDatabase [-FilePath] <String> -DatabaseName <String> -DataFilesDestinationPath <String> -LogFilesDestinationPath <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]
Parameter Set: SingleDestination
New-NAVDatabase [-FilePath] <String> -DatabaseName <String> -DestinationPath <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]
Use the New-NAVDatabase cmdlet to restore a database from a backup file. You can specify the location of transaction log files and data files.
You can use this cmdlet to restore a database to a remote SQL Server instance or to a SQL Server instance that is running on the same computer on which you run the cmdlet.
For more information, see New-NAVDatabase on the MSDN Library.
This example restores a database and preserves the original file names and locations.
New-NAVDatabase C:\Backups\backup1.bak –DatabaseName NewDatabase –Verbose | fl
VERBOSE: NavCommand.BeginProcessingVERBOSE: NavCommand.ProcessRecordVERBOSE: Restoring database 'NewDatabase' from backup file: 'C:\Backups\backup1.bak'...VERBOSE: Restore of database 'NewDatabase' from file 'C:\Backups\backup1.bak' has been completed successfully.
DatabaseName : NewDatabaseDatabaseInstance : MSSQLSERVERDatabaseServer : server1.cronus.comVERBOSE: NavCommand.EndProcessing
This example restores a database, moves transaction log files and data files to the new location 'C:\newdestination', and preserves the original file names.
New-NAVDatabase C:\Backups\backup.bak -DestinationPath c:\newdestination -DatabaseName NewDatabase –Verbose
VERBOSE: NavCommand.BeginProcessingVERBOSE: NavCommand.ProcessRecordVERBOSE: Restoring database 'NewDatabase' from backup file: 'C:\Backups\backup.bak'...VERBOSE: Restore of database 'NewDatabase' from file 'C:\Backups\backup.bak' has been completed successfully.DatabaseName DatabaseInstance DatabaseServer------------ ---------------- --------------NewDatabase MSSQLSERVER server1.cronus.comVERBOSE: NavCommand.EndProcessing
Renames a company in a Microsoft Dynamics NAV database.
Rename-NAVCompany -CompanyName <String> -DatabaseName <String> -NewCompanyName <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-ErrorLogFileName <String> ] [ <CommonParameters>]
Use the Rename-NAVCompany cmdlet to rename a company in a Microsoft Dynamics NAV database.
For more information, see Rename-NAVCompany on the MSDN Library.
This example renames the company Cronus Ltd. in the Cronus database to MyCompany.
Rename-NAVCompany -DatabaseName Cronus -CompanyName "Cronus Ltd." -NewCompanyName MyCompany –Verbose
VERBOSE: NavCommand.BeginProcessingVERBOSE: NavCommand.ProcessRecordVERBOSE: Renaming company 'Cronus Ltd.' to 'MyCompany' ...VERBOSE: Renaming of company 'Cronus Ltd.' to 'MyCompany' has completed successfully.VERBOSE: NavCommand.EndProcessing
This example renames the company Cronus Ltd. in the Cronus database to MyCompany. Errors are logged to the file C:\NavDatabases\ErrorLog.txt.
Rename-NAVCompany -DatabaseName Cronus -CompanyName "Cronus Ltd." -NewCompanyName MyCompany -ErrorLogFileName C:\NavDatabases\ErrorLog.txt
- Morten Jensen and the rest of the Microsoft Dynamics NAV Management Tools team
In the past few months we talked to many hosting companies across several countries which deal with Microsoft Dynamics NAV hosting. They all are confirming that the new platform capabilities of Microsoft Dynamics NAV 2013 are making the product much easier to deploy andmaintain.
The tools that are essential for the companies dealing with volume deployment of Microsoft Dynamics NAV 2013 include:
We also gained insight into the typical hosted Microsoft Dynamics NAV incidents. One of the biggest cost factors for companies dealing with a variety of products, not only from Microsoft, but also from multiple third-party software providers, was support and troubleshooting – finding the root cause faster and being able to see which product is causing problems to relay the support incident to the right support professional.
Many of these companies chose to use the Microsoft System Center platform to manage their virtual, physical, and cloud IT environments. This is a single end-to-end service management solution to handle infrastructure, service delivery, automation, and applications that is easy to customize and extend.
The way to extend this management platform to recognize and maintain all kinds of software and hardware is to use Management Packs (MPs) developed for them. Management Packs are the building blocks which extend Operations Manager capabilities to operating systems, applications, and other technology components. An MP contains best practice knowledge to discover, monitor, troubleshoot, report on, and resolve problems for a specific technology component.
Microsoft provides MPs for more than 60 Microsoft products and Windows components. There are more than 500 Microsoft Partner Management Packs covering most technologies used by organizations today.
We are pleased to announce that a Microsoft Dynamics NAV 2013 Management Pack for System Center is now available for download for all IT professionals working with System Center 2007 R2 Operations Manager or System Center 2012 Operations Manager components of the Microsoft System Center.
This extension package provides Microsoft System Center Operations Manager users with the ability to detect and monitor computer systems running Microsoft Dynamics NAV 2013, including the following components:
Companies providing hosting services to Microsoft Dynamics NAV Partners now have a toolset for extending their offering with Microsoft Dynamics NAV-specific monitoring and basic troubleshooting.
Microsoft Dynamics NAV 2013 Management Pack for System Center enables Operations and IT Management teams to easily identify and resolve issues affecting the health of numerous distributed Microsoft Dynamics NAV 2013 installations. It lowers client support costs by surfacing critical statistics and alerts in context of running Microsoft Dynamics NAV 2013 components. It also reduces IT management complexity by automating routine administration and providing basic actions for working with Microsoft Dynamics NAV 2013 components.
If you would like to hear more about the Microsoft Dynamics NAV 2013 Management Pack for System Center then please visit our Microsoft Dynamics NAV 2013 Product Readiness Library here.
On a final note, we would like to thank all the companies who shared their experience and provided their feedback to our R&D team. This feedback is extremely valuable and greatly appreciated.
- The Microsoft Dynamics NAV Product Marketing team
Assembly Management was released as part of Microsoft Dynamics NAV 2013, and it includes a set of features designed for companies that supply products to their customers bycombining components in simple processes, such as assembly, light manufacturing, and kitting.
Before the Microsoft Dynamics NAV 2013 release, customers and partners in selected regions and countries, such as North America, France, and Australia, may have been familiar with a similar local functionality called Kitting. The uptake of Kitting in those geographies has been both the driver and inspiration behind the global Assembly Management feature. Its value proposition and the functional breadth have been closely investigated and appreciated by the NAV core development team, resulting in Kitting’s key business and user requirements laying the conceptual foundation for the new Assembly Management feature.
To ensure the quality of the new global Assembly Management feature as well as its solid integration into the existing supply chain suite, the core development team produced aphysical and conceptual design that differed significantly from the one in Kitting. The differences are many. While Kitting used the BOM journal to manage the assembly process, Assembly Management operates with the concept of assembly order, which offers more functional flexibility, better user interface and extensibility. Last, but not least, assembly order offers more superior integration points to the rest of inventory, such as availability calculations and order promising, item tracking, supply planning, warehousing, and costing. This is understandable because the BOM journal, like any other journal in the application, is different from an order in its flexibility and scope, with the BOM Journal’s main goal being to support users in quick data entry for a subset of specialized transactions, while bypassing any auxiliary inventory processes.
With the introduction of the assembly order, the BOM journal was deemed unnecessary. This also meant that a disassembly process, which the BOM journal partially supported, wouldhave to be redesigned in Assembly Management along the same principles as the common assembly process. More specifically, a disassembly order to manage a reverse conversion process, i.e. from one item to many, would need to be added and integrated to the same supply chain features that the assembly order integrates to (see above). The disassembly order was not included in Microsoft Dynamics NAV 2013.Customers, who assemble their items themselves (as opposed to purchasing them from outside or getting them back through returns), and who need to reverse the previously made assembly, can use the new Undo Assembly function.
The option of keeping the BOM journal in the application for the sake of disassembly was rejected for several reasons:
a) Though useful in some scenarios, the actual BOM journal support for a disassembly process was limited to automatic creation of negative and positive adjustments for finished items and components respectively.
b) Its handling of cost flows required serious improvement.
c) As pointed out earlier, a journal line offers no integration to other parts of the inventory processes.
The core development team will be evaluating the possibility of including a properly designed disassembly feature in the future NAV releases. Kitting customers that used the BOM journal for their disassembly tasks should approach their partners for a discussion of reintroducing a journal for disassembly scenarios. The core development team will make no design recommendations in this regard.
For more information, see Assemble Items in the MSDN Library.
Best regards,
The NAV Supply Chain team