When first starting Template Studio, it can be overwhelming at first. There are a lot of options, terminology, and things to learn. This onboarding session will not try to cover it all.
Help getting text, images, etc in to headers and footers can be found here. This explains all the different options available to call data, manipulate it, and display it on a report.
As for setting up the depth area, that was covered here.
What is interesting is that almost every dialogue window has a "Group" field, "Header" field, and "Expression" field. There are a host of others, but these are the primary items of interest for this session.
Group is the grid you are pulling data from.
Header is the specific field from the grid. You can use this if you do not want or need to format the output.
Expression is where you can manipluate data: make a phrase and/or perform calculations.
The item you are editing appears gray as shown above for "Header".
If you do not need to format the output you can just use Group and Header as shown in the image below.
If you leave an item in the header and also use an expression, the expression is used and the header ignored.
Expressions are their own thing. If you want to start learning expressions many references are available. It is recommended you start by learning the rules and syntax as listed here. Build out from there to nesting functions and expressions available.
Top Tip: When writing expressions capitalization matters. Functions must be lower case. Also upper/lower case for grid and field names must match how it is seen by the program.
This tip may make you ask, "How do you know how to write a grid or field name when, as a user, you see it in more readable syntax?". There is a hack for that. In the Group and Header fields there are two phrases. One not in parenthesis, and one in parenthesis. The phrase not in parenthesis is how an end user sees the field. The one in parenthesis is how the application sees the field and is the phrase that must be used in expressions. You can change the Header field as you need to know how to write the field names for an expression. Having Professional Open to confirm you are indeed using the correct field in the expression is helpful as well.