This unit explores how the FMR REST API assists in generating, managing, and securing reporting templates. It covers how templates can be created, modified, and retrieved programmatically, as well as how access rights and worksheet protection are managed.
You'll also learn about security considerations, including role-based access control and password protection, and how FMR ensures data integrity while preventing unauthorised modifications.
By default, FMR restricts the generation of XLSX workbooks from reporting templates. Access is controlled based on user roles.
Select each role type for more details.
Admin can download workbooks for any Data Provider.
Agency can download workbooks for Data Providers maintained by the agency.
Data Provider can download workbooks relevant to them.
Data Consumer and Anonymous cannot download any workbooks.
To modify these default settings, you can enable or disable security restrictions but note that this applies globally. Additionally, it's recommended to set passwords for each agency to ensure that the generated Excel workbooks are protected and to prevent unauthorised modifications. It is via the configured directory service that users are assigned these roles in FMR. Fine-grained assignment of, for example, a specific Data Provider to specific workbooks occurs within FMR.
| Click here to view a code snippet example used when configuring a directory service in FMR involving user/role management. |
If your templates include password-protected worksheets, you can retrieve and update these passwords using the following FMR REST API:
The request body should be a JSON object with agency IDs as keys and their corresponding passwords as values.
Only authorised users are allowed to change these values.
| Click here to view a code snippet example used when considering various security elements involved in retrieving and updating worksheet passwords. |
It is possible to retrieve a list of all reporting templates available to the authenticated user. This is achieved using the following web services endpoint:
GET ws/public/reporttemplate/provider/templates.
| Click here to view a code snippet example used when retrieving a list of all reporting templates available. |
Which of the following actions can be performed using FMR REST API for reporting templates?
Select all that apply and then select Submit.
The FMR REST API manages reporting template retrieval, security, and access. Note: formatting changes are not handled via the API, and security restrictions apply globally. FMR also validates templates before processing.
The correct answers are options 1 and 3.
The FMR REST API manages reporting template retrieval, security, and access. Note: formatting changes are not handled via the API, and security restrictions apply globally. FMR also validates templates before processing.
The correct answers are options 1 and 3.
The FMR REST API manages reporting template retrieval, security, and access. Note: formatting changes are not handled via the API, and security restrictions apply globally. FMR also validates templates before processing.
The XLSX Workbook is tailored to the specific Data Provider, containing only the worksheets and data cells relevant to them. Therefore, it is necessary to specify the Data Provider as part of the request to create the XLSX Workbook.
To create an XLSX Workbook via the FMR REST API, use the following endpoint:
GET
ws/public/reporttemplate/provider/create/{agencyId}/{templateId}/{version}/{providerAgencyId}/{providerId}
Replace {agencyId}, {templateId}, {version}, {providerAgencyId}, and {providerId} with the appropriate identifiers.
| Click here to view an example of a code snippet used when generating an XLSX workbook, taking all factors noted on the preceding screen into consideration. |
Now, let’s explore the process of populating the XLSX workbook with data and address some common questions.
Select each question to reveal the answer.
These steps could be completed by the data reporter, the requesting agency, or both, depending on the specific use case.
Please recall that the Accept Header is used by FMR REST API to specify the input format (XLSX) and the desired output format (XML, JSON, or CSV).
The sdmx.io course Validating and Transforming Data fully addresses this process step.
The Registry can read any XLSX workbook that it has created from a Report Template.
The registry is able to read the XLSX workbook because the SDMX structural metadata relating the XLSX workbook to SDMX artefacts in the registry is embedded and hidden within the XLSX file.
Even if the report template definition has been changed or deleted since the workbook's initial creation, the XLSX workbook contains the necessary metadata structures to be read back in.
For a workbook to be read back into the Registry, the following conditions must be met:
Which of the following conditions must be met for the Registry to successfully read and process an XLSX workbook?
Select all that apply and then select Submit.
The registry can only process XLSX workbooks created from reporting templates. The Registry requires consistent Provision Agreements, Dataflows, and DSDs to process XLSX workbooks. Template changes do not prevent processing.
The correct answers are options 1, 2 and 3.
The registry can only process XLSX workbooks created from reporting templates. The Registry requires consistent Provision Agreements, Dataflows, and DSDs to process XLSX workbooks. Template changes do not prevent processing.
The correct answers are options 1, 2 and 3.
The registry can only process XLSX workbooks created from reporting templates. The Registry requires consistent Provision Agreements, Dataflows, and DSDs to process XLSX workbooks. Template changes do not prevent processing.
Need help finding something? I am an AI Assistant that's here to help!
What are you looking for?
By using this AI-powered service ("Service"), you acknowledge and agree to the following:
This Service uses generative AI to assist with statistical analysis and research. While the Service strives to deliver useful information, the output ("Output") may contain inaccuracies, omissions, or biases. The Output is provided for informational purposes only and should not be considered professional advice. You remain responsible for how you interpret and use the Output.
The BIS makes no warranties regarding the accuracy or completeness of the Output and accepts no liability for any loss or damage resulting from its use.
Do not include or share personal, private, confidential or proprietary information when using the Service.
By using this technology, you agree to the Terms and Conditions.
Ask and get clear explanations about SDMX standards.
Find tools and documentation on website quickly.
Ask about API, software and libraries supporting SDMX.
Locate technical guides, specifications, and FAQs.