SIERA Expression Builder

1. Feature Overview

SIERA Expression Builder tool lets Admins create their own expressions that can be used to easily retrieve and manipulate data on any report. This is an evolving tool and presently helps users write basic aggregate functions with multi-conditions.

Note: This article will only list the different expressions you can use. To learn how to write expressions, read this article – Writing Expressions using SIERA Expression Builder.

 

2. Prerequisites

SIERA is a paid feature. To enable it for your account, contact your account manager or support@leadsquared.com.

 

3. Expression Builder Rules

  • A field in the expression builder has to be enclosed with backticks. For example, `data_source_name.field_name`.
  • The field name has to be appended with the entity. For example, `Leads.Lead Stage`.
  • The values for a string have to be in single quotes. For example, 'string'.
  • An array of values must be enclosed in square brackets. For example, ['Value 1', 'Value 2'].
  • SIERA stores empty date values as 01-01-1925. If you want to write an expression with null date values excluded, use ToYear(<date field>) > 1925. Similarly, ToYear(<date field>) <= 1925 will filter rows with date values not defined. For example,
    • CountDistinctIf(`Leads.Prospect ID`, ToYear(`Leads.Date of Birth`) > 1925) will return leads who have a defined date of birth.
    • CountDistinctIf(`Leads.Prospect ID`, ToYear(`Leads.Date of Birth`) <= 1925)will return leads where the date of birth is not defined.
  • Clicking on a tab will enter the selected function from the expression builder.

 

4. Types of Expressions

Expressions in SIERA are of 3 types –

  • Aggregated ExpressionsAn aggregate expression uses an aggregate function to summarize a selected metric. These include expressions like Count, CountDistinct, Sum, Min, Max, and Avg.
    • For example, if we want to get a count of leads, we can use the expression Count(<field name>)
  • Conditional ExpressionsConditional expressions use aggregate functions along with conditions.
    • For example, if you want to Count leads only if they are from Google and Facebook, using an expression of Count() will not work. In this case, we can use CountIf(<condition>).
  • Calculated ValuesCalculated Values are a combination of 2 or more expressions (aggregated or conditional) on arithmetic functions like +, , *, or /.
    • For example, if we want the percentage of leads from Google and Facebook over total leads, we can use (Countif(<condition>)/Count(<field name>))*100. Calculated Values do not support drill-down in the reports or dashboards. 

 

5. Navigate to Expression Builder

Follow the steps below to navigate to the expression builder:

  1. Click Create Report.
  2. Select a Data Source.
  3. Click the + Add Values button.
  4. Click + Custom Values.

navigating to expression builder on SIERA

This sections below will help you understand the syntax and usage of various functions available for building expressions.

 

6. Operators, Conditions, and Constants

Function & Example Expression
Equal​ Used to compare if 2 values or fields are equal.

`Leads.Lead Stage` = 'Customer'

Not Equal​ Used to compare if 2 values or fields are not equal.

`Leads.Lead Stage` != 'Customer'

Less Than​ Used to compare if a value or field is less than compared to another value or field.

`Leads.Lead Score` < 50

Less Than or Equal​ Used to compare if a value or field is less than or equal to another value or field.

`Leads.Lead Score` <= 50

Greater Than – Used to compare if a value or field is greater than compared to another value or field.

`Leads.Lead Score` > 50

Greater Than or Equal ​Used to compare if a value or field is greater than or equal to another value or field. 

`Leads.Lead Score` >= 50

in – Used to determine whether the value exists in a list of values.

`Leads.Lead Stage` in ['INVALID', 'DISQUALIFIED']

notin – Used to determine whether the value does not exist in a list of values.

`Leads.Lead Stage` notin ['INVALID', 'DISQUALIFIED']

Text Constant Text constant to be written as ‘Text’, with quotations.

`Leads.Lead Stage` notin ['INVALID', 'DISQUALIFIED']

Number Constant Text constant to be written as 50, without quotations.

Leads.Lead Score >= 50

