On export of an Agreement as JSON (e.g. using https://folio-testing-okapi.aws.indexdata.com/erm/sas/080c3b20-f4d8-412a-9acf-e54dbbf52676/export) where an Agreement line has "Custom coverage" set, this is not included in the export, but rather the PCIs default coverage is used.
- Add a journal e-resource to an Agreement
- Edit custom coverage for that agreement line
- See that in the Agreement Lines display and "E-resources covered by this agreement" the coverage for that line is indicated as custom coverage and is using the coverage you have just set
- Export as JSON
- See that in the exported file the custom coverage is not used, but the underlying coverage set on the PCI instead
Applies to JSON export