You'll notice that one of your field options is Lava. Lava is a templating engine that allows you to customize the way data is presented. With this field type you can mix and match data in lots of different ways. WarningOne CaveatEvery field you would like to use in your Lava must be included in your report. For instance, if you want to use the First Visit date in your Lava, you have to have that field in your report already. (You can disable showing the field in the grid if you wish). You would access your First Visit column using a Lava Merge Field of the name of the column you want to reference, eliminating any spaces. In this case, information in the "First Visit" column would be displayed using the Lava Merge Field {{ FirstVisit }}. Also, you can't reference one Lava column's value from another Lava column. Below are a few examples: Last Name, Nick Name {{ LastName }}, {{ NickName }} Last Name, Nick Name as a link to the ‘Person Profile’ page <a href="/Person/{{ Id }}">{{ LastName }}, {{ NickName }} </a> If baptized, show field as a checkmark {% if BaptismDate != null %} <i class="ti ti-check"></i> {% endif %} For some fields (like Phone Number), use the dot notation to get the property you want {{ Phone.NumberFormatted }} unlisted: {{ Phone.IsUnlisted }} Let's pull this all together: this setup would create a report where the person's name links to their profile, and display a check mark if they are baptized: We should point out that usually you could simply use the stock Person Name field to create a linked name formatted this way, without using Lava. But if you wanted to link to an alternate person profile page, this would give you full control over doing that. You can find out more about Lava on the Rock RMS learning website. If you want more information on using Lava in merge documents, you'll find that in the Rock Admin Hero Guide. TipLet's Go Farther:You can also create your own custom report fields with some developer knowledge. See our developer docs for all the details.