Hi, guys. Iโm creating a app where Iโll sell for one client various items.
Iโd like to create a new screen where I select one cliente in a list and I will just adding new items, with its respective amount and price.
As you can see, now every time when I try to add a new product, it just create a new sale, but Iโd like itโd be just in one sale with multiple items inside.
Is it possible? If it is, how to do?
For example in this screen. Iโd like just click in the โ+โ and add a new product bellow!
Maybe you wish to take a look at the Order Capture sample app.
https://www.appsheet.com/samples/An-app-for-managing-customers-products-and-orders?appGuidString=83b...
Omg! This is exactly what I need. Thanks a lot! Iโll use this sample then
@Suvrutt_Gurjar maybe you know how is the โOpen Order Detailsโ column made in the โOrdersโ view? When you click the Add button there is virtual column called โOpen Order Detailsโ and after clicking โAddโ below, it opens the form with details. I am trying to figure it out but I canโt understand.
Thanks in advance!
You may wish to further elaborate on your query.
In general, based on your description so far, in that sample app, the [Open Order Details] column in the โOrdersโ table is based on the slice** โOpen Order Detailsโ.
The expression of the column [Open Order Details] refers to that slice.
In turn, the primary view โOrdersโ is based on the slice โOpen Ordersโ that contains [Open Order Details] column.
Yeah I got it but when I copy that it doesnโt work. I have to study a bit more and maybe will understand. Thanks
Is a part of?
These rows will be considered โpart ofโ the referenced table. They can be added as line items in the form view of the referenced table, and will be deleted if the referenced row is deleted (these deletes will not trigger workflow rules).
THIS OPTION HAS TO BE CHECKED, THEN IT WILL APPEAR IN THE FORM AUTOMATICALLY
Thanks a lot!
Great to know you solved it.
In hindsight, I should have requested a screenshot from you.
I would sugegst you to post sceenshots in future wherever feasible. They definitly help much better than description as in similar cases below.
User | Count |
---|---|
32 | |
31 | |
30 | |
19 | |
16 |