Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot delete a service order header in the Swiss version of Microsoft Dynamics NAV 2009 with Microsoft SQL Server database


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • French (Switzerland) (fr-ch)
  • German (Switzerland) (gr-ch)
  • Italian (Switzerland) (it-ch)

↑ Back to the top


Symptoms

Assume that you apply hotfix 2497206 in the Swiss version of Microsoft Dynamics NAV 2009. When you delete a service order header in Microsoft Dynamics NAV 2009 with Microsoft SQL Server database, you receive an error message that states another user has changed the service order header.
For more information about hotfix 2497206, click the following article number to view the article in the Microsoft Knowledge Base:
2497206 Service item line dimensions are not deleted from the Document Dimension table when you delete a Service Order or run the Delete Invoiced Service Orders report in Microsoft Dynamics NAV
This problem occurs in the following products:
  • The Swiss version of Microsoft Dynamics NAV 2009 R2
  • The Swiss version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

↑ Back to the top




Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
  • The Modify permission for the object that you will be changing.
  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.


Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, follow these steps:
  1. Change the code in the Properties in the Service Header table (5900) as follows:
    Existing code
    ...
    END;
    CLEAR(ServLogMgt);
    ServLogMgt.ServItemOffServOrder(ServItemLine);

    // Delete the following line.
    ServItemLine.DELETE;

    UNTIL ServItemLine.NEXT = 0;
    ServDocLog.RESET;
    ServDocLog.SETRANGE("Document Type","Document Type");
    ...
    Replacement code
    ...
    END;
    CLEAR(ServLogMgt);
    ServLogMgt.ServItemOffServOrder(ServItemLine);

    // Add the following lines.
    ServItemLine.CalledFromServHeaderDelete(TRUE);
    ServItemLine.DELETE(TRUE);
    // End of the lines.

    UNTIL ServItemLine.NEXT = 0;
    ServDocLog.RESET;
    ServDocLog.SETRANGE("Document Type","Document Type");
    ...
  2. Change the code in the CalcInvDiscForHeader function in the Service Header table (5900) as follows:
    Existing code
    ...
    <add id="CH1341" dev="SRYSER" request="CH-START-400A-SWS34" date="2005-06-30" area="SWS34"
    releaseversion="CH4.00A">
    Added Post Code Feature
    </add>
    </changelog>
    }
    END.
    }
    ...
    Replacement code
    ...
    <add id="CH1341" dev="SRYSER" request="CH-START-400A-SWS34" date="2005-06-30" area="SWS34"
    releaseversion="CH4.00A">
    Added Post Code Feature
    </add>

    // Add the following lines.
    <add id="NEWCODE" dev="v-aysin" date="2011-06-06" area="SERVICE"
    baseversion="CH6.00.01" releaseversion="CH6.00.01" feature="NEWCODE">
    Not able anymore to delete a service order header. It works fine without SQL.
    </add>
    // End of the lines.

    </changelog>
    }
    END.
    }
    ...
  3. Change the code in the Properties in the Service Item Line table (5901) as follows:
    Existing code
    ...
    CLEAR(ServLogMgt);
    ServLogMgt.ServItemOffServOrder(Rec);

    // Delete the following lines.
    ServOrderMgt.UpdateResponseDateTime(Rec,TRUE);
    UpdateStartFinishDateTime("Document Type","Document No.","Line No.",CALCDATE('<CY+1D-1Y>',WORKDATE),0T,0D,0T,TRUE);
    // End of the lines.

    ServOrderMgt.UpdatePriority(Rec,TRUE);
    DimMgt.DeleteDocDim(DATABASE::"Service Item Line","Document Type","Document No.","Line No.");
    END;
    ...
    Replacement code
    ...
    CLEAR(ServLogMgt);
    ServLogMgt.ServItemOffServOrder(Rec);

    // Add the following lines.
    IF NOT CalledFromDelete THEN BEGIN
    ServOrderMgt.UpdateResponseDateTime(Rec,TRUE);
    UpdateStartFinishDateTime("Document Type","Document No.","Line No.",CALCDATE('<CY+1D-1Y>',WORKDATE),0T,0D,0T,TRUE);
    END;
    // End of the lines.

    ServOrderMgt.UpdatePriority(Rec,TRUE);
    DimMgt.DeleteDocDim(DATABASE::"Service Item Line","Document Type","Document No.","Line No.");
    END;
    ...
  4. Change the code in the Global Variables in the Service Item Line table (5901) as follows:
    Existing code
    ...
    Text053@1083 : TextConst 'ENU=You cannot change the contract number because some of the service lines have already been posted.;DES=Sie k”nnen die Vertragsnr. nicht „ndern, da einige der Servicezeilen bereits gebucht wurden.;ITS=Impossibile modificare il numero di contratto perch‚ alcune righe di assistenza sono gi… state registrate.;FRS=Vous ne pouvez pas modifier le num‚ro de contrat car certaines lignes service ont d‚j… ‚t‚ valid‚es.';
    Text054@1084 : TextConst 'ENU=If you change the contract number, the existing service lines for this order line will be re-created.\Do you want to continue?;DES=Wenn Sie die Vertragsnr. „ndern, werden die vorhandenen Servicezeilen fr diesen Auftrag erneut erstellt.\M”chten Sie fortfahren?;ITS=Modificando il numero di contratto, le righe di assistenza esistenti per questa riga di ordine verranno ricreate.\Continuare?;FRS=Si vous modifiez le num‚ro de contrat, les lignes service existantes de cette ligne commande vont ˆtre recr‚‚es.\Souhaitez-vous continuer ?';
    UseServItemLineAsxRec@1079 : Boolean;
    SkipResponseTimeHrsUpdate@1085 : Boolean;
    Text055@1086 : TextConst 'ENU=You cannot change the %1 because %2 %3 has not been received.;DES=Sie k”nnen %1 nicht „ndern, weil %2 %3 nicht empfangen wurde.;ITS=Impossibile modificare %1 a causa della mancata ricezione di %2 %3.;FRS=Vous ne pouvez pas modifier l''/le/la %1, car %2 %3 n''a pas ‚t‚ re‡u.';
    Text056@1048 : TextConst
    'ENU=One or more service lines of %6 %7 and/or %8 exist for %1, %2 %3, %4 %5. There is a check mark in the %9 field of %10 %11, therefore %10 %11 cannot be applied to service line of %6 %7 and/or %8.\\ Do you want to apply it for other service lines?',
    ...
    Replacement code
    ...
    Text053@1083 : TextConst 'ENU=You cannot change the contract number because some of the service lines have already been posted.;DES=Sie k”nnen die Vertragsnr. nicht „ndern, da einige der Servicezeilen bereits gebucht wurden.;ITS=Impossibile modificare il numero di contratto perch‚ alcune righe di assistenza sono gi… state registrate.;FRS=Vous ne pouvez pas modifier le num‚ro de contrat car certaines lignes service ont d‚j… ‚t‚ valid‚es.';
    Text054@1084 : TextConst 'ENU=If you change the contract number, the existing service lines for this order line will be re-created.\Do you want to continue?;DES=Wenn Sie die Vertragsnr. „ndern, werden die vorhandenen Servicezeilen fr diesen Auftrag erneut erstellt.\M”chten Sie fortfahren?;ITS=Modificando il numero di contratto, le righe di assistenza esistenti per questa riga di ordine verranno ricreate.\Continuare?;FRS=Si vous modifiez le num‚ro de contrat, les lignes service existantes de cette ligne commande vont ˆtre recr‚‚es.\Souhaitez-vous continuer ?';
    UseServItemLineAsxRec@1079 : Boolean;
    SkipResponseTimeHrsUpdate@1085 : Boolean;

    // Add the following line.
    CalledFromDelete@1100 : Boolean;

    Text055@1086 : TextConst 'ENU=You cannot change the %1 because %2 %3 has not been received.;DES=Sie k”nnen %1 nicht „ndern, weil %2 %3 nicht empfangen wurde.;ITS=Impossibile modificare %1 a causa della mancata ricezione di %2 %3.;FRS=Vous ne pouvez pas modifier l''/le/la %1, car %2 %3 n''a pas ‚t‚ re‡u.';
    Text056@1048 : TextConst
    'ENU=One or more service lines of %6 %7 and/or %8 exist for %1, %2 %3, %4 %5. There is a check mark in the %9 field of %10 %11, therefore %10 %11 cannot be applied to service line of %6 %7 and/or %8.\\ Do you want to apply it for other service lines?',
    ...
  5. Change the code in the UpdateStartFinishDateTime function in the Service Item Line table (5901) as follows:
    Existing code
    ...
    StartingDate,StartingTime,FinishingDate,FinishingTime,
    ServHeader3."Contract No.",ServHeader3."Contract Serv. Hours Exist");
    Modifyheader := TRUE;
    END;

    // Delete the following line.


    IF Modifyheader THEN
    ServHeader3.MODIFY;
    END;
    ...
    Replacement code
    ...
    StartingDate,StartingTime,FinishingDate,FinishingTime,
    ServHeader3."Contract No.",ServHeader3."Contract Serv. Hours Exist");
    Modifyheader := TRUE;
    END;
    IF Modifyheader THEN
    ServHeader3.MODIFY;
    END;
    ...
  6. Change the code in the SetCalledFromDelete function in the Service Item Line table (5901) as follows:
    Existing code 1
    ...
    "Vendor Item No." := ServItem."Vendor Item No.";
    CheckWarranty(ServHeader."Order Date");
    END;
    BEGIN
    {
    <changelog>
    <add id="CH1390" dev="SRYSER" request="CH-START-370" date="2004-02-25" area="SWS39"
    ...
    Replacement code 1
    ...
    "Vendor Item No." := ServItem."Vendor Item No.";
    CheckWarranty(ServHeader."Order Date");
    END;

    // Add the following lines.
    PROCEDURE CalledFromServHeaderDelete@30(DeleteCalled@1100 : Boolean);
    BEGIN
    CalledFromDelete := DeleteCalled;

    END;

    BEGIN
    // End of the lines.

    {
    <changelog>
    <add id="CH1390" dev="SRYSER" request="CH-START-370" date="2004-02-25" area="SWS39"
    ...
    Existing code 2
    ...
    releaseversion="CH3.70A">Field 7+8 Size 30 -> 50</add>
    <change id="CH1391" dev="nibelofa" date="2009-02-23" area="SWS39"
    baseversion="CH3.70A" releaseversion="CH6.00.01" feature="NAVCORS23233">
    Spaces and other unallowed characters removed-replaced from names of variables</change>
    </changelog>
    }
    END.
    }
    ...
    Replacement code 2
    ...
    releaseversion="CH3.70A">Field 7+8 Size 30 -> 50</add>
    <change id="CH1391" dev="nibelofa" date="2009-02-23" area="SWS39"
    baseversion="CH3.70A" releaseversion="CH6.00.01" feature="NAVCORS23233">
    Spaces and other unallowed characters removed-replaced from names of variables</change>

    // Add the following lines.
    <add id="NEWCODE" dev="v-aysin" date="2011-06-06" area="SERVICE"
    baseversion="CH6.00.00" releaseversion="CH6.00.01" feature="NEWCODE">
    Not able anymore to delete a service order header. It works fine without SQL.
    </add>
    // End of the lines.

    </changelog>
    }
    END.
    }
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Swiss version of Microsoft Dynamics NAV 2009 R2
  • The Swiss version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

Removal information

You cannot remove this hotfix.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Keywords: kbqfe, kbmbspartner, kbmbsquickpub, kbmbsmigrate, kbsurveynew, kbnoloc, kbmbscodefix, kb

↑ Back to the top

Article Info
Article ID : 2604501
Revision : 1
Created on : 1/7/2017
Published on : 9/14/2011
Exists online : False
Views : 237