From a1ecdc0f8a75597a45d40c2cdd5ce2738f2ca49e Mon Sep 17 00:00:00 2001
From: John Cardinal <support@ayanova.com>
Date: Tue, 8 Sep 2020 18:11:57 +0000
Subject: [PATCH]

---
 ayanova/src/views/ay-report-edit.vue | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/ayanova/src/views/ay-report-edit.vue b/ayanova/src/views/ay-report-edit.vue
index f8fe2630..02058cea 100644
--- a/ayanova/src/views/ay-report-edit.vue
+++ b/ayanova/src/views/ay-report-edit.vue
@@ -28,7 +28,7 @@
           </v-btn>
 
           <v-btn value="jsPrerender">
-            PrepareData
+            Prepare
           </v-btn>
 
           <v-btn value="jsHelpers">
@@ -142,6 +142,7 @@ http://localhost:7575/api/v8/enum-list/list/AyaType
 determine course of action to handle locale keys list for report based on fields in data source
   I'm thinking of replicating the Client translation.js code for this as it's simple and tested
 
+An error when direct rendering brings UI down unlike during render and error when in report designer, fix it
 
 complete docs as much as needed for now then...