Ruby Code for Merging XLTM Files into DOTM: A Complete Guide
# Converting XLTM to HTML
require 'aspose_cells_cloud'
api_cells = AsposeCellsCloud::CellsApi.new
name = 'file.XLTM' # String | The document name.
opts = {
save_options: AsposeCellsCloud::SaveOptions.new, # SaveOptions | Save options.
}
begin
result = api_cells.cells_save_as_post_document_save_as(name + ".HTML", save_options)
p result
end
# Converting HTML to DOTM
require 'aspose_words_cloud'
api_words = AsposeWordsCloud::WordsApi.new
name = 'name_example.HTML' # String | The document name.
opts = {
filename: 'file.DOTM', # String | The file name.
folder: 'folder_example', # String | The document folder.
storage_name: 'storage_name_example' # String | storage name.
}
begin
request_save_options_data = api_words.HtmlSaveOptionsData.new({:FileName => filename + '.%!s(MISSING)'})
request = api_words.SaveAsRequest.new(name: remote_name, save_options_data: request_save_options_data, folder: remote_folder)
end
How to Megre XLTM to DOTM in Cloud Apps
- Initialize WordsApi with Client Id, Client Secret, Base URL & API version
- Set requestDocument assign the local XLTM file name
- Set requestDocumentListDocumentEntriesFileReference and assign local DOTM file name
- Set requestDocumentListDocumentEntries and set file_reference, import_format_mode parameters
- Create DocumentEntryList instance and assing requestDocumentListDocumentEntries to document_entries parameter
- Call AppendDocumentOnlineRequest to merge XLTM file with DOTM document requestDocument and requestDocumentList
- Call WordsApi appendDocumentOnline with parameters
Get Started with Aspose.Total REST APIs
- Create an account at Dashboard to get free API quota & authorization details
- Get Aspose.Words and Aspose.Cells Cloud SDKs for Ruby source code from Aspose.Words GitHub and Aspose.Cells GitHub repos to compile/use the SDK yourself or head to the Releases for alternative download options.
- Also have a look at Swagger-based API Reference for Aspose.Words and Aspose.Cells to know more about the REST API.
FAQ
- What is XLTM Format?The XLTM file extension represents files that are generated by Microsoft Excel as Macro-enabled template files. XLTM files are similar to XLTX in structure other than that the later doesn’t support creating template files with macros. Such template files are used to generate and set the layout, formatting, and other settings along with the macros to facilitate creating similar XLSX files then.
- What is DOTM Format?A file with DOTM extension represents template file created with Microsoft Word 2007 or higher. It is similar to the popular DOCX file format other than it retains the user defined settings for reuse in case of creating new documents. Such documents are more often used in offices where a standard template file is generated with settings like page information, margins, default layout and macros, and is used to create new documents from it when required. DOTM files, however, save macros, that are a series of commands in the form of recorded actions for automatic completion of a task. This helps save time in carrying out actions that are repeated in completion of a task.
- How can I get started with Aspose.Total REST APIs?Quickstart not only guides through the initialization of Aspose.Total Cloud API, it also helps in installing the required libraries.
- Where can I see the release notes for Aspose.Total Cloud API?Complete release notes can be reviewed at Aspose.Total Cloud Documentation.
- Is it safe to merge XLTM to DOTM in the Cloud?Of course! Aspose Cloud uses Amazon EC2 cloud servers that guarantee the security and resilience of the service. Please read more about Aspose's Security Practices.
- What file formats are supported by Aspose.Total Cloud API?Aspose.Total Cloud can merge file formats from any product family to any other product family to PDF, DOCX, XPS, image(TIFF, JPEG, PNG BMP), MD and more. Checkout the complete list of supported file formats.
- I can not find the SDK for my favorite language. What should I do?Aspose.Total Cloud is also available as a Docker Container. Try using it with cURL in case your required SDK is not available yet.