Thank you for reading. I’m Omatsu from the Business Management Department, and I’ll be handling this blog post. This time, as an event introduction, I’ll be sharing details about the End-of-Term Report Meeting held in November 2025.
The first presentation was from Team 1, which primarily handles AI. The content focused on video generation utilizing AI. Details are as follows.
Planning
Narration Text Generation
Image material generation
Generate videos using AI based on the generated images
Edit
Music Generation
I actually watched a video utilizing AI, and I was truly amazed—there were no inconsistencies in the footage used, and the narration was polished and stylish.
Next up is my presentation on the e-commerce site I’m responsible for. Details are as follows.
Number of shops that signed contracts this term
Number of shops publicly launched on the e-commerce site this period
The Full Picture of the Strategic Shift (AI-generated video)
A Year of Transformation
Transition to the Kimono Market
New Content Strategy
Verification: Data and Expert Perspectives
2026 Growth Roadmap
Next Fiscal Year Activities
We submitted monthly reports, but looking back on this period as a significant milestone of one year, I believe it was a year where we saw substantial growth in the number of shops that reached contract and public launch stages, demonstrating that our daily efforts have yielded tangible results.
Following that, we reviewed events from this term (such as the office relocation) and discussed plans for the next term, during which it was announced that the structure would undergo significant changes from the current setup.
Employee Social Gathering
After the end-of-term report meeting, all employees enjoyed a Christmas dinner at Pergola, the restaurant at the Marriott Associa Hotel! We saw everyone’s eyes light up as they admired the array of roast beef and desserts on display! Additionally, this gathering included those joining the company next April, providing an opportunity to deepen bonds. Everyone seemed to be having a wonderful time.
As the networking event drew to a close, we observed the prospective hires voluntarily moving around the room, actively engaging with our employees.
Summary
It was a valuable opportunity to learn about and share the activities we’ve undertaken over the past year. I frequently see AI-generated videos posted as promotions for the e-commerce site I manage, but learning about the generation process firsthand made me truly appreciate their amazing capabilities.
Additionally, this was my first time being given my own presentation time at the end-of-term report meeting, and I was very nervous. However, I feel I was able to clearly convey the initiatives and challenges I faced this term.
That’s all for this introduction. Stay tuned for our next blog post!
As a tech blog, I’d like to share what I’ve been learning recently. This time, I’ll walk you through how I set up a Vue 3 development environment using Cursor, a code editor with built-in AI features.
Requirements
・Node.js ・Cursor ・Vue3 ・Vue Router
Installing Node.js
Download the installer from the official website The latest version at the time of writing is 24.12.0 (LTS) Download the Windows installer
Follow the installation wizard. If you don’t have any specific preferences, just clicking ‘Next’ through all the steps is fine.
You can basically keep clicking ‘Next’ here as well, but if you plan to use various Node.js modules in the future, it’s a good idea to check this option. However, it’s not necessary for this setup.
That’s it! Node.js is now set up and ready to go.
Installing Cursor
Download the installer from the official website. The latest version at the time of writing is 2.2.44. If you don’t have any specific preferences, you can proceed with the default settings during installation. After installation, you’ll be prompted to log in, so it’s a good idea to create an account on the official website beforehand for a smoother setup.
Adding Extensions to Cursor
Add the following extensions to Cursor
Japanese Language Pack for VS Code ・Japanese localization
npm ・Support for npm
Npm Intellisense ・Auto-completion for npm modules in import statements
Vue (Official) ・Support for Vue
Vite ・Support for Vue development server
Creating a Vue 3 Project
Go to File > Open Folder and open the location where you want to create your project.
Open the terminal with [Ctrl + @]
Run the following command in the terminal to create the project
npm create vue@latest
Type ‘y’
Enter your preferred project name and package name.
Select the packages you want to add.
Give it a try
TypeScript ・Must be added
JSX Support ・Enables writing Vue in JSX/TSX syntax. Add this if you prefer a React-like style. ・Turned off for this setup.
Router ・Essential for page navigation ・Must be added
Pinia ・State management library ・Add if you need to manage login info, user data, or shared state
Vitest Add if you want to automate unit testing
End-to-End Testing ・Add if you want to automate tests that include browser interactions
ESLint ・Linting tool to check code style ・Must be added
Prettier ・Automatically formats your code ・Must be added
You’ll be asked whether to enable experimental features. Since we won’t be using them this time, just press Enter to keep the default.
You’ll be asked whether to create the project without sample code. For this setup, select ‘No’ to include the sample code.
The project creation will begin, and once it’s complete, a project folder will be generated.
Reopen the created project folder in Cursor and run the following command
PS C:\vue3\startupVue> npm install
Once the dependencies are installed, the project setup is complete.
Starting the Vue app
Run the following command to start the development server
npm run dev
If the launch is successful, the following screen will be displayed
You can stop the server by typing [q] in the console.
That’s it! We’ve set up a Vue 3 development environment using Cursor. If this sparked your interest, try setting it up on your own PC too!
Happy New Year. I am Hideaki Takahashi of Dandelions Co., Ltd. We sincerely thank all of you for your support throughout the past year. We look forward to your continued support this year.
Toyokuni Shrine 1
Last October, we relocated our office to a new building.
Looking back on last year, a major milestone for us was the office relocation to our new headquarters in October.We were able to complete the relocation successfully thanks to the cooperation of our valued business partners and, above all, each and every member of our team. We sincerely thank you all.
Dandelions New Headquarters
Immediately after the move, the change in environment meant many unfamiliar things, and it was a continuous process of trial and error. However, we have gradually become accustomed to working in the new office building. To be honest, though, I don’t feel like it’s “finished just because it’s ready.” Rather, I feel like this is where the real plan, set in our new headquarters, finally begins.
With our new headquarters as the stage, we will further cultivate an environment conducive to taking on challenges.
We aspire to be a team where ideas flow more freely and challenges are embraced with greater enthusiasm, all to create better services. By leveraging our new base, we will enhance the quality of our daily work, increase learning opportunities, and further cultivate an environment that encourages taking on challenges.
Company atmosphere
Next April, we will welcome new members.
And next April, new employees are scheduled to join us. I myself am very much looking forward to welcoming new colleagues. With fresh perspectives and energy joining the team, this should be a year where the company itself takes another step forward in its growth. As the welcoming side, I want to prepare an environment where they can feel secure in taking on challenges and fully commit to their development.
Toward fields where people can thrive across generations
We want to create a positive atmosphere and provide opportunities for challenge so that everyone joining our company feels, “This is a company that will continue to step up and grow.”At the same time, we will place greater emphasis than ever before on creating fields where individuals can thrive across generations, regardless of age or years of experience. The drive of our young talent, the momentum of our mid-career professionals, and the depth of our veterans—all contribute to the company’s strength. We are committed to building such a team.
Toyokuni Shrine 2
We look forward to your continued support this year.
This year, Dandelions will continue to build upon our valuable work centered around “technology” and “people.” We sincerely appreciate your continued guidance and support.
May this year be one of health and abundance for you all. We look forward to your continued support this year.
Dandelions Co., Ltd. President and CEO: Hideaki Takahashi
I’m oz, and I’ll be covering this study session article. This time, we held our study session “Low-Code Development Experience with OutSystems Part 3,” so let me share how it went!
Continuing from last time, this study session also aims to “deepen understanding of low-code development and OutSystems by experiencing development with OutSystems.” With many members joining for the first time this session, it became an even more lively study session.
The study session will proceed as follows:
① Development Experience with OutSystems ② Summary and Q&A
Development Experience with OutSystems
While delivering a PowerPoint presentation, we simultaneously progressed with actual development using the OutSystems environment. The main activities conducted this time were as follows: Data Import and Export ・Let’s create an Entity (table) ・Let’s create master screens (list/detail) from an Entity: Scaffolding ・Let’s read and write Entity data from the created screens
Let’s create an entity (table)
First, add a table to store the data handled by the app. Next, give the table a name that reflects its purpose so you can understand what kind of information it manages. After creating the table, proceed to add columns. Assign each column a name corresponding to the actual item you wish to store, and simultaneously determine the data type based on the type of data to be stored, such as string, number, or date.
Let’s create master screens (list and detail) from an Entity: Scaffolding
Typically, when creating a master screen, you need to design and implement the list screen and detail screen from scratch. However, OutSystems offers a convenient mechanism that automatically generates a master screen to a certain extent simply by preparing a table. This automatic generation feature is called Scaffolding. Using Scaffolding creates basic master screens such as list displays, registration, updates, and deletions as templates, greatly reducing development effort.
Let’s try reading and writing Entity data from the screen we created.
The master screen created with Scaffolding allows basic operations as-is, but adding further functionality makes it more practical. This time, we will enable direct data entry from the web screen, bulk data import using Excel files, and conversely, the ability to export data as Excel files. From the web interface, you can register or update data one record at a time by setting values in the input fields on the screen and saving them. Additionally, by adding the Excel import feature, you can register or update multiple records at once simply by uploading an Excel file. Furthermore, enabling the output of registered data as Excel files simplifies data verification and integration with other systems. By combining screen input, Excel import, and Excel export, the master screen is designed to be user-friendly for daily operations.
Summary
This study session covered even more practical content than the last one, and I believe it successfully conveyed the benefits of low-code development and OutSystems. As development progressed, when questions or difficulties arose, nearby members actively exchanged ideas, discussing questions and issues together. As a result, I feel that my understanding has deepened even further.
We plan to continue hosting study sessions focused on OutSystems development! Stay tuned for our next article.
In this engineer blog, I’ll introduce what I’ve been learning recently. This time, I’ll explain automatic column generation in OutSystems Data Grid.
OutSystems Data Grid is a spreadsheet-like grid that can be displayed and interacted with within an OutSystems application.
This article assumes prior knowledge of OutSystems Data Grid.
Problem Statement
For example, let’s say we have a grid like the one below.
The usual way to create it would be as follows.
Set the data to be displayed into a Structure that matches the grid layout, convert it into a list, transform it into JSON using ArrangeData, and set the resulting JSON as the grid’s data.
Place a column widget on the grid for each column to be displayed, and configure each header, column width, display conditions, and so on.
For a grid with six columns like the one above, it’s not too difficult. However, if the number of columns to display is variable, creating it becomes more challenging.
You need to determine the maximum number of columns to display, then prepare the Structure from step 1 and the column widgets from step 2 to match that maximum number. Additionally, you must control the visibility of each column based on how many you actually want to display. As a result, all the columns up to the maximum exist, but only the desired number of columns are visible.
Especially for step 2, if the grid’s configuration is even slightly complex—such as having merged headers with dynamic labels—the amount of work required increases significantly.
If the maximum number is around 100, it might take some time, but it’s still manageable. However, I once faced a case where the maximum number reached nearly 1,500. At that time, I looked into whether it was possible to generate the grid columns using JavaScript.
As a result of the automatic generation, step 1 of the usual method still needs to be done as is, but step 2 becomes much simpler.
Prerequisites
In a grid like the one below, the columns outlined in red are the target for automatic generation. (The left three columns are placed as usual. The auto-generated columns are on the right.)
The cells in the auto-generated columns will be set to read-only. The column order in the grid will be fixed and cannot be changed.
The data to be displayed in the grid has already been retrieved and is set to the grid as described in step ① above.
The header labels (such as ‘グループ1’, ‘データX’, ‘名名名’, etc.) are dynamic and have already been retrieved in a format that can be passed into JavaScript. (In the sample JavaScript code, these input parts will be shown in bold.)
In the implementation JavaScript, we use a variable called dataGrid. You can obtain dataGrid as shown below. (Let gridId be the ID of the configured grid.)
var dataGrid = OutSystems.GridAPI.GridManager.GetGridById('gridId').provider;
Preliminary Research
From the link below, I found that it’s possible to push columns into dataGrid.columns.
Upon further investigation of dataGrid, I found that in addition to columns, there is also columnGroups. I thought that by pushing to columnGroups, it might be possible to create grouped, merged header columns.
Implementation Flow
In the ‘On After Fetch’ action after retrieving the data, implement it as follows.
The first column of ‘グループ1’
// Create the element to push
var newColGroup = new wijmo.grid.ColumnGroup (
{header: 'グループ1', align: 'left', columns: [
{header: 'データX', align: 'left', columns: [
{header: '名', binding: 'Data1', width: 100, align: 'left', isReadOnly: true}
]}
]}
)
// Push newColGroup into columnGroups
dataGrid.columnGroups.push(newColGroup);
The second column of ‘グループ1’
// Create the element to push
var newColGroup = new wijmo.grid.ColumnGroup (
{header: 'データ1', align: 'left', columns: [
{header: '名名', binding: 'Data2', width: 100, align: 'left', isReadOnly: true}
]}
)
// Push newColGroup into the columns of the target columnGroup
// columnGroups[3] refers to the created "Group 1", which is at index 3 in columnGroups
dataGrid.columnGroups[3].columns.push(newColGroup);
the ‘グループ2’ column
// Create the element to push
var newColGroup = new wijmo.grid.ColumnGroup (
{header: 'グループ2', align: 'left', columns: [
{header: 'データV', align: 'left', columns: [
{header: '名名名', binding: 'Data3', width: 100, align: 'left', isReadOnly: true}
]}
]}
)
// Push newColGroup to columnGroups
dataGrid.columnGroups.push(newColGroup);
As shown above, grouped columns with merged headers are created one by one. By adjusting the structure of newColGroup and the target of the push accordingly, it should be possible to create column groups with different structures.
additional support
When automatically generating columns, the following two points must be taken into consideration.
The variable dataGrid represents the grid obtained as a JavaScript object. At the time the ‘On After Fetch’ action is executed after data retrieval, the grid must already exist. One way to handle this is to set the data retrieval action’s timing to ‘Only on Demand’ and execute it in the ‘OnReady’ action.
If the grid contains columns with editable cells, a post-edit check is performed on the entire row to determine whether any cells were edited. However, if this check tries to access the automatically generated columns, it will result in an error. (In the grid used as an example in this article, the ‘Settings’ column is editable.)
To handle this, adjust the edit check in the grid’s ‘OnInitialize’ action using JavaScript as shown below.
// Regular cell edit check
var originalCheck = OutSystems.GridAPI.GridManager.GetGridById('gridId').features.dirtyMark._isDirtyCell;
// Adjust the check
// Immediately treat cells in auto-generated columns as unedited
// Since columns with index 3 and above are auto-generated, control with "columnIndex > 2"
var newCheck = function (rowIndex, columnIndex) {
if (columnIndex > 2) {
return false;
} else {
var checkResult = originalCheck.call(this, rowIndex, columnIndex);
return checkResult;
}
}
// Apply the adjusted check to the grid
OutSystems.GridAPI.GridManager.GetGridById('gridId').features.dirtyMark._isDirtyCell = newCheck;
変数dataGridは、グリッドをJavaScriptオブジェクトとして取得したものになります。データ取得後のOn After Fetchアクションが実行される時点で、グリッドが存在しなければなりません。一つの対応方法として、データ取得アクションのタイミングをOnly on Demandに設定して、OnReadyアクションで実行することができます。