Addition Used to add two values in your report. Fields (Number type) and constants can be used as operands

Sum(`Leads.Custom 2`) + Sum(`Leads.Custom 3`)

Subtraction Used to subtract two values in your report. Fields (Number type) and constants can be used as operands. 

Sum(`Leads.Custom 2`) - Sum(`Leads.Custom 3`)

Multiplication Used to multiply two values in your report. Fields (Number type) and constants can be used as operands. 

(Sum(`Leads.Custom 2`) + Sum(`Leads.Custom 3`)) * 100

Division Used to divide two values in your report. Fields (Number type) and constants can be used as operands. 

(Sum(`Leads.Custom 2`) + Sum(`Leads.Custom 3`)) / 100

Like – Matches string against SQL LIKE pattern (case-sensitive).

If(`Leads.Lead Stage` LIKE '%Pro%', 'This is Prospect','This is not Prospect')

ILike – Matches string against SQL LIKE pattern (case-insensitive).

If(`Leads.Lead Stage` ILIKE '%pro%', 'This is Prospect','This is not Prospect')

 

7. Logical Expressions

Function & Example Expression
and An and expression returns true if all of its operands are true. The and expression will work if there is more than 1 expression inside it. 

For example, let’s say you want to return TRUE when a Lead has converted (Stage is Customer) and if the Source is either from Referral or Affiliate.

(<expression1>) and (<expression2>)

(`Leads.Lead Stage` = 'Customer') and (`Leads.Lead Source` in ['Referral','Affiliate'])

or – An or expression returns true if any of its operands are true. The or expression will work if there is more than 1 expression inside it. 

For example, let’s say you want to return TRUE when a Lead has converted (Stage is Customer) or if the Sub-stage is either Converted or Paid.

(<expression1>) or (<expression2>)

(`Leads.Lead Stage` = 'Customer') or (`Leads.Sub Stage` in ['Converted','Paid'])

 

8. Aggregate Expressions

Note:

  • Expression fields should be included in row grouping. Owner Auto ID should be preferred for partitioning.
  • Some of the expressions below support Partition. It divides a value or dataset into separate segments so each segment can be processed independently. This is useful when you want calculations or logic to run within specific groups rather than across the entire dataset.
Function & Example Expression

SUM

The Sum function allows you to calculate the sum of numeric values within a given field.

Example 1 – Create the calculated column which stores the sum of the field mx_Custom_2. We can use the Expression Builder to write the expression.

Sum(<fieldname>)

Sum(`Leads.Custom 2`)

Example 2 – Calculates a running or total sum of Lead Score counts within each Owner’s partition.

Sum(field, PartitionBy(...), OrderBy(...))

Sum(Count(`Leads.Lead Score`), PartitionBy(`Leads.Owner Auto ID`))

SumIf

The SumIf function allows you to calculate the sum of numeric values within a given field along with some conditions.

Example 1 – Create the calculated column which stores the sum of the field mx_Custom_2 when Stage is “Customer”. We can use the Expression Builder to write the expression as given.

SumIf(<fieldname>,<condition>)

SumIf(`Leads.Custom 2`, Stage = 'Customer')

Example 2 – Sums the count of Lead Score values only for rows where Lead Score is greater than 0, grouped by Owner.

SumIf(field, condition, PartitionBy(...))

SumIf(Count(`Leads.Lead Score`) , `Leads.Lead Score` > 0, PartitionBy(`Leads.Owner Auto ID`))

Count

The Count function lets you count the number of occurrences of a specific value or field within a given range.

​​​​​Example 1 – Create the calculated column which stores the count of the leads.

Count(`Leads.Prospect Id`)

Example 2 – Counts the number of rows in each Team partition after computing the summed Lead Score for each row.

Count(Sum(Leads.Lead Score), PartitionBy(Users.Team))

CountIf

The CountIf function allows you to count the number of occurrences that meet a specific condition.

Example 1 – Create a calculated column that stores the count of the leads when the lead stage is ‘Prospect’.

