Am I the only one dreading what will happen when Microsoft unleashes their BC update regime? Judging by these examples that I've encountered in the last week or so, Microsoft is not up to the task.
You decide whether you will trust an automated upgrade procedure from a company that makes these mistakes:
1) CU's introducing errors.
I recognize the fact that fixing one error may introduce another error. But in this case, installing CU11 meant that applying ledger entries suddenly failed. This error only occurred for licenses without Intercompany functionality.
My problem with this is as follows: Microsoft demands of us to test a minimum of 80% of our extensions. I would assume that they at least adhere to this standard themselves, as testing the base application is surely more important than testing some random extension - the implication of errors is much more severe.
Applying ledger entries would most certainly be encompassed by such a test. Maybe it is, and they just forgot to test it with licenses without Intercompany functionality. I don't know. But breaking such a vital part of the system is simply not okay; it agitates the customers, makes us look like idiots, and wastes both our's and Microsoft's time.
2) CU's are not CU's.
See if you can spot the problem here:
NAV.11.0.26401.NL.CUObjects.fob:
Table 111 Sales Shipment Line 27-07-18 12:00:00 NAVW111.00.00.23572
Table 121 Purch. Rcpt. Line 27-07-18 12:00:00 NAVW111.00.00.23572
Table 247 Intrastat Setup 26-04-18 12:00:00 NAVW111.00.00.21836
Table 248 VAT Reg. No. Srv Config 22-02-18 12:00:00 NAVW111.00.00.20783
NAV.11.0.26401.W1.CUObjects.fob:
Table 111 Sales Shipment Line 28-06-18 12:00:00 NAVW111.00.00.23019
Table 121 Purch. Rcpt. Line 28-06-18 12:00:00 NAVW111.00.00.23019
Table 247 Intrastat Setup 22-02-18 12:00:00 NAVW111.00.00.20783
Table 248 VAT Reg. No. Srv Config 26-01-18 12:00:00 NAVW111.00.00.20348
Excuse my French, but what the hell is up with that? This list (which is by no means complete) took me less than 5 minutes to compile. I expect Microsoft to be in possession of technology that would enable them to reach the same conclusion: applying a CU really just applies a random set of objects. You might think you've upgraded a customer to CU11 by installing the CU11 package, but nothing could be farther from the truth.
With BC, Microsoft wants to apply CU's automatically as they become available. Right now, that strategy is severely compromising both us and our customers because of the horrible quality of deliveries from Microsoft.
Dear Microsoft: we're supposed to be friends, but you're drifting away.
You decide whether you will trust an automated upgrade procedure from a company that makes these mistakes:
1) CU's introducing errors.
I recognize the fact that fixing one error may introduce another error. But in this case, installing CU11 meant that applying ledger entries suddenly failed. This error only occurred for licenses without Intercompany functionality.
My problem with this is as follows: Microsoft demands of us to test a minimum of 80% of our extensions. I would assume that they at least adhere to this standard themselves, as testing the base application is surely more important than testing some random extension - the implication of errors is much more severe.
Applying ledger entries would most certainly be encompassed by such a test. Maybe it is, and they just forgot to test it with licenses without Intercompany functionality. I don't know. But breaking such a vital part of the system is simply not okay; it agitates the customers, makes us look like idiots, and wastes both our's and Microsoft's time.
2) CU's are not CU's.
See if you can spot the problem here:
NAV.11.0.26401.NL.CUObjects.fob:
Table 111 Sales Shipment Line 27-07-18 12:00:00 NAVW111.00.00.23572
Table 121 Purch. Rcpt. Line 27-07-18 12:00:00 NAVW111.00.00.23572
Table 247 Intrastat Setup 26-04-18 12:00:00 NAVW111.00.00.21836
Table 248 VAT Reg. No. Srv Config 22-02-18 12:00:00 NAVW111.00.00.20783
NAV.11.0.26401.W1.CUObjects.fob:
Table 111 Sales Shipment Line 28-06-18 12:00:00 NAVW111.00.00.23019
Table 121 Purch. Rcpt. Line 28-06-18 12:00:00 NAVW111.00.00.23019
Table 247 Intrastat Setup 22-02-18 12:00:00 NAVW111.00.00.20783
Table 248 VAT Reg. No. Srv Config 26-01-18 12:00:00 NAVW111.00.00.20348
Excuse my French, but what the hell is up with that? This list (which is by no means complete) took me less than 5 minutes to compile. I expect Microsoft to be in possession of technology that would enable them to reach the same conclusion: applying a CU really just applies a random set of objects. You might think you've upgraded a customer to CU11 by installing the CU11 package, but nothing could be farther from the truth.
With BC, Microsoft wants to apply CU's automatically as they become available. Right now, that strategy is severely compromising both us and our customers because of the horrible quality of deliveries from Microsoft.
Dear Microsoft: we're supposed to be friends, but you're drifting away.
