Are you currently using SQL Server in your operations and looking to call its data into i-Reporter or register the content created in Documents?
With the addition of SQL Server integration, we now offer the following four features!
compatible with SQL Server 2022 and later versions.
This feature import i-Reporter reports based on existing data from the database.
Database → i-Reporter linkage
Automatically create i-Reporter report based on SQL Server database data.
Call the API(Webhook) generated by the mapping Settings of i-Repo Link from the SQL Server database.
This feature registers the report data entered in i-Reporter as new records in the database.
i-Reporter → Database Linkage
Register the report data entered in i-Reporter as a new record in the database.
Webhook notification of i-Reporter
This feature get data from the database and integrates it into i-Reporter reports using ConMas Gateway.
Database → ConMas Gateway → i-Reporter linkage
Use the ConMas Gateway to get the database data into a cluster of i-Reporter reports.
Executing the i-Reporter action clusterer
This feature get master data from the database and integrate it into i-Reporter reports from master selection cluster via ConMas Gateway.
Database → ConMas Gateway → i-Reporter linkage
Use the ConMas Gateway to get the database data into a selection master cluster of i-Reporter reports.
Retrieve master selection cluster data for i-Reporter
For detailed instructions on how to use the system, please refer to the following manual.
Case 1: Automatic Sales Report Generation
<Problem to be solved>
When creating daily or monthly reports from massive sales data stored in SQL Server, manual processing using Excel or similar tools was required, leading to errors and time-consuming efforts.
<Solution with This Release>
With the SQL Server integration, i-Reporter can automatically generate reports based on the existing sales data, significantly improving the efficiency of report creation. This allows the responsible staff to focus more on other important tasks.
<Functions used>
1.Import Report
Case 2: Real-time Reflection of Field Work Reports
<Problems to be solved>
Staff were previously reporting fieldwork using paper or offline forms, which led to delays in digitizing the reports and reflecting them in the database, causing issues with information sharing.
<Solution with This Release>
With i-Reporter, the work reports entered are directly registered as new records in SQL Server, enabling real-time information sharing. This eliminates missed reports and manual input errors.
<Functions used>
2.Registration of input results
Case 3: Real-time Update Inventory Status
<Problem to be solved>
Although inventory data was managed in SQL Server, the latest inventory information was not reflected in the reports used at the field level, leading to lost sales opportunities and overstocking.
<Solution with This Release>
With the integration of SQL Server, automatically get inventory data into the i-Reporter documents, allowing field staff to make ordering and purchasing decisions based on the most up-to-date inventory status.
<Functions used>
3. Get Data of databases
Case 4: Centralized management production master
<Problems to be solved>
Product master was being managed separately at each store, leading to inconsistencies and missed updates in the master data.
<Solution with This Release>
By centralizing product master data in SQL Server and automatically retrieving it into i-Reporter’s master selection clusters via ConMas Gateway, all locations can now use the most current and consistent product information.
<Functions used>
4. Get Master Data of database