CountIf(`Leads.Lead Stage` = 'Prospect')

Example 2 – Counts how many leads have Status = Converted within each Owner partition.

CountIf( Lead.Status='Converted', PartitionBy(Lead.Owner Id))

CountDistinct

The CountDistinct function allows you to count the unique number of occurrences that meet a specific condition.

Example 1 – Create a calculated column that stores the count of unique leads.

CountDistinct(`Leads.Prospect Id`)

Example 2 – Calculates the percentage contribution of distinct Prospect IDs relative to the overall total across all partitions (Used in a % Grand Total scenario).

(Countdistinct(Leads.Prospect ID) / Sum(Countdistinct(Leads.Prospect ID), PartitionBy()))*100

% Grand Total Usecase

CountDistinctIf

The CountDistinctIf function allows you to count the distinct number of occurrences that meet a specific condition.

Example 1 – Create a calculated column that stores the count of distinct leads when the lead stage is ‘Prospect’.

CountDistinctIf(`Leads.Prospect Id`, `Leads.Lead Stage` = 'Prospect')

Example 2 – Counts distinct Prospect IDs where the Status is Converted, grouped by Owner.

CountDistinctIf(Lead.Prospect ID, Lead.Status='Converted', PartitionBy(Lead.Owner Id))

Max

The Max function allows you to calculate the maximum of numeric values within a given field. 

Example 1 – Create the calculated column which stores the maximum of the field mx_Custom_2.

Max(<fieldname>)

Max(`Leads.Custom 2`)

Example 2 – Returns the maximum summed Lead Score within each Owner’s partition.

Max(field, PartitionBy(...))

Max(Sum(`Leads.Lead Score`), PartitionBy(`Leads.Owner Auto ID`))

Min

The Min function allows you to calculate the minimum of numeric values within a given field. 

Example 1 – Create the calculated column which stores the minimum of the field mx_Custom_2.

Min(<fieldname>)

Min(`Leads.Custom 2`)

Example 2 – Returns the minimum summed Lead Score within each Owner’s partition.

Min(field, PartitionBy(...))

Min(Sum(`Leads.Lead Score`), PartitionBy(`Leads.Owner Auto ID`))

Avg

The Avg function allows you to calculate the average of numeric values within a given field. 

Example 1 – create the calculated column which stores the average of the field mx_Custom_2. 

Avg(<fieldname>)

Avg(`Leads.Custom 2`)

Example 2 – Returns the average summed Lead Score within each Owner’s partition.

Avg(field, PartitionBy(...))

Avg(Sum(`Leads.Lead Score`), PartitionBy(`Leads.Owner Auto ID`))

MaxIf

The MaxIf function allows you to calculate the maximum of numeric values within a given field along with some conditions.

Example 1 – Create the calculated column which stores the maximum of the field mx_Custom_2 when Stage is ‘Prospect’.

MaxIf(<fieldname>,<condition>)

MaxIf(`Leads.Custom 2`, `Leads.Lead Stage` = 'Prospect')

Example 2 – Returns the maximum summed Lead Score but only for rows where Lead Score is greater than 0, grouped by Owner.

MaxIf(field, condition, PartitionBy(...))

