Open kutting opened 8 years ago
One approach is to remove the payment fields, and make these screens strictly for creating monetary adjustments disconnected from specific events. Another approach is to add an Event ID field, and look up the events and/or per diem data for the event, which must be tied to both the event id and the cadre id.
The first approach seems a little limited; seems like you might want to tie an adjustment to the event that the adjustment needed to be made for. The second approach seems like it leads towards confusion; there is little apparent difference between the automatically generated invoices and ones you could create manually.
With the second approach, you'd definitely want to make the Reason field required.
Stored Procs: For second approach: Cadre.PerDiemInsert Event.GetEventPerDiem
Currently, these screens are confused and confusing. On the per diems screen, we have meal days and lodging days, but not the corresponding rate fields. On both screens, there are payment fields, but no event to tie them to,