eStat Data View - Overview (O11) | OutSystems

Log in

estat-data-view

Stable version 1.0.2 (Compatible with OutSystems 11)

Uploaded

on 20 December 2019

by

0.0

(0 ratings)

estat-data-view

Details

This is a sample application to retrieve data from e-Stat (Japanese government statistics data archive).

Asset screenshot_0

Read more

https://www.e-stat.go.jp/

This application uses REST api to get specific data related with a certain statistics.

https://www.e-stat.go.jp/api/api-info/e-stat-manual

The feature of this application:

Search statistics list with a keyword
Get statistics detail (header and data)
Download statistics data in the CSV format (Please be noted that text encoding is UTF-8)

Release notes (1.0.2)

Added a dependency to 'Text Util 2' extension module.

Reviews (0)

Team

Other assets in this category

mobile-utilities

A group of multiple utilities to use on your Mobile or Reactive applications. The main goal is to bring Text, HttpRequestHandler, and other extensions from the server-side to the client-side.

A safe implementation of Stripe (credit card payment processor). More at www.stripe.com

mark-search-text

Component to mark search text in expression

More from Tsuyoshi Kawarasaki

editable-table-reactive-sample

A sample application to show how to implement ‘Editable Table’ in Reactive Web applications.

highcharts-sample-reactive

A sample application to show how to develop custom Highcharts widgets.

column-based-concurrent-update-sample

This forge component shows a sample implementation to achieve column-based concurrent update. This sample shows how we can implement exclusive access control in the following use cases. Scenario 1: User A and B concurrently access the same record of SampleTable. User A modified ‘Name’ field and saved the data. Then, User B modifies ‘Description’ field and saves the data. In this scenario, User B can save his/her data without any warning. Scenario 2: User A and B concurrently access the same record of SampleTable. User A modified ‘Description' field and saved the data. Then, User B modifies ‘Description' field and saves the data. In this scenario, User B gets warning. The warning says "The Description field was already modified. Will you override it with your data?"