MaxIf(Sum(`Leads.Lead Score`) , `Leads.Lead Score` > 0, PartitionBy(`Leads.Owner Auto ID`)

MinIf

The MinIf function allows you to calculate the minimum of numeric values within a given field along with some conditions.

Example 1 – Create the calculated column which stores the minimum of the field mx_Custom_2 when Stage is ‘Prospect’.

MinIf(<fieldname>,<condition>)

MinIf(`Leads.Custom 2`, `Leads.Lead Stage` = 'Prospect')

Example 2 – Returns the minimum count of Lead Score only for rows where Lead Score is greater than 0, grouped by Owner.

MinIf(field, condition, PartitionBy(...))

MinIf(Count(`Leads.Lead Score`) , `Leads.Lead Score` > 0, PartitionBy(`Leads.Owner Auto ID`))

AvgIf

The AVGIF function allows you to calculate the average of numeric values within a given field along with some conditions.

Example 1 – Create the calculated column which stores the average of the field mx_Custom_2 when Stage is ‘Prospect’. 

AvgIf(<fieldname>,<condition>)

AvgIf(`Leads.Custom 2`, `Leads.Lead Stage` = 'Prospect')

Example 2 – Returns the average count of Lead Score only for rows where Lead Score is greater than 0, grouped by Owner.

AvgIf(field, condition, PartitionBy(...))

AvgIf(Count(`Leads.Lead Score`) , `Leads.Lead Score` > 0, PartitionBy(`Leads.Owner Auto ID`))

ArgMax

Returns the value of target_field for which selector_field is maximum.

For example, the expression below returns the Lead Source of the lead that has the most recent Updated On date.

ArgMax(target_field, selector_field)

ArgMax(Lead.Source, Lead.Updated On)

ArgMin

Returns the value of ‘target_field’ for which ‘selector_field’ is minimum.

For example, the expression below returns the Lead Source of the lead that has the earliest Updated On date.

ArgMin(target_field, selector_field)

ArgMin(Lead.Source, Lead.Updated On)

ArgMaxIf

Returns the value of ‘target_field’ for which ‘selector_field’ is maximum where condition holds.

For example, the expression below returns the Lead Source of the most recently updated lead, but only among leads where Status = Converted.

ArgMaxIf(target_field, selector_field, condition)

ArgMaxIf(Lead.Source, Lead.Updated On, Lead.Status = 'Converted')

ArgMinIf

Returns the value of ‘target_field’ for which ‘selector_field’ is minimum where condition holds.

For example, the expression below returns the Lead Source of the earliest created lead, but only among leads where Status = New.

ArgMinIf(target_field, selector_field, condition)

ArgMinIf(Lead.Source, Lead.Updated On, Lead.Status = 'New')

Any

Returns any arbitrary value of the field from a group.

For example, the expression below returns any one City value from the group.

Any(field)

Any(Lead.City)

AnyHeavy

Returns the most frequent value (>50%) using heavy-hitters algorithm.

For example, the expression below returns the most frequently occurring City, but only if it appears in more than 50% of the records.

AnyHeavy(field)

AnyHeavy(Lead.City)

AnyLast

Returns the last-seen value based on processing order.

For example, the expression below returns the last-seen Stage value based on the order in which records were processed.

AnyLast(field)

AnyLast(Lead.Stage)

 

9. Date Time Expressions

Function & Example Expressions
DurationAdd

The DurationAdd function allows you to add any duration to a particular date field.

Allowed Units – second, minute, hour, day, week, month, quarter, year

Returns – Added Duration (DateTime)

For example, you can create the calculated expression which counts the lead which came into the system 4 months ago and the current stage is not ‘Customer’.

DurationAdd(<date>,<value>,<Unit>)

CountIf(`Leads.Lead Stage` != 'Customer' and DurationAdd(`Leads.Created On`,4, 'MONTH') < CurrentDateTime)

DurationSubtract

The DurationSubtract function allows you to subtract any duration from a particular date field.

Allowed Units – second, minute, hour, day, week, month, quarter, year

Returned Value – Subtracted Duration (DateTime)

For example, you can create the calculated expression which counts the lead which came into the system 4 months ago and the current stage is not ‘Customer’.

DurationSubtract(<date>,<value>,<Unit>)

CountIf(`Leads.Lead Stage` != 'Customer' and `Lead.Created On` < DurationSubtract(CURRENTDATETIME, 4, 'MONTH'))

CurrentDateTime

The CurrentDateTime function returns the current date and time.

For example, you can create a calculated column that stores -4 months from date field mx_Custom_2.

CurrentDateTime

DurationSubtract(CurrentDateTime, 4, 'MONTH'))

ToHour

The ToHour function allows you to extract the hour component of any datetime(timestamp) field.

Returned Value: Hour Component (Number) eg: 23

