Elevate Workfront Reporting with Advanced Text Mode

Take your Workfront reporting to the next level with advanced text mode techniques. In this session, Nathan Johnson from Adobe will show you how to create more efficient, dynamic, and user-friendly reports by:

  • Merging fields for cleaner reports Combine multiple data points into a single column to reduce clutter, improve readability, and highlight key information.
  • Using custom calculations with value-expressions Apply real-time calculations and conditional logic to display custom summaries, metrics, or status messages, enhancing report insights without altering underlying data.
  • Creating custom prompts for flexible filtering Add dynamic filters to reports, enabling end-users to adjust views without editing the report, and making reports more interactive and user-friendly.
  • Learn to create polished, functional reports that provide meaningful insights instantly.
Transcript

Hi, I’m Nathan Johnson. I’m a Technical Support Engineer at Adobe. Today I’m going to help you elevate your Workfront reporting by using Advanced Text Mode. On the next slide, I’m going to introduce myself a little bit more, and then I’m going to segue into our theme. I want you to think about your reports as more than just data, but as a way for you to leave a record with your voice. We’re going to do that by looking at Mergle. We’re going to look at the emerging columns. We’re also going to take a look at value expressions. Then I’m going to teach you how to create custom prompts.

I’ll go over takeaways, and then at the end I’ll answer your questions.

I’ve been a Technical Support Engineer at Adobe for the last three years, and I generally work with APIs, Fusion, and Text Mode. I might have a few cases with you open right now, so shout out in the chat if I do.

Outside of work, I really like to build board games, design board games. I play with my kids a lot. I’m a scout leader, and I like to go on adventures. I go swimming, I go hiking, and most of all, I really like visiting national parks. I live really close to a bunch. One of those is Mesa Verde National Park in the Four Corners area.

I’m going to be segueing into a theme that ties into Mesa Verde National Park about leaving a record. For a long time, we found all these cliff dwellings in that area. That’s why we built the national park around them. For a long time, we had no idea why these cliff dwellings were built and what happened to the people.

Recently, we’ve been listening to the voices of the descendants of those people, and we have a better understanding. I’m going to tie that into the records that you build in Workfront in reporting and how you can use advanced text mode to tie your voice into the record that you’re leaving. If you want to get to know me on an individual level, go ahead and scan the QR code there. I am happy to make friends and expand my connection through LinkedIn.

Why does advanced text mode matter? Our default Workfront reporting tool is extremely helpful, but as you might know, it lags a little bit in the way that it presents data. It doesn’t look quite as nice as some of our competitors, and that’s okay because Workfront isn’t a reporting tool by default. That is just one thing that we add into Workfront.

But with text mode, you can actually create a lot of flexibility. You can decrease clutter with merging columns. You can create real-time insights and custom interactivity with custom prompts.

Okay, so let’s take a look at an example in Workfront. One thing that I want to cover is how data without context is dangerous. Within Workfront, you can create a report on just about any object. You can create a report on projects, on tasks, on proof approvals, and the default reporting tool shares enough information to get you started, and you can add a few columns through the UI. But if you look at this example here, this is a project report where someone added some additional date columns. So we have projected start date, projected completion date, planned start, planned completion. If someone was to ask you when these projects are due and how late they might be or how early they might be, just looking at that report can cause a lot of confusion. You’re going to have to do some math in your head, and you might come to the wrong conclusion, especially if you’re looking at multiple projects at the same time. So using value expressions, we can create columns that will, in real time, dynamically update how ahead or how behind you are on your projects. In the same way, one thing that really struck me as I was touring the Cliff Palace in Mesa Verde National Park, for a long time, we didn’t really understand how the people who lived there, how they lived and where they went and how they died. For a long time, we thought they just were wiped out, maybe by war, and they disappeared. But now, by listening to the voice of the people who are their descendants, who actually still live in the area, they just moved to a different area, we understand what their homes look like, how they live their lives, and why they may have moved. As I go about this presentation, I’m going to be sharing a lot of Text Mode snippets. You do not have to take pictures. You do not have to memorize anything. I am sharing all of the examples in the chat, and you can go ahead and start perusing those and ask me any questions at the end.

So let’s start with merging columns.

