Report Desk: Developing Custom Reports

Release Date: 8/3/2020
Version 8.6


Sometimes, a developer will need to create a Report Desk report for a particular customer.  This may be on a contract basis, where the report will only be for the particular customer.  Therefore, it would not be a base (B) report or an enhanced (E) report,  because they automatically would get widely distributed.  It would need to be a custom (C) report that is derived from a base or enhanced report.  

If there is no existing report to derive from, see the following Knowledge Base article for details about how to create one: 

You must run Report Desk as an end-user (registry entry not NETCELLENT, CYBERMAC or GUN) to create a custom (C) report design that can be exported, sent to the customer and imported there.


  • Run Report Desk and bring up the existing report.
  • Press the Save New button to create the new, custom report.
  • Make any desired changes to this new report and then save it.
  • When the new report is completed, export the design and send it to your customer (note the default export/import directory -- you may want to use it at the customer site for convenience),
  • Run Report Desk at the customer site and import the custom report.
The customer now will have the ability to run the custom report.

In certain circumstances, you may want to make sure the customer cannot override an existing report.  When you export a report, you may select The Import side must create a new report option, below, to make sure the customer automatically creates a new report:


When the project to develop this capability started, we specified that a special registry value would allow a NETCELLENT or CYBERMAC developer to create a new custom report that was not derived from an existing report.  The code that would allow that is there, but it is not completely tested.  Look for "REPORTDEV" in the code if that ability needs to be provided in the future.

Modified programs: EL860RD, UDRDesign, UDTDesign

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: Registry Settings
  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
  74. Logging I-O Logic Errors
  75. Report Desk: Developer Documentation Roadmap
  76. Report Desk: Resolution of Pervasive.Data.SqlClient.dll
  77. TB API
  78. Creating HTML Emails for Professional Presentation
  79. EM API - Create and Send an Email
  80. DN API (Document Number Handling)

Feedback and Knowledge Base