How to Customize Docentric SSRS Replicas
When you start a new project, we recommend installing the latest version of Docentric AX (the core product) and the latest version of Docentric SSRS replicas.
Set up Docentric SSRS replicas
The next step, after you finish the installation process, is to open Docentric report setup from the Docentric AX workspace in D365FO and click the Reload all button. All Docentric replicas will appear in the setup and be ready for use.
Customizing Docentric SSRS replicas
Change Docentric SSRS replicas artifacts directly
Each replica consists of a Docentric design (aka template) and the corresponding custom Docentric DSP class that provides the report specific placeholders available for use in print destination settings such as Email body and Output filename. These classes also enable use of Print archive improved by Docentric. But most importantly, Docentric DSP classes should serve as a starting point for your customization.
This is what we meant under “Starting point for your customization”.
We also recommend changing Docentric designs directly in the Docentric AX SSRS Replicas project. Provided Docentric designs look identical to built-in SSRS designs so you will probably want to replace them with your own designs. You can still keep the initial Docentric designs for learning purposes, and you can avoid reloading them as System templates by decorating their AOT Resource artifact with the SkipLoadSystem=true entry in Tags.
Inherit/Extend Docentric SSRS replicas artifacts
Alternatively, you can create your own model, which will reference the Docentric AX, Docentric AX Extension and Docentric AX SSRS Replicas models (and all other models you will need for report customization, e.g. Application Suit). Then you can create new DSP classes (1) by inheriting or (2) by extending the existing DSP classes from the Docentric AX SSRS Replicas model for those reports to which you want to add additional data and/or placeholders, and also provide the corresponding Docentric designs tailored to your needs.
Where to keep Docentric designs
There are four different template storage types: (1) Azure blob storage, (2) SharePoint, (3) File system (only for on-premises or during development on OneBox) and (4) AOT Resources.
If you choose to store your templates (aka Docentric designs), which are just ordinary MS Word documents, as AOT Resources, they will be deployed alongside other customizations via deployable packages. These kind of templates are called System templates. After deployment they have ability to load themselves in our main report setup, where you can replace them (i.e. change them) with some other templates stored on Azure blob storage, SharePoint or File system. These templates are called Customized system templates.
However, you don’t have to operate with System and Customized system templates at all, but instead use only so called Custom templates. In this case, in your UAT/Test/Production environment you will upload/download your templates freely to/from Azure blob storage, SharePoint (which supports template versioning OOTB) or File system.
When using only Custom templates, we have provided Export/Import tools to support transfer of both metadata and content for all Custom templates between environments. Also, by copying one environment to another including Azure storage, your Custom templates content stored on Azure storage will get copied automatically.
Upgrading Docentric SSRS replicas
If you want to get new features and bug fixes, you will only need to upgrade Docentric core product (version releases are usually published each two or three months).
Docentric SSRS replicas are fully featured and we don’t really develop them further. Basically, what we occasionally do is adding a new replica, or an extension which fixes some misbehavior that is not necessary related to Docentric.
You can always check with us if you encounter an issue, or if you notice that we published some new replicas you would like to use, and we will gladly help you to upgrade without installing the whole model but rather separate artifacts.