- Print
- PDF
Customizing and Extending Lasernet BC Connector
Note
This article’s intended audience is Business Central developers.
Introduction
This article describes possible ways to customize Lasernet BC Connector by adding custom reports as well as extending the functionality of the basic Lasernet Connector.
Note that:
This article does not cover all possible use cases.
The way your customization works will change according to the changes made in the Lasernet Connector application.
These customizations will not be implemented immediately (only in case of drastic changes).
Consistency is not guaranteed. If you find discrepancies in the code or would like to suggest ways to improve it, please notify Formpipe Support. We always appreciate your feedback.
Getting Started
To start customizing and extending your Lasernet BC Connector, follow these recommendations:
Use the provided source code as a basis for developing your own extension, which will enable handling custom reports.
Visual Studio Code is often preferred over an IDE for development.
The minimum application version dependency is specified in
app.json.The comments within the code explain the purpose of procedures and objects.
Extending your Lasernet Connector application is not only useful for adding custom reports, as it opens up several possibilities in the following areas, including but not limited to:
Connector Interface — see
Src>NewFileConnectInterfacein the attached file.Print Archive Interface — see
Src>NewArchivein the attached file.Document Layout Field Type Interface
Footer Data Interface
Print Method Interface
FileNaming Interface
FileNaming — see
Src>FileNameHandlingSubscriberin the attached file.Path Selection Interface — see
Src>NewPathInterfacein the attached file.Export/Import Handling — see
Src>ExportImportExtin the attached file.Batch Printing — see
Src>BatchPrintin the attached file.Other — see
Src>LanguageFormatAddressin the attached file.
A number of available publishers can help you with customizing Lasernet BC Connector. For more information, refer to the LACPublishers.md file attached to this article.