Through merging columns, we can get rid of clutter, we can make the report easier to scan, we can reduce horizontal scrolling. I was actually just recently working with a customer who asked me to troubleshoot a specific column, and it was the 30th column, so I had to scroll all the way over every single time that we needed to make an edit or change that. If they had included less columns or merged a few columns, that would have been much easier to handle.

This also gives you a lot of context clues as to what the report is about, and it can be a way for you to tell people how the data should be interpreted.

So in this example here, this is a basic project report. These are the three default columns. We have the report name, or the project name, the description, and the owner name.

Through merging columns, we can combine all of that into a single column called project information. You can choose different fonts, you can bold, and you can put things where you need them to be seen.

All right, so here are some of the snippets that I used to create that last screenshot. So these are the text mode snippets that you’re going to use to merge your columns together. So that first one, the one on the top left, that’s the most important one. So that is value format equals HTML. So that’s telling us that we’re going to be using some HTML tags, and it tells the system how to interpret what we’re putting in. Width equals one, that’s just a default thing. I’m going to explain that in just a moment. And share call equals true is the most important line. That is what combines that column with the one to its right. So every time that you’re merging columns, you’re going to create your columns, then you’re going to put in some blank columns, and that share call equals true is going to merge every column to the one on its right, and it’s just going to bring them over one at a time.

Some of these snippets are a little bit more advanced, and I’ll talk about those as I put them in.

So one thing that really stood out to me when I was touring Mesa Verde National Park is the fact that what you see when you walk through the cliff palace or these different cliff dwellings is not what the people who lived there a thousand years ago would have seen. So they would have had a lot more context on their buildings, and I’ll explain that. So what I mean by that is they would have had plaster on their walls.

They would have had hangings throughout, and if you look at that pottery there, that pottery tells a story. They would have actually had that on their buildings as well. They would have had stories that explain their religion, explain their family history, and as you walk through, you would have been able to tell exactly who these people were and what their story was. In the same way, when we look at these columns, we want you to see what the story is behind the data.

So here’s an example of how to merge columns. I’m going to walk you through it just because I’ve seen a lot of people get confused. So here’s the documentation. I’m sharing that in the chat. And the most important line for that documentation, the most important snippet, is that one right there, those four lines. If you take those and you create blank columns between the columns that you want to merge. So this is how you get started. If you ever run into problems, if you ever get errors while you’re building out these merged columns, start over from the beginning and just start this way, as I’m doing here. So in that blank column, I’m putting in those four lines and the share call equals true is what merges it with the one on the right. Then I’m going to move over to the next one and I’m adding just share call equals true this time. So the description column is now going to be merged with the owner column. And then take those four lines, I’m going to add it to the blank one to the left and it’s going to merge it with the one on the right. And then I’m going to add share call equals true on the furthest one on the left. And now we have them all merged together. This is pretty good. This is good enough for a lot of like if you’re just building a quick report and you want people to see everything merged in one column, that does the trick.

Now, if you want to make this a little bit more advanced, right, if you want to add in bolding, you want to add in horizontal line breaks. This is what you what you’re going to need to do. So I’m going to start over and put those three columns back and I’m going to put in some blank columns. And what we’re going to start with, we’re going to start with the owner because we’re going to start on the right and we’re going to move left. Right. So in that blank column, instead of just putting a line break, which is that br, that’s the HTML tag for line break. I’m going to be adding in value equals and I’m actually going to put some text in there. So this is not a value expression. A lot of people think this is this is part of our text mode value expressions. This is actually just an HTML tag. That’s why we’re using value format equals HTML. So we know how to interpret the tags that we put in here. And I’m putting in br for line break, hr for horizontal line.

And those are HTML elements, so they don’t need a closing tag. The b with the with the closing b. Those are HTML tags and that bolds the owner. Then I put share call equals true and brought them together. I’m going to go ahead and add in description. And this time I’m going to actually change the font. Now, you can use just about any HTML element. Some of them won’t work. That’s just something that there’s some limitations there. I’m going to share as much as I know that does work with you in the chat. You know, this isn’t built just for HTML. This is just something that that you can do in text mode. So I’m going to share all the examples that I know work. It doesn’t take long to kind of learn about HTML tags and elements. So I recommend going to like w3schools.com and and just doing some basic couple hours worth of basic HTML learning. And you’ll you’ll know enough to just start plugging and playing here.

