Before upgrading into V3sp3 check this . . .

In technet there is an interesting topic (#9999) about mismatching layers in sp3. (See technet.navision.com) br, KK

It sounds interesting - but I can’t find the topic. Will you please post a link. Thanks.

quote:


Originally posted by Esa
In technet there is an interesting topic (#9999) about mismatching layers in sp3. (See technet.navision.com) br, KK


Contribution 9999.1 from willys, Germany: Difference between SYP-GLS-GLP-DIS-DIP We noticed that changes made to the form CustTable and the form VendTable, changes made in SP3 - SYP layer, are not present in GLP and DIP-layers. Example: validatewrite/create methods on datasource (We used the latest DIS/DIP layers available (dated april 2004).) A form is stored entirely in the layer it has been changed, and this are all lower layers. I don’t believe it is our job to merge modifications in SYP and DIS/DIP. The latest DIP version should be based on the latest SYP-version. Now we have to change things in VAR/CUS/USR layer, with all the consequences. Has anyone had similar experiences? Can we expect more problems like this? Kind regards, Willy. Contribution 9999.2 from mcostello, United States: Re: Difference between SYP-GLS-GLP-DIS-DIP Hello Willy. I would like to thank you for your observation. Have you reported this issue to support? If you have what is the case number? /Michael Contribution 9999.3 from Helmut Wimmer, Austria: SYP changes not merged into DIS/DIP??? Hi! I must say I am shocked about what I’m reading here! Has this already been reported in the service system ? That is obviously one of the most annoying errors I have come across in my 5 years time with Axapta. I was just in the process of updating an application to SP3 and I have to stop that now because the DIS/DIP layers are obviously wrong. Helmut Contribution 9999.4 from andrae, Germany: intended? Hi, looking at the changes / differences, it seems to me that someone decided to have things differennt in the glg and dip layer. Dont forget that dis / dip is a correction of the sys / syp and not the other way round. So, if everything is working well - fine! If there is a malfunction, put it in the service system. Best regards, Tobias Contribution 9999.5 from willys, Germany: Contribution 9999.6 from willys, Germany: Reply corrected I don’t think the diffirences between SYS/SYP and GLS/GLP and DIS/DIP are intentional, as Tobias states. I believe it’s a matter of time. If you have to wait before SYP SP3-layer is ready, before you can start work on GLP and DIP layers, the complete package will be finished a lot later. Look’s as if things are based on SYP SP2. To Michael: Not reported in the service system, we don’t have access to that. (And yes it’s a shame TECHNET has to go!) And to Helmut: There isn’t just a problem with DIS/DIP, GLS/GLP aren’t updated either with SYP/SP3. Kind regards, Willy. Agree I agree with Willy. If you take as an example VendTable_ds.create method there was a piece of code added in syp layer with SP3, that just didn’t find it’s way into glp layer. I don’t know in which way/order updated code is propagated from one MSB branch to another, but maybe people working with dip layer just took the wrong glp layer as base of their work. And in the same week MSB decided to move technet from public site to partnersource - interesting br, KK