Ideas for implementing the quotation creation function

Ask for Help
1

Ideas please.

I am creating a car maintenance history sharing app.

In this app, the maintenance shop owner can register the maintenance menu on the app.
Car owners can find the menu and place an order with the garage on the app.
The maintenance shop that receives the order can create an estimate based on the maintenance history of the vehicle registered in the app and additional explanations from the owner.
When creating an estimate, you select what to do this time from the work details and parts list linked to the initially registered menu, or add a new one.




The UX on the app will continue after this, such as sharing work progress, making payments, and creating history, but the current issue is the realization of a UX that allows repair shops to create estimates from templates.

The data structure of this app takes the form of coexisting data with different statuses such as menus, orders, and history in one data table called “records”.

And in this record table, the relation between work details and parts table is established.

When the car owner orders from a screen displaying a record with a status of “Menu”, a record with a status of “Order” is created by copying the original record’s values.

When creating the “Order” record, we copy the Row ID of the original record, so we can refer to the work detail list and parts list associated with the original record.

The problem comes after this.

In car maintenance, it is not enough to do work and parts replacement according to the template menu.

We customize the work details and parts list according to the condition of the vehicle.

However, 80% work according to the template menu.

Therefore, from the work details and parts list of the copy source “menu”, I would like to copy only the necessary amount for this order in a form linked to the “order” record.

I really wanted to copy the relevant work details and parts list when the order action was executed, but after looking around the official guide and this community, it seems that it is not possible yet.

I tried to do this by adding a row in the list component’s collection item action, but I couldn’t set the row id of the “order” record I wanted to associate.

After trying various things, it seems that the add row action cannot bring in values from other tables.

Therefore, we are looking for ideas that successfully pull Row IDs and ideas that change the UX itself.

2

Actually it can. Bring the value into the user profile then select from user profile in action
 or use single relation + lookup in the table that initiates the add row
 or query
 or single value
 basically anything that can copy a value
 do that first then you can use it in the add row.

3 Likes
3

Thank you. It is solved.

I adopted the following method.
・Write the RowID of the record you want to associate with the parts list in the column of the user profile.
・When copying a parts list, refer to RowID from the user profile and write.

When using relations + lookups or queries, it was difficult to filter to identify records when the same menu was ordered by multiple users.

With the above method, the action of pooling the RowID is extra at first, but the data structure can be very simple.

The UI uses the title bar action of the table component to write the RowID of the record you want to associate data with to the user profile and transition to a new screen.

Place a table component that displays the original record parts list and the copied parts list on the new screen.

By placing an add line button in the collection item action of the original record parts list, we were able to realize a UX that copies the list speedily.

It’s still in the testing stage, so there may be omissions in the operation, but I’m glad that I was able to achieve what I wanted to do.

Thank you.

1 Like
4

User Specific Columns can help you with that.

2 Likes
5

thank you.

We considered a user-specific column, but decided against it. The reason is that I wanted to share one order record with the orderer and the orderer, but there was a problem that the orderer could not see it when using the user-specific column.

Currently, this is supported by changing the record owner (user email) for each status.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.