So at the very end, we have this column at the very beginning.

It is a blank column, but we’re putting in display name. So we want to name the merged column altogether. And in this case, we’re going to call this one project details. And then we’re going to add in our normal.

Name in bold and our share call equals true and all of that. One thing that’s interesting about merging these columns together when the report loads, it actually sees all of these as individual columns.

The share call equals true allows it to be displayed in one single column format, but the column numbers are still important. So just keep that in mind when you’re building out more columns, you could run into errors. OK, so skill two, we’re going to talk about custom calculations without expressions.

You can combine this with those merging of columns. So go ahead and try that out if you want to. But custom calculations without expressions. This is a way for you to dynamically change data in your report without actually changing the real underlying data.

So this is similar to custom fields and in custom forms. However, in this case, you don’t have to recalculate things often. In this case, you build it into your report. Every time you load that report, it’ll recalculate itself. You can use this to add explanatory text and emojis in these examples right here. We see the status column in the schedule status column. The status column we have complete with an emoji there and then we have unknown. I’m going to talk more about that schedule status. This is where I was talking about earlier. You can actually say that this project is behind by a certain number of days or ahead by a certain number of days. You don’t need to look at dates and you get that information right away.

So here’s the text mode behind both of those. So these are value expressions. I’m going to share more examples in the chat. But this first one here, I’ll explain it as I as I add it to the report itself. But it’s just a simple if statement. It looks at the status of the project and then it puts in a few things here. Change that to meet your needs or you can just use those elements and build something else entirely different. This bottom one here, a few things I just want to point out, it’s kind of it’s kind of big and unwieldy. I’m going to show you how to add it to the report in just a moment. But the first thing.

We have multiple statements here, so we have if and everything is within that if statement. And we’re saying if the actual completion date is blank. Don’t show anything. So it’s not even complete yet. Don’t show anything. Otherwise, we’re going to concatenate some some verbiage with the date diff. So that’s taking a difference between two dates of planned completion date and actual completion date. If it’s over zero or say ahead by if it’s under zero behind by and we concatenate that value with the actual date diff. We take the absolute value of that because we don’t want to show like ahead by a day or behind by negative a day. Right. We want to show just a single value and then we concatenate days at the very end. So let me show you what that looks like. This is our documentation that that shows you all of our value expressions. So there’s like 100 different expressions that are all supported. Look through that for the different criteria that you need to meet to make those work. But what I’m going to do here is I’m going to first add that that very first one that I showed you. I’m just going to do it real quick. It is pretty self-explanatory. We look at the the status if the status is equal to this. Add in this emoji and this name. I do like to show you how I start. So I like to start with the UI. I grab the field in question. So that’s the status field. And then I’m going to change that from value field to value expression. And I’m going to change the value formats to HTML only because when you start dealing with a lot of text mode, HTML seems to work best. You can keep different value formats and that sometimes is needed. If the the output of your value expression is going to be a date or something like that, you keep it at date or at date time.

But I like to just change them to HTML by default. If that doesn’t work, then I go in and mess around with those value formats. So in this case, we have unknown. And right there, do you see how percent complete is one hundred percent? That tells us a lot of information that says the the status is not set to complete. It’s unknown. And yet we’re at one hundred percent complete. So we need to go in and figure out why.

This last one that I’m going to add, this is the one that I showed you with the with a ton of text mode. This is the schedule status. Going in here and I’m starting with the planned completion date because I want to I want to start with something we know right from the UI. I don’t want to build everything from scratch. We’re going to change the display name. So that’s the name that’s in the column header. And I can put any value in here. Spaces are OK. I’m going to put schedule status and then I’m changing value field value expression. And this is where I’m dropping in that whole line. Some of you who are who are really advanced might already foresee something that might go wrong here. I just want to show you how I fix it. So we hit done. Save and close.

