Multi level custom url | Community
Skip to main content
M
MollieSh
Level 4
September 3, 2020
Solved

Multi level custom url

  • September 3, 2020
  • 3 replies
  • 896 views

Hi, I need to put a link to a program level custom field on a project report. I can get it to work when the fields are on the same level, but not when going "up" a level. Here is what I have for the same level:

displayname=Task List

link.url=customDataLabelsAsString(Project Task List)

textmode=true

valueexpression=IF(ISBLANK({DE:Project Task List}),"", "Task List")

valueformat=

And here is what I've tried for going from project to program level

displayname=Risk Register Link

link.url=customDataLabelsAsString(DE:program:Risk Register Link)

namekeyargkey.1=Risk Register Link

textmode=true

valueexpression=IF(ISBLANK({program}.{DE:Risk Register Link}),"","Click Here")

valueformat=

I'm almost positive it is a syntex error but I can't seem to find it. This code results in "Click Here" in the box but it's not actually clickable!

Thanks!

Mollie

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by MollieSh

    Just a FYI I did find a work around for this, although kind of cheating. I created a project level calculated field that is equal to the program level field that I want to display.

    3 replies

    Doug_Den_Hoed_AtAppStore
    Community Advisor
    Doug_Den_Hoed_AtAppStoreCommunity Advisor
    Community Advisor
    September 3, 2020

    Hi Mollie,

    If you can’t get the syntax working when the link is up a level, consider bringing it down first, then using the syntax that works from the same level (which is working).

    Regards,

    Doug

    K
    KevinQu1
    Level 10
    September 3, 2020

    Doug, tricks like these are among the plethora of things I need to memorize when trying to solve reporting problems. Any tips for getting them to stick in my brain? 😋

    Doug_Den_Hoed_AtAppStore
    Community Advisor
    Doug_Den_Hoed_AtAppStoreCommunity Advisor
    Community Advisor
    September 3, 2020

    “Never memorize something that you can look up”

    — A. Einstein

    You can search or use bookmarks in 0ne, Kevin, but if you’ve not yet started a personal “vault” of tips and tricks, naming the files with meaningful keywords you can later recall and search, and storing them locally for immediate and long term access, I encourage you to start today with this very post, and invest the minor amount of time it takes to develop The Habit.

    My Workfront vault is over a decade old, and I’m sure I’ve forgotten more than I know. But I know how to find it.

    Regards,

    Doug

    P.S. and yes, I searched the internet for the wuote so I could get it right

    M
    MollieShAuthorAccepted solution
    Level 4
    September 3, 2020

    Just a FYI I did find a work around for this, although kind of cheating. I created a project level calculated field that is equal to the program level field that I want to display.

    Doug_Den_Hoed_AtAppStore
    Community Advisor
    Doug_Den_Hoed_AtAppStoreCommunity Advisor
    Community Advisor
    September 3, 2020

    Excellent Mollie,

    Yes, my suggestion could be considered a cheat, but often on these, the end justifies the means. Glad it helped.

    Regards,

    Doug

      K
      KevinQu1
      Level 10
      September 3, 2020

      I prefer to think of these as "hacks"‚Ķ 😁 ...and this is a minor one in the grand scheme of Workfront hacks. More like a benign "trick."

      I've seen some of atApp's tricks (these are "hacks"...LOL), and shortly after launch I had to put together some doozies (I barely can handle text mode and you want me to do *what*!?!).

      You get used to it Mollie. Management here gets cranky about all the work-arounds (vs. out-of-box/built-in), but as an Admin, creative thinking is a tool in the toolbox.

      Thank goodness for this community!

        Terms & ConditionsAccessibility statement

        Loading footer...