Adding new role centers to an Extension?

Business Central/NAV Developers Forum
1

I’m sure I have seen it somewhere, but now I simply cannot find any information about it.

But what is the process of adding a new profile/role center when creating an extension? Not talking about the actual role center page, no problem to include the new object. But don’t seem to have any functions for exporting the profile configuration data here? Is it a post installation process to add it?

It’s for NAV 2018/BC.

2

Hi Erik,

I suppose you have read the following page:

https://docs.microsoft.com/en-us/dynamics-nav/how-to–develop-an-extension

In particular the section “To use a staging table to load data into an existing table”

Perhaps will help you.

3

Thanks [mention:ba4af57369b949f2973760bde9ffb9a0:e9ed411860ed4f2ba0265705b8793d05], yes knew that one too and I was going in that direction already, but was really hoping for something more like the permissions - in an XML format, that we could track in Git. [emoticon:c4563cd7d5574777a71c318021cbbcc8]

And I guess if we can copy a profile, then I can also copy it to a staging table, that I can export to be imported to the extension and inserted later, when the user installs it.

4

[mention:74275055534c437ab13054c27a1ed5fb:e9ed411860ed4f2ba0265705b8793d05] or [mention:4a07ce597c904f50a75d74552219b7a6:e9ed411860ed4f2ba0265705b8793d05], does one of you have the answer to this?

5

Was just checking up on my old threads and saw that this one was still open (i.e. not verified).

Since then I have found the answers. Sort of.

What I really where talking about were the profile customization’s. The ones made using the Windows client and profile configuration mode. Was really not clear in my question above.

But the answer to this is to use page customization objects and then using:

Customizations = MyPageCustomization;

to specify which customization’s belongs to which Profile object.

Technically it may be possible to use the Windows client to create customization meta directly in the “old way”. But as everybody knows, then this may be easy, but debugging/testing it becomes quite difficult. Plus with C/Side and the Windows client on it’s way out, then its only a question about time when that option is out of question.

As to loading data into a standard table with an extension, then that can happen in two ways: Load the data into an extension specific table with the DataPerCompany = false on Extension installation. Data can be exported with the PowerShell CmdLet and just has to be compiled with the extension. Then upon setup of the extension, this data can be copied into the standard tables/fields. The other way is to load the data (again upon setup) via a web services or other external source.