And as you look, it worked. But we have too much precision in the date. Right. So we have four hundred fifty eight point and then a bunch of numbers after the decimal. We want to change the precision. So let’s go back to edit text mode. And what we want to do is the actual date. That’s that’s that part that’s wrapped in absolute value. And then it’s date diff. We need around that. So showing you how I find that documentation. We’re going to round the value that we output already. That’s the number. And then the precision. We want to put something like two. So that way we have only two digits after the decimal. And I just show you how I add that there. Put a comma and then we put two. Just highlighting that to make sure you see it. And then we’re done. And that should show up just right.

OK. Awesome. Next up, custom prompts for flexible filtering. Prompts are perfect for project managers who want to switch between different views. Members of a team who have different criteria when they look at the same report.

And it also helps with faster loading times because you don’t have to load all those different filters at one time. You could put those into the into the report itself as different or statements. But then the report actually has to load like process all of those at the same time. So if you just leave it to the prompts and leave it to the viewer of the reports to change, then it makes it much easier.

My favorite part of Mesa Verde National Park was actually the kivas here that you can see. You can see my kids looking down into the kiva wondering what they what they were built for.

You can see that there’s a fireplace in the center. But other than that, there’s not a lot of context clues. For a long time, we thought that these kivas were built for all sorts of different things, for war rooms, for religious ceremonies. Turns out that we’re right about all of them. Kivas, just like reports with prompts on them, can be used for anything.

These were used. These are the center of society for the ancient prevalence. So they were used for family gatherings. They were used for war rooms. They were used for religious ceremonies. And in the same way, if you create a report for projects in general and then add a lot of prompts to it, that one report can be used by everyone on your team for just about everything they need to know about projects.

So I’m not going to go into the basic UI functionality. You probably should know that. Right. This is advanced text mode. What we’re going to jump to is creating a custom text mode prompt.

And to demonstrate this, I just want to share a quick example of how you would use one of these prompts. So in the example on the left. So that’s the UI one. That is just a basic filter that you would pick through the UI showing any project where the owner’s home team idea is equal to. And you’re not going to decide that. You’re going to let the person who opens the report decide that. Right. But what if you want to do something a little more complex? What if you want to show any project where the owner is a member of a team? And that’s not something that you can actually grab in the UI because the home team idea is a one to one relationship. So now we’re dealing with the actual tables right in our API and our tables have references that allow you to go from project to the owner, the user table, and then look at that home team idea. So that’s one to one relationship. But if you’re looking at teams, that’s a one to many relationship. They could be on many teams. We want to see if they are on one of these teams, even if it’s not their home team. That’s where we need to bring in exist filters. Those are complex. They’re kind of hard to build. I’m sharing a ton of examples. I built a bunch of exist filter training internally for my team. So I’m sharing some slides from those kinds of trainings in our chat. You can plug and play those in your reports. Use them. If you want. You can ask me directly how how these work. They’re kind of like joins in sequel.

But that’s a little too much for this training to go over. But once you build them, you may realize that you need to customize that a little bit more. Right. You build an exist filter. It’s hard to build. It’s static. People can’t go in and change them because they don’t understand how to build a different exist filter. So what you can do is you can add it to these prompts and you can have it run a different exist filter based on choices that people select as they open their reports.

This is super easy because it gets around a few complexities with exist filters. If you use more than five or six exist filters in a single report, our our reporting engine actually can’t handle that. It will usually error out. You kind of blow up so you can put more than six. You can put 10, 20, 30 options and it will run one exist filter based on each of those options that you choose. So in our documentation here for adding a prompt to report, we have a section for adding custom prompts to report. Check that out. There’s an example there that you can just plug and play and it will be really helpful for you to learn. I’m going to show you real quick how to create a quick prompt in case you need a refresher. And then I’m going to take it over to an exist statement in our filter. I’m going to show you then how to format that to prepare it for custom prompt.

So in our home team, we’re going to put in the ID. One of the things that’s a downside to regular prompts that you build in the UI is that users have to be able to understand how to create a filter. Some of our end users don’t really understand that. So you have to say equals or less than or use those options. Then they have to put in the ID and they might not know that or they might not know what home team to put in.

So what we’re going to do is we’re going to go into this filter. We’re going to build out the advanced text mode filter that I was talking about before. So this is the exist statement where we use user as the linking object. So this is the join that I was talking about.

And this is taking us to any project where the owner is on the creative team.

