He saves the data in a temporary server file created with this code: The NAV developer has written a module to query the CRONUS database and to export the product list in the pre-described XML format required by the web shop. The location has been defined in a NAV setup table. The production manager wants to have the file in a predefined location on his hard drive. He wants to import the list into his web shop to keep product information updated with data in NAV. The production manager at CRONUS needs an XML file in a specific format containing his latest product list with description, prices, and quantities. The following describes a scenario for the silent file upload/download pattern, both from the user’s point of view and from the NAV developer’s point of view. Using the API in the File Management codeunit instead of the historical API is recommended for all file transferring and file management in NAV implementations. The new API for file transfers in the File Management codeunit: The path to the temporary file can be obtained when this file is created, by using the following function in File Management: := ServerTempFileName(). This remedy introduced an issue: If we use “Magicpath” instead of FromFolder and ToFolder specifications, then where do we upload from and where do we download to? The answer is that they are uploaded to and downloaded from the NAV server’s temporary folder. DOWNLOAD(FromFile, DialogTitle, Magicpath, ToFilter, ToFile) UPLOAD(DialogTitle, Magicpath, FromFilter, FromFile, ToFile) Under this condition, the way to invoke silent file upload or download becomes: Historically, NAV offered a remedy to this, namely by using the “Magicpath” string, which is the constant ‘’. DOWNLOAD(FromFile, DialogTitle, ToFolder, ToFilter, ToFile)Īs you can see, this historical API leaves no place for turning off the functionality for showing a dialog. UPLOAD(DialogTitle, FromFolder, FromFilter, FromFile, ToFile) Since we keep both implementations possible for the sake of backward compatibility, we strongly recommend that you use the file-transfer API provided that is provided with the File Management codeunit (419). In the following, both the historical and the recommended ways of silently transferring files are described. Sometimes, files must be transferred to or from known locations without triggering file-save or file-load dialogs. “Upload” transfers the file from the client to the server.Download” defines transferring a file from the server to the client.Know the PatternĪs a terminology clarification, note that both “upload” and “download” are named as seen from the client’s point of view: By “silently” we mean: without showing a dialog box at upload or download time. This pattern is about silently handing file transfers between NAV Service Tier and the NAV client. The NAV Pattern of the week will be taking a summer break during the rest of August, but we’ll be back with new patterns in September. This is an open initiative to anyone who has documented design patterns which are specific to NAV, please reach back to us either by leaving a comment here, or by writing to us. The Reusable Dynamics NAV Patterns is a joint initiative between the NAV team and NAV partners.
0 kommentar(er)
