Pesquisas recentes


Sem pesquisas recentes

Denis Iliev's Avatar

Denis Iliev

Entrou em 05 de jan. de 2024

·

Última atividade em 02 de ago. de 2024

Seguindo

0

Seguidores

0

Atividade total

6

Votos

1

Assinaturas

2

VISÃO GERAL DA ATIVIDADE

Atividade mais recente por Denis Iliev

Denis Iliev comentou,

ComentárioMetrics, attributes, and filters

I need assistance with creating report:

A report that shows users who have provided an email address for feedback and have not had contact with technical support in the past year. Here’s what I’ve tried so far:

I created a date filter to include tickets from the past year.

I attempted to create a metric with a standard calculation using the following formula:

sql

IF (DATE([Ticket created - Year]) = (DATE("today") - 1 year)) THEN [Requester email] ENDIF

However, I keep encountering a syntax error. I then tried this formula:

sql

IF [ticket created - Year] <= today() - 364 THEN [requester email] ENDIF

But I received this error:

“You can’t use [Ticket created - Year] as a number and TODAY() - 364 as text. Use only numbers or only text. If necessary, use the NUMBER function to transform text to numbers.”

Any help or suggestions would be greatly appreciated. Thank you in advance!

Exibir comentário · Publicado 02 de ago. de 2024 · Denis Iliev

0

Seguidores

0

Votos

0

Comentários


Denis Iliev comentou,

ComentárioEnd users and organizations

Thank you for your response. I would like to inquire if there is a method to create a custom field that functions similarly to the system-provided "Email" field, specifically intended for feedback purposes. The objective is to restrict entries within this custom field to be exclusively in the format of an email address (e.g., example@site.com) and disallow any other text input.

Exibir comentário · Publicado 09 de jan. de 2024 · Denis Iliev

0

Seguidores

0

Votos

0

Comentários


Denis Iliev comentou,

ComentárioEnd users and organizations

Hello! We are currently using a custom field categorized as "text" instead of "email" within the user data input section. However, we have noticed that this element doesn’t provide clarity to our users regarding its purpose. Instead, it might confuse them about the requirements for entering an email address, which is intended for feedback purposes.

We would like to edit or add clarification to this built-in "Email" field to make its purpose clearer for our users. Is it possible to perform this edit? We aim to introduce explanatory text alongside the field, guiding users on what is expected when filling in their email addresses.

Exibir comentário · Editado 05 de jan. de 2024 · Denis Iliev

0

Seguidores

0

Votos

0

Comentários