And we didn’t get a result there. That’s all right. So what we’re going to do is we’re now going to take that filter and we’re going to edit it so that we can put it in as a custom prompt. So each line of text mode needs to be brought onto the same line. And instead of a line break between them, we’re putting an ampersand. That’s all we need to do. You can take as many lines of text mode as you want and put it in as a custom prompt. I haven’t ran into any issues with putting in multiple exist statements or things like that. Though you could still run into problems with multiple exist statements. Just because, as I mentioned earlier, if you have a lot of those, those are pretty intensive for our system to process. So you could run into errors. So you could run into that here. But if you’re putting one in for each option, it will process just one at a time.

Okay. And I’m just switching out the option there. So what’s cool about custom prompt is you choose the field name, you choose the options. And when you run it, as I’m showing here, all people have to do is just choose the option and it runs the report. They have no idea how complex the filter behind it was. And there we go.

All right.

Number one thing I hope you take away is that a good report is a record, but a great report is a record with your voice. Where you leave guidance, explanatory text, you guide people through the columns, and you allow them choices so that they can make the report what they want. And I’m ready to answer your questions.

Nathan, so I bet the entire audience was trying to break the internet scrambling to copy and paste all of your text move tips in real time. So I just, this is what’s in my imagination.

All of your examples show the benefit of customizing that report formatting to communicate powerful messages. So the first thing I want to ask you and talk about is how important is considering storytelling when you are building reports? Thanks, Cynthia. Pleasure to be here.

Yeah, so when it comes to storytelling and building reports, I come from it from a kind of interesting perspective because I’m a technical support engineer. Right. I’m not generally building those reports for people like many of our customers are doing, our admins. However, I am on the side of it where I have to fix things for people and I have no idea what business they’re in. You know, they could be in healthcare or banking or something like that. So when they show me a report, if it doesn’t tell a good story, I’m kind of lost. I have no idea what they’re trying to do, what they’re trying to accomplish and what story they want to tell. So if they are already telling that story, it gets me right in there and I can fix stuff right away. So it’s extremely important. Love that. So before we really get into the questions and there’s some great questions from the chat, let’s address the rumor mill. So, you know, is text mode going away? I don’t think it is. No, it isn’t. So I just want to throw that out there. Text mode’s not going away.

Like just be like everything that we talked about. I just wanted to throw that out there. Some very smart people are trying to build something so that we don’t have to use text mode, but it’s going to be around for a while. Yeah, definitely. So speaking of that, so when we talk about like text mode and your role, like how do you decide, when did you decide, how did you decide to go all in with learning text mode, using text mode instead of like kind of focusing on those out of the box type report? Yeah. So my story is a little unique for technical support engineers.

I joined Adobe right out of college. I mean, I went back to college, so I was in a training role before this. So came into Adobe and in college I learned a ton about information systems. I really like SQL. I like building databases, that kind of stuff. So I came in and my manager actually worked in consulting before his role and he kind of saw what I liked and he just put me straight into reporting. And immediately I just kind of took off. I want to learn everything about it. I learned it before I learned Workfront really. So I was more competent in the reporting area than I was in just basic projects and tasks. So yeah, I just kind of jumped in. There’s an advanced reporting guide that you can find online that really helped me. I kind of read through that my first few months and then just kind of kept going. So I love that. And I love that you learned that first. That’s amazing. It’s fun. So speaking of learning, someone asked, you mentioned the W3 website is a place to learn HTML tags.

And I know you talked about your background, but do you have any other recommendations? Yeah, so it’s kind of hard to remember all the different places. I think Code Academy is one.

I did pick that up in courses in school. So basically any website design will kind of get you there too. So if you go online, I know there’s a lot of free courses that you can find online. You can even take, I think Harvard puts out one where it’s like website design for free. It’s pretty cool. So like any basic website design, you’ll learn enough to help you in text mode. I love that. So this one, I know you get a lot. And so I’m going to word it in a way like when you’re talking to customers, because I know like I heard it too. I said it too. Like we love text mode and it’s great for sort of cracking the code on how to present your story. However, sometimes it renders your report, let’s just say not as pretty. How about that? What are your recommendations, your thoughts, like how to get that prettier graphing, charting capabilities or like what are your thoughts on that? So the first thing I would worry about is if you’re using text mode in your groupings, it’s probably going to break your charts and the summary page.

