This article describes the steps to take regarding the Dataverse Online OData v2.0 endpoint removal with respect to custom ExportToWord buttons.
IMPORTANT: This article is only relevant if you created a custom “ExportToWord”-button that triggers the DocumentsCorePack Client. The CreateDocument Dialog for server-based document generation is not affected.
Am I affected by this change?
To help determine if you’re affected by this change, you need to verify if you have added custom ExportToWord buttons by using the “Advanced Button Configuration” function as shown in the below screenshot that shows the configuration option in the local DocumentsCorePack Server Configuration tool.
Step-by-step description: Troubleshoot
Step 1: Download the updated code template (using the web API instead).
Step 3: In Web Ressources look for ptm_dcp_custombuttonactions.js
Important: Make a backup copy of the current content!
Step 4: First, you need to unzip the ptm_dcp_custombuttonactions.zip file that you previously downloaded.
Once you have done this, open the “ptm_dcp_custombuttonactions.js” code template included in the file using a script editor like Notepad++.
Then add your custom code to the top section of the template script.
To initiate the ExportToWord process from your custom code, execute the following function:
ptmDCPCBCustomButton.startExportToWord(selectedIds, typeCode, selectedItemCount, entityName, nameOfDCPTemplate);
Step 5: After you have inserted your custom code into the new template, you will need to update the content of the “ptm_dcp_custombuttonactions.js” web resource in Dataverse with your modified script.
Step 6: Save and publish it.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to email@example.com.