From f831cf0a07c2462e07a0c9f4351a5537e4f01548 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 16 Nov 2021 20:46:54 +0000 Subject: [PATCH] --- docs/8.0/ayanova/docs/ay-report-edit.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/8.0/ayanova/docs/ay-report-edit.md b/docs/8.0/ayanova/docs/ay-report-edit.md index 5da1ea33..1a623306 100644 --- a/docs/8.0/ayanova/docs/ay-report-edit.md +++ b/docs/8.0/ayanova/docs/ay-report-edit.md @@ -251,6 +251,9 @@ ayServerMetaData: * ayApiUrl - this is the URL of the server relative to the report generator and is useful for calling AyaNova API methods in your prepare data function to bring in sources of information from other areas of AyaNova that might not be directly available to your report * HasXXLogo - these keys are set to true if a Logo has been uploaded for each size to AyaNova and are useful for controlling whether or not to show a logo on a report template as can be seen in many of our sample reports +### Accessing top level meta data from inside nested objects + +In Handlebars templates #each or #with blocks the top level meta data needs to be addressed by [switching context](https://handlebarsjs.com/guide/expressions.html#changing-the-context) from inside the nested element to the top level. e.g. `{{../ayServerMetaData}}` rather than `{{ayServerMetaData}}` as would normally work from the top level of the template. ## Localization and Translation