Hi WF Community,
I'm looking to add a custom prompt to a Task report that allows users to pull in task data based on a custom prompt that looks at a custom field (DE:Portfolio Account Director) at the Portfolio level.
Example:
Custom Prompt: Portfolio Account Director
Dropdown Item Label: Joe Sample
Condition: project:portfolio:DE:Portfolio Account Director="Joe Sample"
I also attached a screenshot.
It's giving me the 'Whoops, something went wrong' error when I run it.
Anyone know where I might be going astray?
Thanks.
Nick
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
@Nick Valeriote‚ and @Brandon Pritchard‚ I've asked around and it seems it can be done, you just have to use an EXISTS statement:
For Emily, copy and paste the following into a custom prompt:
EXISTS:1:$$OBJCODE=PROJ&EXISTS:1:DE:portfolio:Portfolio Account Director:name=insert Emily GUID&EXISTS:1:DE:portfolio:Portfolio Account Director:name_Mod=in&EXISTS:1:ID=FIELD:projectID
For Nick and Kim, you'll want to update the GUID.
If you aren't sure how to find a user's GUID, you just have to click on that user's profile and grab the alphanumeric code following /user in the URL.
If you have any questions, let me know!
Views
Replies
Total Likes
@Nick Valeriote‚ Is that custom field a Typeahead field, Single line text field, a dropdown or a multi-select field?
Views
Replies
Total Likes
It's a Typehead field (user object lookup).
Views
Replies
Total Likes
I don't think you can do this with a typeahead field. You would have to create a calc field for the typeahead field to populate first and then use the calc field for the prompt condition. This is the same for the filter section. You cannot filter on a typeahead field. booooo
Views
Replies
Total Likes
Thanks for the input, Brandon. I tested the option you noted (custom calculated field that would populate my original typehead field value, and the system doesn't appear to let me create a calculated field based on another calculated field, or maybe just not on one that is a typehead format. In the formula (calculation field), it doesn't recognize/find my original typehead field.
Views
Replies
Total Likes
Hmmm. I would have thought for sure that was the trick there. My apologies. So, we can use typeahead field, but we cannot report on them?? That seems silly, but yea, I cannot get mine to work either. It recognizes it in the calculation field, but nothing pulls through on a form or report. There has to be way to leverage typeahead fields in a report! WF users unite!
@Nick Valeriote‚ and @Brandon Pritchard‚ I've asked around and it seems it can be done, you just have to use an EXISTS statement:
For Emily, copy and paste the following into a custom prompt:
EXISTS:1:$$OBJCODE=PROJ&EXISTS:1:DE:portfolio:Portfolio Account Director:name=insert Emily GUID&EXISTS:1:DE:portfolio:Portfolio Account Director:name_Mod=in&EXISTS:1:ID=FIELD:projectID
For Nick and Kim, you'll want to update the GUID.
If you aren't sure how to find a user's GUID, you just have to click on that user's profile and grab the alphanumeric code following /user in the URL.
If you have any questions, let me know!
Views
Replies
Total Likes
Nichole for President! That's super helpful. It worked. Thanks again for digging up an answer for us.
Brandon - thanks for the idea, and morale support.
Views
Replies
Total Likes
Nicely Done @Nichole Vargas‚ ! Nick, I attached a deck I picked up from a LEAP conference some years back that explains the EXISTS filter in pretty good detail, which may be helpful for future filtering. Also, not to steal this thread, but I am wondering if there is a solution for simply adding a typeahead field as a column rather than a filter?
Views
Replies
Total Likes
@Brandon Pritchard‚ If you want to add a typeahead field as a column to your report, you should be able to use the standard report builder and search for that field in the field list. If it's a user typeahead field, you will see two options underneath - iD or name.
If you are asking about referencing a Typeahead field in a text mode column, let me know!
Views
Replies
Total Likes
Thanks for the resource, Brandon.
Re your comment about adding a typehead field as a column rather than a filter, are you just asking if you can display a typehead field as a column in a report, or were you suggesting it as an alternative to my original request (custom prompt)?
Views
Replies
Total Likes
Oh lord... I have embarrassed myself. I was looking in a user report and not a project report where that field exists for us. 😋 But, what I meant was a reference, yes. When referencing a typeahead you get a string of data:
{"objCode":"USER","name":"Emily Petroff","ID":"5d5aa23701108d9615f6268381daf8a3"}
Is there an easy way to parse this out to the data you want? Like say, I just wanted to see the name and not the ID?
This will be my last question and then I shall bury my head in the sand...😣
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies