Report Desk Database Delivery Strategy

Release Date: TBA
Version 8.6

Purpose

This document outlines the database tables of Report Desk and how they get updated. All Report Desk tables reside in the <Root> directory, where Elliott is installed (e.g. M:\Elliott7).  All Report Desk database files are named starting with SYRD. The first two digits represent the module (SY for System module) and the next two are RD (for Report Desk).  Upon the first installation of Elliott 8.6 & up, all these database files will be copied by the installation automatically. During an update/upgrade installation (when the installed root folder already exists), some of them will be overridden, and some of them will be skipped if they already exist.

During an Elliott 8.6 update, live installation will not be a problem as long as the users run Elliott in Local mode (from their local directory). If the users do not run in Local mode (Shared or Hybrid mode), you should install Elliott 8.6 when no one is running Elliott -- a Report Desk file may need to be updated but cannot because it is in use by an Elliott user.

Updating Report Desk Database Files
The Database files can be classified as Base (maintained by Netcellent), Enhanced (maintained by other Elliott developers) or Custom (maintained by Elliott users)

Tables That Will Always Be Overridden During Installation or Update

  • SYRDCOLB: Specifies special Types (like CustNo for ARCUSFIL.CUS_NO) for table/columns (Base). 
  • SYRDRLGB: Log of changes to base report definitions (Base)
  • SYRDTASK: Automatically updated internal security files (Base)
  • SYRDTLGB: Log of changes to base template definitions (Base)
  • SYRDTTLB: Most popular titles for columns -- suggested first when a column is being added to a report (Base)
  • SYRDTYPB: Version-specific column type info for sizing and formatting.  They must be added by Netcellent (other Netcellent developers must ask Netcellent to maintain theirs) .
  • SYRDUDRB: Master report definitions (Base)
  • SYRDUDTB: Master report templates (Base). 

Tables That Will Only Be Installed If They Do Not Exist

  • SYRDCOLE: Assigned special Types to table/columns (Enhanced).  The maintenance of this table should come from the developer.
  • SYRDPLOG: Report Desk Performance Log (data automatically supplied when running reports)
  • SYRDPRTO: Print output options information saved for the convenience of users (Custom)
  • SYRDRLGCLog of changes to customized report definitions (Custom)  
  • SYRDRLGE: Log of changes to enhanced report definitions (Enhanced)  
  • SYRDTCHG: Tracks which template changes are accepted or rejected by the users (Custom)
  • SYRDTLGE:  Log of changes to enhanced template definitions (Enhanced)     
  • SYRDUDRC: User report definitions. User's changes to reports are stored in this table (Custom)
  • SYRDUDRE: Enhanced report definitions (Enhanced).  The update of this table should come from the developer.    
  • SYRDUDRS: Used for restricting use of a report for specific users (Custom).
  • SYRDUDTC: Report templates for user-customized reports (Custom).  When a user customizes a base report, its template is copied from the base template table and stored in this table.
  • SYRDUDTE: Report templates for user-customized reports (Custom). When a user customizes an enhanced report, its template is copied from the enhanced template table and stored in this table.  

Prior to Creating a New Update   

At Netcellent, Report Desk reports are developed in the production directories (M:\Elliott7).  So, when it is time to create a new update, it is necessary to copy some files from the production directories to the staging directories (M:\ELI86 and M:\ELI86\Bin86).

  • Copy M:\Elliott7\SYRD???B.BTR         to M:\ELI86.
  • Copy M:\Elliott7\Bin86\EL860S.CFG    to M:\ELI86\Bin86.
Then you can build and deliver a new update.

Manual Update

To manually update a customer's Report Desk Reports, create a .Zip file of the files (SYRD???B.BTR and EL860S.CFG) and use that to install at the customer site. It is suggested that you create a temp folder somewhere and use the following command from a command prompt while in the temp folder to copy these files to the temp folder:

  • COPY M:\ELI86\SYRD???B.BTR          (currently there are 7 files that match this pattern)
  • COPY M:\ELI86\BIN86\EL860S.CFG

If there are Netcellent-created enhanced reports, copy SYRD???E.BTR files (2 files match this pattern) to this folder as well.  Then zip the files in this folder and deliver the update. The BTR files are to be copied to <ElliottRoot> folder and EL860S.CFG to <ElliottRoot>\Bin86.  Use PSQL Monitor to make sure that there's no user with these files open before overriding them.


JEG

Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. ElisyscdService
  16. EliNoteService
  17. El2rstimService
  18. EliOrderService
  19. ItemInquiry
  20. EliitmiqService
  21. EliShiptoService
  22. El2getfrService
  23. Steps Required to Test ReportWriter in V8.2
  24. Installation of ElliottService, NETcellent’s Web Services for Elliott
  25. ResellerFinder
  26. EliaptrxService
  27. VendorInquiry
  28. EliloginService
  29. ElislsmnService
  30. EliserhsService
  31. EliatpobService
  32. ElievprcService
  33. ElihdtrxService
  34. ElicuswlService
  35. QueryTurnaround
  36. InvoiceInquiry
  37. ElicustmService
  38. EligetcdService
  39. OrderInquiry
  40. EliordiqService
  41. EliecontService
  42. EliautdpService
  43. El2CrCrdService
  44. Log-Timer / ElliottTimer.Ini Support
  45. Alpha Document Number Support (V8.5/V9.0)
  46. ElliottService System.TypeInitializationException
  47. Feature - Printing API to Dynamically Set Number of Copies
  48. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  49. DD API Changes (V9.0)
  50. PA API (8.5)
  51. Validate License API
  52. AP API
  53. TP API: Temporary Path
  54. Data Structures for Report Desk Defaults and Enforcements
  55. COBOL to VB Interface Programs
  56. IN API: Option to Support Files and Folders Validation
  57. FF API: File Functions
  58. ID API
  59. LK: Links API
  60. FFLNearYou
  61. Report Desk Developing and Debugging
  62. Developing a New Elliott V8.6 Report Desk User Defined Report (UDR)
  63. CustomerInquiry
  64. Elliott API (JSON Web Service)
  65. Animating COBOL Code in Elliott V8.5
  66. Preliminary Programming Changes for Elliott 8.6
  67. CV API
  68. System Lock File Requirements
  69. How to Write Test Codes for C# ESS Projects
  70. Solving the Inability to Debug Elliott on a New Server
  71. Report Desk: Developing Custom Reports
  72. Report Desk Tables
  73. Report Desk Database Delivery Strategy

Feedback and Knowledge Base