For example, you can write a condition where you want to count the leads which came into the system at 11 PM.

ToHour(<date>)

CountIf(ToHour(`Leads.Created On`)='17:00')

ToYear

The ToYear function allows you to extract the year component of any datetime(timestamp) field.

Returned Value: Year Component (Number) eg: 2023

For example, you can write a condition where you want to check if the year component of the datetime field is equal to 2023.

ToYear(<date>)

ToYear(`Leads.Created On`)= 2023

ToYearWeek

The ToYearWeek function allows you to extract the week and year components of any datetime(timestamp) field.

Returned Value: Week and Year Component (1-53 Number) Eg: 202345 (45th Week of 2023)

For example, you can write a condition where you want to check if the week and year component of the datetime field is equal to the 45th Week of 2023.

ToYearWeek(<date>)

ToYearWeek(`Leads.Created On`)=47

ToMonthOfYear

The ToMonthOfYear function allows you to extract the month component of any datetime(timestamp) field.

Returned Value: Month of the Year (1-12 Number) eg: 1 (for January)

For example, you can write a condition where you want to check if the month component of the datetime field is equal to January.

ToMonthOfYear(<date>)

ToMonthOfYear(`Leads.Created On`)='0002-02-01'

ToDateOfYear

The ToDateOfYear function allows you to extract the date component of any datetime(timestamp) field.

Returned Value: Date of the Year (1-366 Number) eg: 32

For example, you can write a condition where you want to check if the date component of the datetime field is equal to 2nd Feb.

ToDateOfYear(<date>)

ToDateOfYear(`Leads.Created On`)='2023-02-02'

ToQuarterOfYear

The ToQuarterOfYear function allows you to extract the quarter component of any datetime(timestamp) field.

Returned Value: Quarter of the Year (1-4 Number) eg: 2

For example, you can write a condition where you want to check if the hour component of the datetime field is equal to 2nd Quarter.

ToQuarterOfYear(<date>)

ToQuarterOfYear(`Leads.Created On`)='Q2'

ToMonth

The ToMonth function allows you to extract the month and year components of any datetime(timestamp) field.

Returned Value: yyyy-mm-01 (String) eg: ‘2023-02-01’

For example, you can write a condition where you want to count the leads created in the month of February 2023.

ToMonth(<date>)

CountIf( ToMonth(`Leads.Created On`) = '2023-02-01' )

ToQuarter

The ToQuarter function allows you to extract the quarter and year components of any datetime(timestamp) field.

Returned Value: YYYY QX (String) eg: ‘2023 Q2’

For example, you can write a condition where you want to count the leads created in the 2nd Quarter of 2023.

​​​​​ToQuarter(<date>)

CountIf( ToQuarter('Leads.Created On') = '2023 Q2' )

ToDayOfWeek

The ToDayOfWeek function allows you to extract the day of the week component of any datetime(timestamp) field.

Returned Value: 1-7 (Number) Range: (1-7: Monday = 1, Tuesday = 2, …, Sunday = 7) eg: ‘6’ for Saturday

For example, you can write a condition where you want to count the leads created on Saturdays.

ToDayOfWeek(<date>)

CountIf( ToDayOfWeek(`Leads.Created On`) = 6 )

ToWeek

The ToWeek function allows you to extract the week and year components of any datetime(timestamp) field.

Returned Value: YYYYWW (Number) eg: 202347

For example, you can write a condition where you want to count the leads created on the 47th Week of 2023.

ToWeek(<date>)

CountIf( ToWeek(`Leads.Created On`) = 202347 )

DateUnitDiff

Returns the count of the specified time unit boundaries crossed between the start and end dates. This can be used to create TAT between 2 date fields.

Returned Value: (Number) eg: 43

DateUnitDiff(<start date>, <end date>, <interval>)

Accepted Intervals – 

  • SECOND
  • MINUTE
  • HOUR
  • DAY
  • WEEK
  • MONTH
  • QUARTER
  • YEAR


