2020. 2. 28. 18:25ㆍ카테고리 없음
It’s still a hassle. But something we’re all used to work with.
But sometimes, ID’s of objects need to be renumbered. You have to move a piece of functionality to a new number band, or you want to incorporate a piece of an app into another database, which would result in overlapping object id’s. No matter what situation. Every developer sometimes need to renumber objects.How?Well, it’s not really the topic of this blog. But now that we’re talking about it: I like to use the Mergetool for this.
Object Renumbering Tool For Navision 2009 Online
It never failed on me, and seems to take all internal references into account! So I can strongly advise you to use t.So what is the topic of this blog?Well, since NAV 2013 R2, you really have to be careful when you start renumbering tables! You could potentially loose data!Say what?When renumbering tables in NAV 2013 R2 with a wrong build, you will lose your data in that table! Without any warning.Example:Suppose we have a custom table 50001, called “TestRenumber” with data:Let’s try to renumber it to 50002:Compile the tableWhen running the table, the data is gone:In a way, Microsoft has blogged about it in their blog about.
I strongly recommend to read this blog, so that you understand this synchronization that is going on in R2. In the blog, Microsoft has a few developer best practices, which I would like to repeat here, as I fully support them:.
Do not use Build No. Lower than than 36310As a partner, you take this as the “RTM Build No.” starting point for NAV 2013 R2 and deploy this platform hotfix in the future projects while you also convert existing installations.NOTE: As per common best practice, we recommend that you download / request / test and deploy the latest platform hotfix for Microsoft Dynamics NAV 2013 R2. Additional steps Only if updating an existing site, and your Customer already had data in the new tables. After the new text file is created, but before it is imported, rename each of your old tables (just put the word ‘Old’ in front of each current name) in the database. Remove all of the other Objects (forms, reports, codeunits and dataports) which were created in the old system (do NOT remove base application Objects).
Then import your text file and recompile all Objects. Create a process (normally a report) to transfer the data from each old table to its corresponding new table. The TRANSFERFIELDS function can be used to transfer the data from the old record to the new record. Once the data has been transferred and verified, remove the old data, the old tables, and the conversion process.Is this a big problem?Well, I don’t want to make too much of a fuss about it. In a way, renumbering is being done – relatively – a lot, I believe.
But the combination “renumbering and preserving data”. It’s just a coincidence that I bumped into it, as I had a situation like it: developed it without thinking too much of number bands. And later on came into the situation that I HAD to move all of it. The workaround that is described above obviously works like a charm – just hope you don’t have to do this for too many tables;-). Let’s not exaggerate. We’re talking about renumbering in combination with keeping data here.
That’s it.Sure, it has to do with supporting the MT environment, but then again. I won’t miss this flexibility too much;-). Thanks to PowerShell.
NAV has become far more flexible on other parts. So is NAV really less flexible?I know of quite some (big) implementations already on MT. It’s a new business, for sure.
And people that are doing On Premise business, have difficulties to see what benefit it has for them. Also in our company, sure.In my opinion, On premise will exist for long. But who am I. I’m just a NAV developer;-). Archives.
(2). (2). (4). (2). (2). (2).
(2). (3). (2). (3). (3). (2).
(2). (2). (2). (4). (2). (3).
(1). (3). (6). (2).
(3). (4). (2).
(1). (5). (2). (3).
(2). (3).
(2). (3). (3).
(2). (4).
(3). (7).
(2). (2). (2). (3). (3). (3).
(4). (3). (3). (4). (3). (5). (2).
(2). (4).
(3). (4). (4). (3). (3). (3).
(3). (2). (3).
(4). (1). (3). (3). (2). (3). (2).
(4). (6). (2). (3). (2).
Object Renumbering Tool For Navision 2009 Mac
(5). (2). (2). (5). (3).
(6). (5).
(7). (4). (3). (2). (4). (1). (1).
(1).