So to get around that, though, you can still use your text mode skills. You can go create custom calculated fields and then you can pull those in the UI. You can use those. Actually, I think that’s one of my favorite techniques to use is put a lot of it in your forms. That way you don’t have to do the text mode in the report when you’re doing charts and things like that. You still get that really cool data with the prettiness of it. That’s that’s the hard part, right? Text mode isn’t necessarily built to be like Tableau or all these other like Power BI, right? Sometimes it is best to just export everything and go do that if you don’t want it really pretty. But text mode can take you most of the way there. It’s pretty awesome. I love it. So get ready for your technical questions because here they come. All right. So first one, can we include negative numbers in an expression? I can just like there was an example, but I’m gonna let you just talk through it. Yeah, yeah, yeah. Negative numbers. Totally fine.

I think in the example, we had negative numbers and we wanted to make sure that it looked positive just because the explanatory text was adding that negative, right? It was behind by or ahead by. So we used absolute value to bring that into a positive. But you can use negative numbers as much as you want. It’ll handle it just fine. I love that. Yeah.

So here’s another one. OK. If a project was marked as complete, then reopen and the field actual complete day would have a value from the first time the project was marked complete. How do you validate that you show that correct data? Oh, so reopened. And then if we’re going to close it again, that changes.

Yeah. So that’s so.

Personally, I’d probably use a calculated field to capture that just because as long as you’re not recalculating the expression, it’ll hold onto that value. So you have it calculated the first time and then hopefully you can keep keep that from recalculating. But that is kind of hard because a lot of our fields do only hold one value. So you can’t you can’t bypass that. So a calculated field will help and you can hold on to that value and make sure it doesn’t. You can actually add some statements in there so it doesn’t recalculate again, even if you do mess up. So, you know, if it’s not blank, take that value. Otherwise, don’t don’t do it again. So so it won’t happen again if you recalculate expressions. So there’s a way around that. I love that. So we’re going to pivot just for a second. But there’ll be more questions about, I’m sure, technical stuff.

We talked about this before. Can you use different text editors such as notepad plus or built in or. Yeah. What do you use? Yeah. So for our position as technical support engineers, we oftentimes have to troubleshoot.

We try to focus on things that are actually broken. But a lot of times it’s just a matter of finding out why it’s not working. And it’s usually some kind of logic issue or something is built incorrectly. So if we take your text mode, we sometimes we’ll just put it into like a text editor. Honestly, anyone that works that will highlight things show you like the number of parentheses. Make sure you’re actually looking at that the logic correctly. So the if statements all line up and all that kind of stuff. It helps quite a lot. I know in custom forms, they’ve added like a text editor in there to kind of help validate those expressions. That is that is good. I think that is the gold standard right now. Like if it doesn’t work there, no matter what other text editors are saying, it’s not going to work. So, yeah, it’s amazing that we have that. Like I know we’ve got some og work fronters on this session and we remember the days that we didn’t have that. So, yeah, that’s a great that’s a great feature.

So I do want to talk about it’s not really on your on your on your session, but like talk about matrix reporting a little bit. Like I think that seems one of the things at least we get a lot of questions about. And it’s kind of one of the challenging like do you have any best practices in terms of matrix reporting? And using text most reporting as well. Yeah. Yeah. That does get kind of tricky.

I don’t know if I’ve actually spent as much time in that as I have with with other areas of text mode, just because it does get kind of kind of difficult.

It is grouping. But then you’re also bringing in different fields, right, that you’ve or different columns. So you have columns and you have groupings and then you’re going to be intersplicing them. Right. So you’ve got to make sure your columns are correct first and that they’re summing correctly and all that kind of stuff. And then you need to make sure your groupings aren’t causing any issues. But yeah, that’s something I could definitely dive into more if you guys have more questions about that and you reach out to me directly. Yeah. And let’s talk about like I want to talk about that idea of what you just said, because I think in terms of like learning text mode, using text mode, what you just said in terms of the matrix reporting is learning how to build reports and work front. And then also using text mode can be challenging. Let’s see. Should we use that word challenging? Yeah. So how do you definitely like how I guess whether maybe just like your advice on persisting and just not giving up and keep trying. Right. Like what are your. Yeah. Yeah. Yeah. Definitely keep at it. One of the things I would say if you had to break it down to like simplify things to a level that that makes sure that you’re really learning like a good foundation so that that everything going forward is easier.