For example, consider your data source has 2 fields – CreatedOn and PaymentDate which capture the lead created and the payment date of the lead. To create a TAT report (in days) on the PaymentDate from the lead created, we can use the expression below –
Avg(DateUnitDiff(`Leads.Created On`, `Leads.Payment Date`, 'DAY'))

The above expression will calculate the TAT for each grouping on average. For cases when there is no value in the date field, the expression builder will take the value of 01-01-1925. To exclude cases where there is no payment done, use the syntax below-

AvgIf(DateUnitDiff(`Leads.Created On`, `Leads.Payment Date`, 'DAY'),ToYear(`Leads.Payment Date`) > 1925)

ToDate

Returns the date component from a datetime field.

Returned Value: (String) eg: 2023-10-03

For example, you can write a condition where you want to count the leads created on 2023-10-03

ToDate(<date>)

CountIf(ToDate(`Leads.Created on`) = '2023-10-03')

ToDayOfTheMonth

Extracts day of month (1–31).

For example, the expression below returns the day of the month (1–31) from the Created On date of the lead.

ToDayOfTheMonth(date)

ToDayOfTheMonth(Lead.Created On)

ToDayOfYear

Extracts day number in year (1–366).

For example, the expression below returns the day number in the year (1–366) extracted from the Audit Event Time field.

ToDayOfYear(date)

ToDayOfYear(Audit.Event Time)

 

10. String and Column Functions

Position

Returns 1-based index of substring; 0 if not found.

For example, the expression below Checks whether the substring “Pro” exists in the Lead Stage field. If found (i.e., position > 0), it returns “This is Prospect”; otherwise, it returns “This is not Prospect”.

Position(string_field, substring)

If(Position(`Leads.Lead Stage`,'Pro')>0  , 'This is Prospect','This is not Prospect')

Concat

Concatenates multiple fields into a single string.

For example, the expression below combines the First Name and Last Name fields into a single full name string, inserting a space between them.

Concat(field1, field2, ...)

Concat(Lead.FirstName, ' ', Lead.LastName)

JSONExtractString

Extracts string value from a JSON object by key.

For example, the expression below extracts the “city” value from the JSON object stored in the AdditionalInfo field.

JSONExtractString(json, key)

JSONExtractString(Lead.AdditionalInfo, 'city')

RegexpExtract

Extracts regex capture group by index.

For example, the expression below extracts the portion of the email before the ‘@’ symbol using a regular expression, and returns the first captured group (e.g., the username part of the email).

RegexpExtract(str, pattern, index)

RegexpExtract(Lead.Email, '([^@]+)@', 1)

 

11. Window Functions

Note: Expression fields should be included in row grouping. Owner Auto ID should be preferred for partitioning.

Lag

Returns value from a previous row in partition.

For example, the following expression returns the Lead Stage from the previous row within each Owner’s partition, based on the stage’s ascending order.

Lag(field, offset, PartitionBy(...), OrderBy(...))

Lag(Leads.Lead Stage , 1 , PartitionBy(Leads.Owner Auto ID), OrderBy(Leads.Lead Stage ASC)) 

Lead

Returns value from a following row in partition.

For example, the following expression returns the Prospect Creation Date from the next row within each Owner’s partition, ordered by creation date in ascending order.

Lead(field, offset, PartitionBy(...), OrderBy(...))

Lead(Leads.Prospect Creation Date , 1 , PartitionBy(Leads.Owner Auto ID), OrderBy(Leads.Prospect Creation Date ASC))

RowNumber

Assigns sequential row number within partition.

For example, the follwing expression assigns a sequential row number to each record within the Owner partition, ordered by Lead Stage.

RowNumber(PartitionBy(...), OrderBy(...))

RowNumber(PartitionBy(`Leads.Owner Auto ID`), OrderBy(`Leads.Lead Stage` ASC))

FirstValue

Returns first value in ordered partition.

For example, the follwing expression returns the first Lead Stage value in each Owner’s partition, based on ascending stage order.

FirstValue(field, PartitionBy(...), OrderBy(...))

