1. HTML Table Data:
2. JavaScript Code:

1. HTML Table Data

Export HTML data in Excel, even before we have to load some data into an HTML table. So here we have to make fetch employee table data and load it in an HTML table with table columns like name, address, gender, designation, and age. Here we have created an HTML table with id employee_data. So this id we will use for fetch this HTML table data in JavaScript code. Under this HTML code, we have made one button tag with id export_button, so when use has clicked on this button, then HTML table data will be download in Excel file format without refresh of a web page using JavaScript.

2. JavaScript Code

In this tutorial, we have to use SheetJS JavaScript Library to export HTML table data to Excel using JavaScript. So first we have to include the following SheetJS library link at the header of this HTML web page.

In the JavaScript code part, first we have created the html_table_to_excel(type) function. This function has used sheetJS library function and convert or write HTML table data to excel format and download it in a browser without refreshing the web page.

Once a function is ready then we have to call html_table_to_excel(type) function on the button click event, so for the trigger button click event, we have to use the addEventListener method. So when a user has clicked the button the html_table_to_excel(type) function is called with the xlsx file type. Then it will download the HTML table data in .xlsx format Excel file in the browser without having to refresh a Web page on the client-side.

The post How to Export Html Table to Excel Sheet using JavaScript appeared first on scmGalaxy.

In JavaScript, a Module is a JavaScript file where we write codes. The object is a module that is not available for use unless the module file exports them.

Exporting Module

export – The export statement is used when creating JavaScript modules to export functions, objects, or primitive values from the module so they can be used by other programs with the import statement.

There are two different types of export – named and default. You can have multiple named exports per module but only one default export.

Default Export

You can have only one default export per module. A default export can be imported with any name.

mobile.js

Named Export

You can have multiple named exports per module. Named exports are useful to export several values. During the import, it is mandatory to use the same name of the corresponding object.

mobile.js

Named Export

You can have multiple named exports per module. Named exports are useful to export several values. During the import, it is mandatory to use the same name of the corresponding object.

mobile.js

Importing Module

import –  The static import statement is used to import bindings that are exported by another module. Imported modules are in strict mode whether you declare them as such or not.

Importing Defaults

You can have only one default export per module. A default export can be imported with any name.

mobile.js

app.js

Importing Named

You can have multiple named exports per module. Named exports are useful to export several values. During the import, it is mandatory to use the same name of the corresponding object.

mobile.js

app.js

Importing All

mobile.js

app.js

Importing Default and Named

mobile.js

app.js

The post How does the Import and Export module work in JavaScript? appeared first on scmGalaxy.

Location:

BuildForge Home Dir – Platform

To display command syntax, use bfexport with no options.

 $ ./bfexport

 Usage: bfexport -l

 or:

 bfexport [-c comment] [-f filename] [-g] [-s] [-L] [-n] <Project name or UUID> <Version name>

 Options :

 -l: Lists all projects in the system and their project UUID.

-c : Add a comment to the output XML.

-f : File to write the output to.

-g : Include group users.

-s : Include all servers.

-C : Include servers collectors (requires -s).

-L : Include LDAP configuration.

-n : Include template notifications.

Project must be a valid project name or project UUID.

Example

To list the project names and project IDs that are stored in the Build Forge database, use

 > bfexport -l

To send project data to an XML file,

> bfexport -f <file_name>. You must specify the -f <file_name> option to generate a file that can be used to import project data.

To write output to a file, use the -f <file_name> option. In the following example, helloworld is the output file name and the project ID is used instead of the project name.

> bfexport -c “Saving a copy of project before making changes” -f helloworld 675B57CC-8366-11DD-B2E0-043C04E44E1A

To export the default project snapshot only, use the <project_name>.

> bfexport -f helloworld test_project

To export one snapshot of a project, use the <project_name> <snapshot_name>.

> bfexport -f helloworld test_project snapshot_1

If the parent project snapshot is not the default project, you must specify the <project_name> followed by the parent keyword to export the parent project snapshot.

 > bfexport -f helloworld test_project parent Document

 ./bfexport -c “Saving a copy of project before making changes” -C -s -f Citius-Coverity-Full-parent 6d66e5050c5a1000bcd5cd010bc00bc0

The post BuildForge – Exporting projects using bfexport | BuildForge Guide appeared first on scmGalaxy.