Developing extensions blindfolded in Dynamics NAV

Developing extensions blindfolded in Dynamics NAV

Developing extensions in Dynamics NAV, it is possible to add two extensions that are adding the same field numbers to a solution.

Let’s try an example:

Now I publish and install the extension together with a page extension:

In the Extension Management, it looks like this:

Nothing new about that.

Now, let’s try to install another extension with the same field number used:

Now I publish and install the extension together with another page extension:

It is possible to publish the extension and even install it in the tenant but starting the Windows client, I get the following error:

It is not possible to start the windows client again until I have uninstalled the extension through PowerShell:

In all the workshops I have conducted until now, I have been given the question:

“How do I see which object numbers and field numbers that are already used in the solution?”

I haven’t found any standard solution to this, so I made one myself:

Install two objects:

  • Table 50149 Extension Detail Information
  • Page 50149 Extension Detail Information

(And No, it is not possible to create as extension due to the tables I access.)

Run the page and it will generate detailed information on all apps that are published (installed or not):

Now you can filter for the desired table:

The object can be downloaded here:

http://ba-consult.dk/downloads/ExtensionDetails.zip

Have fun

6 thoughts on “Developing extensions blindfolded in Dynamics NAV

  1. Yo, wanted to chime in about 66win9. This site is decent. They have a good variety of games, and navigation isn’t too bad either. Bonus structure isn’t the best, but it is functional. Worth a check on your own accord 66win9.

  2. Alright lads, heard about m8888e and decided to give it a go. Pretty similar to other sites, but what I like is the bonus they offered when I joined. Check it out if you’re looking for some decent promos!

Leave a Reply

Your email address will not be published. Required fields are marked *