Accessing Developer Tools
There are 3 main ways to access Google Chrome's Developer Tools:
-
View > Developer > Developer Tools
-
Google Settings > More Tools > Developer Tools
-
Keyboard Shortcuts
Mac Users: ⌥ the Option (alt) + ⌘ the Command () key + I
Windows User: Ctrl + Shift + I
Configuring Developer Tools for Athennian Doc Coding
- When the Developer Tools are accessed, you will first land on the Console view, which can look a little intimidating.
😱 Don't be intimidated!
- In the DevTools Console:
-
Navigate to the Filter field:
- Type
DXT_variablesinto the filter field. This filters out unrelated logs. You’ll notice that all logs have been cleared and there’s nothing displayed at the moment. To generate log entries containing the DXT variables, initiate the ATH Document Generation workflow, which assembles the variables automatically.
-
Navigate to the Filter field:
- In certain sections of Athennian, you can trigger the Document Generation workflow. When you click the Generate or Merge button in Tasks or Supporting Documents modal -
DXT_variableslog will appear in the console. For detailed guidance on initiating Document Generation workflows in Athennian, please visit [this link]. - You have now populated the
<DXT_variables>🍋 log in the console using the most common Document Generation workflow, Generate Summary.- Click the triangles next to each array to expand or collapse the DXT collections.
- You can explore all related root collections - keep clicking the triangles for each collection name to inspect and review the variables and their values.
- All the collections and variables are listed in alphabetical order.
You can populate the
DXT_variablesrepeatedly by clicking Merge or Generate in different workflows. This allows you to inspect how the collections vary across various document generation workflows, or to check variable values if you have updated an entity’s data record.
💡Tips & Tricks
How do I code with the Developer Tools?
The Developer Tools allow you to see all the variables that are available through each specific workflow (eg. when generating a Share Register through the Register/Ledger buttons, the variables that you may code with will be different from the variables available if you are generating a document through an Annual Compliance Task)
Make sure you are merging/generating the document through the right workflow, and have the Developer Tools open before you click Merge/Generate. Once the document generated screen ✅ appears, you will see the <DXT_variables> path outlined above, and be able to see all the variables that you can use!
The Data You Know
Using a familiar entity record or a test entity you created can go a long way in helping you understand the shape of data as it's stored in Athennian. For example, if you know the entity number of a record, you can easily find the corresponding variable by looking for that entity number in the Developer Tools.
Docking the Developer Tools Pane (See it Your Way)
The Developer Tools can be viewed from different sides of your screen based on your preference. Use the More button to see the docking choices. This setting will be saved once set (or you can leave it as the default).
The options appear as follows (in the order they appear from left to right in the Dock Side choices.
Pop-up as a separate window:
On the Left side of the screen (within the same browser window):
On the Bottom of the screen (within the same browser window):
On the Right side of the screen (within the same browser window):
Troubleshooting the DXT_variables "Overflow" Message
When attempting to retrieve DXT_variables after clicking Merge or Generate, the Console may display the following error message instead of the expected data: Object, variable object size overflow, and was cleared
This message indicates that the workflow attempted to load too much data at once (e.g., from an entity with thousands of transactions or certificates), exceeding the Console's display limit.
To resolve this, we must reduce the amount of data loaded into the DXT_variables log. This is done by configuring the template's Selected Data settings and restricting the data collections that Athennian loads for that specific template.
Navigate to the template being used (e.g., in the Templates tab of an entity).
Click the View Template Settings (gear) icon.
In the Template Settings modal, scroll to the Selected Data section.
Uncheck the boxes for any data collections not required for the template (e.g., Certificates, Transactions).
Click Save.
Return to the entity and re-run the document generation workflow (e.g., Generate Summary).
The
DXT_variableslog will now populate, containing only the collections selected in Step 4.
Important: This method creates a trade-off. The
DXT_variableslog will only display the data for the collections that were left checked. Data from unchecked collections (e.g.,certificates,transactions) will not be available for inspection in the Console.
⚠️ File a Support Ticket
If the "overflow" message persists, or if all data collections must be inspected for coding and debugging, the issue may require engineering assistance.
In this situation, file a support ticket with the Athennian Support team. Please include the entity's name and the specific workflow being used so the team can investigate the data size issue.