Update the A&R exporter to include legacy fields - for example, legacy Net Revenue columns can now either be calculated (with new records) or can be saved in the system (historical records). The exporter will have to search for legacy Net Revenue values before performing the Net Revenue calculation.
Additionally, the exporter may need to include legacy fields that are not associated with any activity, though business may choose to just never incorporate them in the exporter. There are 5 of these:
Gross Misc Day Use Revenue
(Activity: DAY USE)
Net Misc Day Use Revenue
(Activity: DAY USE)
Additional Details
(Activity: LEGACY DATA)
Source Data
(Activity: LEGACY DATA)
Picnic Shelter Variance Note
(Activity: DAY USE)
Acceptance Criteria:
Confirm inclusion/order of 5 new columns (Jeff/Patrick)
Exporter displays the correct field value depending on whether the record is legacy or not
For this first iteration, legacy records should never calculate values if they are not provided. Values should not be assumed. If the legacy data is not on the legacy record, leave the column blank.
Legacy Data activity fields are added to the exporter.
Additional legacy fields are added to the exporter if they do not line up with existing fields.
historical: new field name “camping party nights” to replace Total Attendance, add Total Attendance (people) field with this calculation ((Standard + Senior + SSCFE +Longstay) * 3.2) (Note: this AC was transferred from #256)
(Transferred from #256) For the historical data, the display would be the same, but will need to be implemented a little differently. This is because the historical data’s display is showing a Total Attendance field that is really Total Camping Party Nights, as no 3.2 multiplier is being applied. So for the historical data the current Total Attendance would be mapped to/ re-labelled as Total Camping Party Nights, and then the Total Attendance would be that number multiplied by 3.2.
Description
Update the A&R exporter to include legacy fields - for example, legacy
Net Revenue
columns can now either be calculated (with new records) or can be saved in the system (historical records). The exporter will have to search for legacy Net Revenue values before performing the Net Revenue calculation.Additionally, the exporter may need to include legacy fields that are not associated with any activity, though business may choose to just never incorporate them in the exporter. There are 5 of these:
Acceptance Criteria:
Legacy Data
activity fields are added to the exporter.(Transferred from #256) For the historical data, the display would be the same, but will need to be implemented a little differently. This is because the historical data’s display is showing a Total Attendance field that is really Total Camping Party Nights, as no 3.2 multiplier is being applied. So for the historical data the current Total Attendance would be mapped to/ re-labelled as Total Camping Party Nights, and then the Total Attendance would be that number multiplied by 3.2.
Notes
Spreadsheet of legacy fields to be provided. See
Get legacy field names from result of BRS-816: Migrate historical data into A&R system
Linked issues
blocks
created by
is blocked by
is cloned by
relates to