How can I trigger a warning for duplicate project names in Workfront? | Adobe Higher Education
Skip to main content
H
himabi6
Level 2
June 13, 2025
Resuelto

How can I trigger a warning for duplicate project names in Workfront?

  • June 13, 2025
  • 4 respuestas
  • 587 visualizaciones

I'm looking for a way to trigger a warning or flag when a user attempts to create a project with a name that already exists in Workfront. The goal is to prevent unintentional duplication and maintain clean project naming across the system.

I've explored using custom forms and calculated fields, but Workfront Core doesn’t seem to support real-time validation or lookups for duplicate detection. Ideally, I’d like a solution that alerts the user upon project creation or update—either via Fusion or a custom logic setup.

Has anyone implemented a workaround for this, perhaps using:

  • Custom fields + validation dashboards

  • Fusion scenarios that monitor for duplicate names

  • Text mode filters or reports to highlight issues

Any guidance on the best approach

    Este tema ha sido cerrado para respuestas.
    Mejor respuesta de skyehansen

    we used to have a fusion scenario that would monitor for a similar thing -- users with duplicate names. So as a user is created, if another user in the system has the same name, the admins are contacted. I'll move your question over to the fusion forum -- I agree with you that Workfront itself will not support real time validation or lookups to detect duplication.

    4 respuestas

    skyehansen
    Community Advisor
    skyehansenCommunity AdvisorRespuesta
    June 13, 2025

    we used to have a fusion scenario that would monitor for a similar thing -- users with duplicate names. So as a user is created, if another user in the system has the same name, the admins are contacted. I'll move your question over to the fusion forum -- I agree with you that Workfront itself will not support real time validation or lookups to detect duplication.

      Doug_Den_Hoed__AtAppStore
      Community Advisor
      Doug_Den_Hoed__AtAppStoreCommunity Advisor
      Community Advisor
      June 15, 2025

       

      Hi @himabi6,

       

      Untested, but I wonder if the native but relatively new Business Rules might be able check for (and ideally; especially if doing so also governed Fusion behavior, at the database level...) prevent duplicate project names.

       

      On the tried and true front...

       

      You could create a native report grouped by Project name and defaulted to show as a column chart, then whack-a-mole any such bar of height > 1 by renaming the offenders uniquely.

       

      For easier whacking...

       

      You could also add an EXISTS filter to only include projects where at least one other project with the same name but a different ID (or Reference Number; both are unique) exists.

       

      I'm interested to hear how you make out - good luck!

       

      Regards,

      Doug

       

        ChrisStephens
        Community Advisor
        ChrisStephensCommunity Advisor
        Community Advisor
        June 17, 2025

        You could for sure write a Fusion scenario that could handle this. At a high level, it would look like:

         

        1. Create webhook that watches for a project's name to change (This should also trigger when project is created)

        2. Do a search for projects that have the same name that aren't the triggering project

        3. If any projects are found, do {thing you want to happen when name is duplicated}

          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          July 16, 2025

          @himabi6 Just checking in — were you able to resolve your issue?
          We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

          Kautuk Sahni
            Términos y condicionesAccessibility statement

            Loading footer...