Friday, May 18, 2012 6:55 PM
Building a helpdesk ticketing system in LS. Right now we have a choice list for Systems Effected, there are 32 total. The users are telling me that there are cases in which a reported issue can effect more than one system. Is there an good way to capture something like this in LightSwitch?
Friday, May 18, 2012 8:15 PM
if i understand right, i believe this is quite easily solved with One-To-Many relationship.
TABLE - Systems_Effected, where You will have 32 choices pre-entered.
TABLE - Ticket_General_Info (where You will have ticket number, clients name, etc...)
TABLE - Ticket_Rows, "child" table of Ticket_General_Info, each row representing affected system.
this table will be related to "Systems_Effected" and to "Ticket_General_Info"
so, ticket can have one or more rows, depending on how many systems are affected (each row shows to one record from System_Effected choices, selected from Auto-Complete box).
i hope this helps?
should you need some more details, just let me know.
Saturday, May 19, 2012 2:15 PM
This smells like a common junction table need. Your senerio maps directly to Order Details and products many to many relationship if that helps your understanding. You need a juntion table between Tickets and Systems (i.e. TicketSystems)
And here is a shot of the LS screen