Displaying items and prices in view
I am creating a view which should show the items ordered and the extended prices. The problem is the form shows multiple item and extended price fields. Since you can only choose one field for the column I am trying to figure out the best way to handle this. I have tried concatenated the items but they just list side by side on each line. I want them to show as separate values under the correct department. I have tried checking the field to separate values and using new line but it doesn't work. Also, I have used @if@isavailable to only show fields that are filled in but on the extended price it gives me a data type text expected error. would it be best to use an array here? There are so many items and prices that I am not sure how to handle it so that it looks right in the view. I am not sure how to create an array either. I am listed each field in a formula by concatenating them. I don't know if this is the best way. Any help would be appreciated. Thanks.
Software/Hardware used:
Software/Hardware used:
ASKED:
April 29, 2006 12:05 AM
UPDATED:
April 30, 2006 6:01 PM
Answer Wiki:
This is not possible without an architectural change. You either need to have the separate line items spawn/update/delete single documents that can be displayed in views in the manner that you want, or you need to have users create the separate documents and have the main form display the information in the way you are doing it now (multivalue fields, etc.).
I've worked at this issue for about 8 years and have no other solution. Based on your current architecture, it can't be done.
To see all answers submitted to the Answer Wiki: View Answer History.
You again! Reading between the lines I suspect you need to do some more training because your fundamental understanding of what Notes/Domino IS and how to develop applications is way off beam. There is no easy answer to your question because as Brooklyn Egg has said your architecture is wrong from the start. I have replied to your other question and hopefully that will give you a bit of a clue how to define your forms as they relate to the data.