Skip to main content
spencer_engel
spencer_engel
Expert ⭐️
May 14, 2020
New Idea

Allow reporting on custom mapped fields in Journey Orchestrator

  • May 14, 2020
  • 20 replies
  • 460 views

I recently found out via a support ticket that sometime in the recent past, we stopped writing back custom attributes to the AO Participants table in order to accommodate an “enhancement” of allowing the mapping of 50 custom fields of any type (rather than limiting admins to 6 string fields, 3 date fields, etc.).

 

I think we should fix this and do so soon. I have to think most admins would much rather have the ability to easily report on these custom field mappings if the tradeoff is being able to map more fields that they won’t be able to report on anyway. The “solution” I was given was to download a CSV of the participants from the program itself, load that CSV to the MDA, and then join it back to the AO Participants table. This is not scalable. Admins want to be able to map more custom fields because they want to report on them. 

    20 replies

    sai_ram
    sai_ram
    Expert ⭐️⭐️
    June 9, 2020

    @spencer_engel Thanks for bringing this up! We have added this to our near term road-map items. I will update you here once we consider it for release. 

    anna-whitehouse
    anna-whitehouse
    Contributor ⭐️⭐️⭐️⭐️
    June 17, 2020

    It would be great if custom fields were reportable from AO Emails, as well.

    phani_kumar
    phani_kumar
    Gainsight Employee ⭐️⭐️
    June 18, 2020

    I recently found out via a support ticket that sometime in the recent past, we stopped writing back custom attributes to the AO Participants table in order to accommodate an “enhancement” of allowing the mapping of 50 custom fields of any type (rather than limiting admins to 6 string fields, 3 date fields, etc.).

     

    I think we should fix this and do so soon. I have to think most admins would much rather have the ability to easily report on these custom field mappings if the tradeoff is being able to map more fields that they won’t be able to report on anyway. The “solution” I was given was to download a CSV of the participants from the program itself, load that CSV to the MDA, and then join it back to the AO Participants table. This is not scalable. Admins want to be able to map more custom fields because they want to report on them. 

    Yes, I came to know that we are not storing the Custome field Mapping fields in AO Participant object as we are offering to add 50 custom fields in the Custome Field Mapping section in JO.

      cmultanen
      cmultanen
      Helper ⭐️
      July 30, 2020

      +1, recently came across while working with Support on a program we are trying to set up. This would be super helpful to have again. 

        spencer_engel
        spencer_engelAuthor
        Expert ⭐️
        September 15, 2020

        Another common use case that is much more difficult now without being able to report on custom mapped fields: A/B testing. I created a program where I used a Case Expression to split my participants so that half would get an “A” version and half would get a “B” version.

         

        This all worked great, but...reporting on it is a huge pain now. I should just be able to use the AO Participants object and filter on my custom mapped field that designated the participant either A or B. Instead, I have to download the participants file as a CSV, upload it to a custom MDA object, and then merge it with the AO Participants object - all just to get this one custom attribute into my dataset. This is a LOT of extra work.

          nitisha_rathi
          nitisha_rathi
          Expert ⭐️⭐️
          December 24, 2020

          Reporting on custom fields will be available in Feb

            phani_kumar
            phani_kumar
            Gainsight Employee ⭐️⭐️
            December 24, 2020

            Super cool Thanks.

            andreammelde
            andreammelde
            Helper ⭐️⭐️
            February 10, 2021

            This would be super helpful…….

            Andrea Carroll
            mglarocca
            Contributor ⭐️⭐️
            February 10, 2021

            Thank you all. Critically important for us. we use very few custom fields on our programs but they have essential reporting elements. e.g. which test group A/B or which cohort are the participants a part of. 

              rakesh_lingala
              Helper ⭐️⭐️⭐️
              March 8, 2021

              Hello Everyone!

              Happy to announce that your request has been considered and included as part of the v6.22 release (SFDC / NXT). Journey Orchestrator custom fields are now available to generate reports from Report Builder as well as used as a source in Query Builder under the AO Participants Custom Fields object name. 

              This feature is implemented in both SFDC & NXT versions.

              Thanks for posting!

              Show more replies
              Terms & ConditionsAccessibility statement