rolling BN

Business Notifications for Dynamics NAV uses NAS for connectivity with the database.
Misconfiguration of NAS is the most frequent cause of problems, when deploying BN.
In order to avoid most of the issues follow these steps:
- make sure a user used for running “Notification Service Deployment Manager” service has access to Dynamics NAV database.
- check if registry information under: HKLM\SOFTWARE\Microsoft\BusinessSolutions\BusinessNotification\NAS Parameters, matches your system configuration.
e.g. “servername=localhost,database=Demo Database NAV (5-1), nettype=TCPS”
- ensure that no errors related to BN are present in the eventlog
- check content of a PropertyStore table in Dynamics NAV database, it should look like this:

and now you should be good to go!

If you are using Business Notifications for Dynamics NAV and would like to see how does the xmlport output look like after an event is triggered, this is a post for you…
In this example “Inventory Status” event is taken into consideration, but you can use it for any other event. In order to be able to save an xml content generated by an xmlport, replace a piece of code related to “Inventory Status” event in codeunit 8000 Business Notification Mgt. with the following:
 
        REPORT::”Inventory Status”: BEGIN
          RecRef.SETTABLE(Item);
          Item.SETRECFILTER;
          ItemXML.SETTABLEVIEW(Item);
          tempBLOB.Blob.CREATEOUTSTREAM(outStream);
         ItemXML.SETDESTINATION(outStream);
          ItemXML.EXPORT;
          F.CREATE(’c:\output.xml’);
          F.CREATEOUTSTREAM(tempOutS);
          tempBLOB.CALCFIELDS(tempBLOB.Blob);
          tempBLOB.Blob.CREATEINSTREAM(tempIns);
          COPYSTREAM(tempOutS, tempIns);
          F.CLOSE();
          ItemXML.”Inventory Status”;
          LineSent := TRUE;
        END;
and just trigger an event the usual way.

/rollo

This Blog is related to Business Notifications for Dynamics NAV.

Welcome!