Numbering of objects - what is the significance

jeremyspx

Hello all,
Can someone inform me please - what is the significance of the numbering of objects. I notice that Pages in the 90xx's, for example, generally are Role Centers, Activities and Factboxes. I'm pretty sure there are general rules for the numbering of all the Objects but would really apprevciate it if someone can tell me what the sequences are.
Many thanks!

Marije_Brummel

Most of the numbering contains some logic. Many go back to the early windows version or even the dos version although I don't know much about this.

For us near mortals that are not allowed to create objects below the 50000 ranges it does not matter much what you do. It just makes searching easier and when time goes by you'll notice that it is useful to know some numbers by heart.

One thing to consider is the TRANSFERFIELDS function where all fields are copied from one table to another that have the same numbers. In this case they also need to have the same function and type.

When making your own objects it might make sense to create some logic in your numbering but it is hard, since most of the time you need way more pages/forms than tables.

jeremyspx

Thank you for that information. Darn! I was hoping to find a fairly rigid numbering system, that would really help one to locate an object, based on a logical series.
I bought your e-book today, by the way.
Jeremy

Marije_Brummel

jeremyspx wrote:

I bought your e-book today, by the way.
Jeremy

Thanks.

manisharma31

You only cannot find the object by its ID, you will also need the name for that.

jeremyspx

Yes, true, you will also need the name - however...
When you look at a chart of accounts - I mean the chart of accounts in any company - you find that the numbering of the accounts is logical and you can quickly learn them, which makes doing mental arithmetic or writing programs etc become much easier.

Knowing each number series range means you can quickly locate whatever you're looking for when you're trying to select an object in a dropdown list. I see there are a few sequeces in the various lists of objects and I'll bet someone has a few of those documented.
If anyone can help out with that I'd be glad of it!

Many thanks! images/smilies/icon_smile.gif

manisharma31

That's correct.
Microsoft should share this kind of info.

einsTeIn.NET

I know (never verified by MS) only some general rules that you might already know yourself.

• up to 9999 is the standard application range
• between 10000 and 49999 are used for country specific standards
• from 50000 to 99999 is your individual (company's) no. range (also some vertical solutions are located in here if they are not certified)
• between 100.000 and 999.999 (?) there are special standard help tools and temporary standard solutions like update tools
• from 1.000.000 to 98.999.999 you find certified vertical solutions and standard add-on modules
• 99.000.000..?? special W1 enhancements?
• 1.000.000.000.. temporary tables
• 2.000.000.000.. system tables and virtual tables

Within these ranges there might be some additional rules, but I don't know.

jeremyspx

Thanks so much - that will certainly help. Now I just need to get the group 1-9999 broken down.
Hopefully there are bands of numbers there with significance.

vaprog

There's some info available in the section "Numbering Conventions" of the CAL Programming Guide available at the Microsoft Dynamics NAV Support Site in PartnerSource.

jeremyspx

Many thanks, all. I finally have all the info I need on object numbering!

Dakkon

For anyone without access to the document on partnersource, here is the excerpt relating to object numbering:

Similar Reports
Almost identical reports within the application areas are numbered when possible with the same two final digits, even if the report name is different. For example, the Sales Invoice report is number 206 and the similar Purchase Invoice report is number 406. Other examples are the date compression batch jobs for ledger entry tables, which always end with 98, and date compressions for budget entries, which always end with 97. This practice may cause gaps in the numbering sequence, but it helps the programmer when adjustments to similar reports elsewhere in the application are needed.

Codeunits
Codeunit object numbers are not divided into intervals. Use the first available object number when you create a codeunit. Try to group related codeunits together.

Journal Posting Codeunits
The journal posting codeunits follow a pattern that makes it easier to understand a new journal once you are familiar with one group of journal posting codeunits. A group consists of two parts. Codeunits in the first part post a journal, and those in the second part manage the journals.

Codeunit Final Digit | Journal Posting Codeunits
1 = Journal Line-Check
2 = Journal Line-Post
3 = Batch Name-Post

Codeunit Final Digit | Journal Managing Codeunits
0 = Journal-Management
1 = Journal-Post
2 = Journal-Post+Print
3 = Journal-Batch Post
4 = Journal-Batch Post+Print
5 = Register-Show Ledger

Invoices
Codeunits for posting invoices and so on have a system, too:

Codeunit Final Digit | Sales/Purchase Posting Codeunits
0 = Sales/Purchase-Post
1 = Sales/Purchase-Post (Yes/No)
2 = Sales/Purchase-Post+Print

When you create codeunits for the sales application areas, use the same final digit for similar purchase application areas.