website logo
⌘K
Introduction
PORTAL
Agency Whitelabelling
PAGES
Pages - Accessing Page Data
Pagination Layouts
Page Templates
FORMS
Form Confirmation Pages
Adding a Progress Bar
Adding Custom CSS To Show Form Submit Process
Dynamic Content in Workflow and Autoresponder Emails
How to output Custom Field Set fields in a Form's Custom Layout
Custom JavaScript Validation for Forms
File Upload Previews
FAQ
CATEGORIES
Filtering WebApps and Modules by Categories
Outputting Categories on WebApp / Module / eCommerce Layouts
Outputting Category Fields in any Location
Category Detail Layouts
FAQ
COMPANY INFORMATION
Company Information
SITE SEARCH
Site Search
PUBLIC API/ZAPIER
Zapier - Formatting arrays correctly
Public API/Zapier Changelog
MODULES
Module Marketplace
Building Custom Modules
Siteglide Modules
Front-end Submit Modules
DATA STRUCTURES
Automations
Creating WebApps from the CLI
Field Types
WEBAPPS
Front-end Submit WebApps
Layouts
Search and Filtering
Understanding Custom Field Names and IDs
FAQ
CRM
User Details
User Secure Zones
Storing User's Favourite WebApp / Module Items
User's Form Submissions (Cases)
How Users Edit their Email and Password Front End
Editing a User's CRM record Front End with Custom Field Sets
CLI
Introducing Siteglide CLI
CLI Changelog
Secure Zones with CLI
Page Templates with Siteglide CLI
Pages with Siteglide CLI
Includes with Siteglide CLI
Managing Email Templates
Migrate - Manual Form setup
Migrate - Convert existing Forms
Liquid
Accessing Assets
Liquid Dot Notation
Using WebApp Collections- Tutorial
Using the current_user object with Secure Zones
Preventing Duplicate Content with Query Parameters- Canonical URL and Robots.txt
FAQ
GraphQL
Tutorial Overview
About GraphQL
Tutorial 1- Your First Query
Tutorial 2 - Pagination
Tutorial 3 - Filtering the Results
Tutorial 3 - Answers to the First Filtering Challenge
Tutorial 4 - Advanced Filtering
Tutorial 4 - Challenge Answers
Tutorial 5 - Using Liquid to run GraphQL queries on your Site
Tutorial 6 - Variables
Tutorial 6 - Answers to the Variables Challenge
Tutorial 7 - Sorting
Tutorial 8 - Building a Liquid API GET Endpoint Page powered by GraphQL queries
Best Practice and Performance
Module/WebApp Caching
Getting Started with Liquid Caching - to Reduce Server Response time and Improve Performance
Includes
ecommerce/checkout_standard
Frequently Asked Questions
Using Liquid Logic to Check if a field exists, or is empty on the Front End
How do I learn more about Liquid?
How to setup a multi domain start page
Docs powered by archbee 
20min

User Details

The user_details Layout contains the User's name, email and Custom Field Set Data. It can also be used as a container for other CRM Layouts.

Prerequisites

  • This Layout must be outputted inside a Page protected by a Secure Zone

You can use the following links to learn how to set up a Secure Page and the means to access it:

  • Create a Secure Zone
  • Create a Secure Zone Sign Up Form
  • Add a Secure Zone to a Page

Introduction

The user_details Layout contains a {{this}} object with the basics of the User, as well as details that have been added to the CRM record via Custom Field Sets. As such, it can be useful (though it is optional) to use this Layout as the container for all other CRM Layouts. This allows other Layouts e.g. user_secure_zones to also have access to both their specialist data and the more general User data, allowing you to build more complex Layouts.

Syntax

{% include 'user_details', layout: 'default' %}

Parameters:

  • layout - Choose a Layout to use.

File Structure

You can find the user_details Layouts at the following path in Code Editor: layouts/modules/module_5/user_details/

Inside this folder, a single Liquid file can be created to act as your Layout. There is no "wrapper" and "item" file needed for this kind of Layout.

Developing the Layout

Available Standard Fields

  • {{this.name}}
  • {{this.first_name}}
  • {{this.last_name}}
  • {{this.email}}
  • {{this.created_at}} - The date the User first signed up or submitted a Form on the Site
  • {{this.updated_at}} - The last date the User's CRM data was updated
  • {{this['Company']}} - An array of Companies this User is connected to
  • {{this['Address']}} - An array of Addresses stored against this User

Accessing Custom CRM Fields

Inside a user_details Layout, you can access custom CRM fields by using:

  • {{this.properties.user_field_1}} - To get the Field by it's field ID

Accessing Custom Field Sets

Accessing Custom Field Sets will depend on the Custom Field Set data you have set up on your Site. Each Custom Field Set has a unique ID number assigned to it, and data is organised based on this number.

Document image

Accessing data from a Custom Field Set by a specific Custom Field Set ID

Custom Field Sets allow you to store custom fields directly against a Module Item. In the case of the CRM, they are used to store fields against a User which can be kept up-to-date. You can learn more about Custom Field Sets here.

In the following example, I'll be accessing data from the Custom Field Set 3 (Profile). You can use this example and replace the ID 3 for the ID of your Custom Field Set.

  • {{this.custom_field_sets.cfs_3.cfs_name}} - The name of this Custom Field Set
  • {{this.custom_field_sets.cfs_3.properties.cfs_field_3_1}} - The first field of the Custom Field Set. Replace the ID number at the end to fetch any field.

You may find it more helpful to output your available fields as JSON and use this to write your code. Outputting {{this}} will fetch the data as JSON, e.g.

Document image

Updated 19 Oct 2021
Did this page help you?
Yes
No
UP NEXT
User Secure Zones
Docs powered by archbee 
TABLE OF CONTENTS
Prerequisites
Introduction
Syntax
File Structure
Developing the Layout
Available Standard Fields
Accessing Custom CRM Fields
Accessing Custom Field Sets
Accessing data from a Custom Field Set by a specific Custom Field Set ID