I would learn a lot about how databases are structured and how like primary keys, secondary keys, many one to many relationships and all that kind of stuff. It gets into the API. But once you really get that down, that’s that’s really why we need text mode is our UI lets us do things that won’t break stuff. That’s that’s really, I guess, the easiest way to put it. The engineers put everything in the UI so that things won’t break, that the reports work seamlessly. But then we want to do something extra. So now we need to understand how those connections between different objects, like how there’s a reference. That’s the one to one relationship. And there’s collections, the one to many relationships. And if you really understand how that works, then it just makes everything easier. Yeah. And I want to talk a little bit about I have a question like it’s a specific one, but then we can talk a little bit about the purpose of report. So the question that came in is, is there any way around the issue that with a shared column like you have a column report that you’re not able to in line at it? And I just want to get your thought like that is a true statement, but I just want to talk about your again, your larger story of using the right report for the right message. Right. So the purpose of a shared column report is to do this at an in line editable. So I just want to get your thoughts on that. Right. Yeah. Yeah. A lot of people work out of reports. Right. So sometimes it isn’t this is just a place to view things easily that you’re sending to your I don’t know, your your vice president or whatever. You know, you want the executives to look at it and just see things. You don’t want them to go and edit anything. But a lot of times you’re working out of it. I would say merging columns there is helpful in that it could it could guide them to the right columns and then those columns you probably don’t want to merge so that they can just edit. Right. And you can maybe have explanatory text in a merge column that points over to the to the one to the right. It says edit this, you know, something like that. But yeah, there’s definitely two different types of reports that people build. There’s ones they work out of. And then the ones that are just ones that you teach you things about things. Yeah. Yeah. The ones that you share. And I just think that that I just want to make sure that that message from your presentation like that’s kind of like I absolutely agree. Like you can’t in line edit. But the shared column report is such a powerful report where you can like here’s for your executives that can’t click on anything. Right. Can’t break it. Yes. That is perfect. And then here’s the message. OK. So we have it’s this is going to be a shorter question. FYI, everybody, I like just before we started this, I twisted Nathan’s arm and he’s going to be willing to join us on some sort of scale event. So the question. Yeah, right. It does. So the question is like, hey, are there better like documentation, training and events on how exists work and all of that. So I just wanted to like let you answer that. But also maybe we’ll do an event to. Yeah. Yeah. So exists. The cool thing about exists. They’re really just straight out of sequel. So it’s like joins. Right. You’re joining between tables. So if you have that background exists, will make perfect sense to you. If you don’t, then it’s pretty advanced. It’s pretty difficult. There’s not a lot of resources out there right now. Internally, I’ve created a bunch of stuff and I actually shared a lot of that in that PDF that’s been shared. But we’re definitely going to want to do more trainings on that for sure. I love it. So everyone’s leaving. What do you want to do today? I’ll go make a cool report. I love it. And get some doughnuts. The Harry Potter doughnuts for sure. That’s what we were talking about earlier.

Nathan, thank you so much for sharing the value of text mode and just the storytelling. I love it. Thank you. Awesome. Thanks, Cynthia. Everyone have a great day.

Transforming Data into Actionable Stories

Unlock the power of Workfront reporting by combining technical expertise with storytelling.

  • **Advanced Text Mode **Enables flexible, customized reports that go beyond default UI limitations.
  • Merging Columns Reduces clutter and enhances readability, allowing you to present key project details in a single view.
  • Value Expressions Provide real-time insights, such as project status and schedule calculations, directly within your reports.
  • Custom Prompts Empower users to filter and interact with reports dynamically, catering to diverse team needs.

Applying these techniques helps you create reports that not only inform but guide and engage your audience. Use this knowledge to build records that reflect your unique voice and drive better decision-making.

recommendation-more-help
82e72ee8-53a1-4874-a0e7-005980e8bdf1