Búsquedas recientes
No hay búsquedas recientes

Patrick Crane
Incorporación 13 may 2021
·
Última actividad 27 oct 2021
Seguimientos
0
Seguidores
0
Actividad total
14
Votos
3
Suscripciones
5
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Patrick Crane
Patrick Crane hizo un comentario,
We are working on making Explore dashboards embeddable. This is to empower enterprise customers to combine information from multiple sources and to consume dashboards outside of Explore.
We aim at shipping it in the first half of 2021.
Has there been any progress on the work to embed explore dashboards? Maybe an ETA to activation?
While I agree with all the requests for APIs, embeddable dashboards would be a perfect solution for one of my clients.
Ver comentario · Publicado 18 jun 2021 · Patrick Crane
0
Seguidores
2
Votos
0
Comentarios
Patrick Crane hizo un comentario,
Thanks @...! That's a great point. I don't recall being able to see or interact with the tags on the typeform/ zapier side, but now that you mention it, all fields I build on ZD get custom tags with a "header" (for lack of a better term) that describes the data set they are related to. Like on a drop down for color choices the tags would be "customer_choice_data_set_1_blue" for the selection "Blue" on that field (and so on...). The header is usually the title of that field.
This could be where my problem is coming from ... when I make the drop down and enter the choices the ZD "automagically produced" tags are simply "blue". Maybe because of my custom tags zapier can't connect the simple typeform tag with the ZD field.
Hmmm.... I sense a test coming on. Thanks for the idea Chris!
Ver comentario · Publicado 06 may 2021 · Patrick Crane
0
Seguidores
0
Votos
0
Comentarios
Patrick Crane hizo un comentario,
Nope you hit it on the head. I was pretty sure that would be the answer, but it never hurts to ask.
As for whether to leave this post open or not, I'm good, but if you think it would benefit others, feel free to leave it open.
Thanks for the help!
Ver comentario · Publicado 29 abr 2021 · Patrick Crane
0
Seguidores
0
Votos
0
Comentarios
Patrick Crane hizo un comentario,
Thanks Brett, I will.
For the record, I did find a solution/ work around. If all the ZD ticket fields in question are single line text boxes, they accept the output from the TF/ zapier.
I'm not sure if that's by design or not, but at least it works in my use case.
Follow on question; if I change a field in an existing ticket (example from a dropdown to a text field) AND the data from said field is currently being used as a KPI on a dashboard in Explore, will I need to change the query or will the data merge automagically?
Ver comentario · Publicado 29 abr 2021 · Patrick Crane
0
Seguidores
0
Votos
0
Comentarios
Patrick Crane creó una publicación,
Hi!
One of my brands is using a website hosted typeform (TF) to gather customer info and some statistics. The TF uses a combination of text, multi line text, dropdowns (with conditionals), and multiple choice fields.
Zapier makes the connection and creates the ticket (ZD Support). The Zap works fine. It creates a ticket for each "submission". But I can only get the data from the text and multi-line boxes to come through. The dropdowns, conditionals, and multiple choice fields refuse to come through.
The customer needs all data from all fields to import to the ticket.
I only found one other question related to my use case in the community. The answer there didn't help, so here I am.
I have free reign to change the TF, Zap, and/ or ZD ticket to make this work. Any thoughts?
Publicado 27 abr 2021 · Patrick Crane
0
Seguidores
3
Votos
7
Comentarios
Patrick Crane hizo un comentario,
This looks like a pretty old thread, but I'll give it a shot...
The previous administrator/ creator made a custom field for tracking customer reported income (for statistical purposes and not a required field if the customer wanted to remain private).
However they built the field as text meaning I can't use it as a metric. (Or, at least, I can't figure out how to use it.)
Is there any way to wrangle the "text" (which is actually all numbers) into a format that I could use it as a metric? I want to lay out an income trend line over an existing chart.
Further, am I correct that to convert this to a numerical field going forward, I'll have to make a new field, and replace the old one on the ticket?
Edit to add: if I do replace this text field with a numerical field AND there is some way to use the text field data as a metric, in the future, would I be able to merge the two data sets to one unified metric?
Ver comentario · Publicado 16 feb 2021 · Patrick Crane
0
Seguidores
0
Votos
0
Comentarios