FirstValue(Leads.Lead Stage , PartitionBy(Leads.Owner Auto ID), OrderBy(Leads.Lead Stage ASC)) 

LastValue

Returns last value in ordered partition.

For example, the following expression returns the last Lead Stage value in each Owner’s partition, based on ascending stage order.

LastValue(field, PartitionBy(...), OrderBy(...))

LastValue(Leads.Lead Stage , PartitionBy(Leads.Owner Auto ID), OrderBy(Leads.Lead Stage ASC)) 

 

12. Custom Dimensions

Function & Example Expressions
If

Returns a string based on a condition. The condition can be nested.

Returned Value: (String) e.g., ‘Hot’, ‘Medium’, ‘Warm’, ‘Cold’

For example, let’s assume we want to classify leads based on their ProspectStage into ‘Hot’, ‘Medium’, ‘Warm’, or ‘Cold’ categories.

If(<condition>, <value_if_true>, <value_if_false>)

If (`Leads.Lead Stage`= 'Customer', 'Hot', If (`Leads.Lead Stage`= 'Prospect', 'Medium', 'Cold' ) )

 

Any Questions?

If you have any questions related to Expression Builder that weren’t answered here, please leave comments below. We’ll be happy to help!

Subscribe
Notify of
guest
16 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Nitin Kumar Sankhla
Nitin Kumar Sankhla
17 days ago

Hi Team,
I am trying to build a report in SIERA (using the “All Activities” data source) and want to use a custom field for activities in the custom value expression. Specifically:

  • I use an activity type (code 217) and have a custom dropdown field (mx_Custom_1, display name “Reason”).
  • I want to count how many activities of type 217 have Reason = a certain dropdown value.
  • My expression is: Attached

Could you please confirm:

  1. Does SIERA support custom activity‑fields (fields like mx_Custom_1) in report expressions by default?
  2. If yes — what’s the correct syntax (field reference) to use them?
  3. If not — can you enable or provide a custom template/data‑source that includes custom activity fields so I can report based on them?

Thanks for your help.

mx_custom_1
Ajay
Ajay
2 months ago

I’m not able to create custom expression for Rows. Custom expression is not showing.

Yash Singhal
Yash Singhal
5 months ago

I need Help, I am creating a report, In rows, I have partner names, in values, I have Number of leads from respective partners are coming. Now, I need one more column, I which I want to show % of leads from respective partners. How can I get sum of all the leads from all the partners.
1st column I am getting correctly, but for second one, I don’t know How to get the total opportunity value from summary.

Screenshot-2025-06-26-181305
Ishan
Ishan
6 months ago

Hey, is there a ‘like’ function in SIERRA? Like how it works in SQL
Eg: first_name like ‘%raj%’ so it will pull all first_names that have raj

Ishan
Ishan
7 months ago

Hi, I’m trying to figure out how if statements work in SIERRA?
Basically I have two columns connected disposition and not connected disposition and I want to combine both so I want to write an IF statement – if connected is null then not connected else connected – basically an ifnull. But it does not seem to work.
Ref: If(Activity.mx_Custom_1 = Null, Activity.mx_Custom_2, Activity.mx_Custom_1)

ajay.gupta1
ajay.gupta1
11 months ago

If I want to count on basis of data contains specific character, then how to use it SIERA.

For Example: Column1 has following data

A123
12C4
H543
8890
GHS0
9430

I want to count if data contains “4″ then output will be 3 (i.e. 12C4, H543, 9430)
How to do this in SIERA

ajay.gupta1
ajay.gupta1
Reply to  Zaid Assadi
11 months ago

Is there any function like starts with specific character

For Example: Column1 has following data
A123
12C4
H543
8890
A783
GHS0
9430

I want count of output where data startswith “A” i.e. A123, A783.

Last edited 11 months ago by ajay.gupta1
ajay.gupta1
ajay.gupta1
Reply to  Zaid Assadi
11 months ago

Is there any alternative of this functions so we can use it to create Dashboards