Import Permission Set with Powershell?

The permission set automatically becomes part of the .navx file of the extension if you export it to the same folder before you run New-NAVAppPackage there, so the import is already integrated if it's available.
https://msdn.microsoft.com/de-de/library/mt600264(v=nav.90).aspx
https://community.dynamics.com/nav/b/navvideos/archive/2016/07/05/how-do-i-include-a-permission-set-in-a-microsoft-dynamics-nav-extension

kalyankandimalla wrote: »

Hi,
Please try to use XMLPort 9171:Import/Export Permission Sets

XMLPorts 9171, 9172 produce csv files and usually need to be used together.

The powershell commandlet produces an xml file and can only export one permission set per call, even though the file structure would allow for any number of permission sets. The commandlet appears to be intended solely for the purpose of creating an extension. Therefore no corresponding import-NavAppPermissionSet exists.

mgn wrote: »

@Kowa: I prefer not to use a navx file…

In that case Export-NAVAppPermissionSet is the wrong choice, as it is part of the cmdlet group specially designed for extensions which all have this 'App' in their name
https://msdn.microsoft.com/en-us/library/mt584152(v=nav.90).aspx

Hi, But also using Xmlports (like 9171 )will generate xml file. We need to select required format while saving.But as you mentioned maybe customizing xmlport will help.