search

microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
747 stars 245 forks source link

Permission Sets #711

Closed hvogelpohl closed 7 years ago

hvogelpohl commented 7 years ago

Last time (Extensions 1.0) I had to compile a permissions.xml in my NAVX file with the permission set of my app. Is this still needed, if so, how?

MikeGlue commented 7 years ago

You can simply use the same XML file you generated for your V1 extension, or use the same process to make a new one for your V2 extension, and then put the XML file into your extension project. Seems like you can put it anywhere you want and the compiler will figure out what to do with it.

For example, I put mine in a specific folder, and no other settings were needed to be changed and the compiler picked it up and included it in the compiled extension app.

image
hvogelpohl commented 7 years ago

Ahhh... "The file matches the definition for 'PermissionSet'.". Thank you very much!

hvogelpohl commented 7 years ago

I'm just wondering what object type page extensions and table extensions are? ( <Permission><ObjectType>??</ObjectType></Permission>). I searched here, I didn't find anything..

MikeGlue commented 7 years ago

Just give permissions to the original table/page objects you are extending, not the actual extension objects.