Universal fields and metrics that map to different customised Client Org fields

Brendan Codrington shared this idea 40 days ago
Idea Logged

Hi,


I would like to raise an idea to enable a way to set up standard fields/metrics in a view (replicated across client orgs or in a parent org view) which can then be mapped per client org to their customised fields.


Eg I have a standard % Females Applied field, and client org A uses field APP: Gender, answer ‘Female’, client org B uses field Gender App, answer ‘Female’ etc. Like usage parameters for a parent org source but at a field level.

Comments (3)

photo
1

Hi Brendan,


Thank you for raising these interesting enhancement ideas.


With this one, I'm going to need a little more clarity as I'm not clear on how this would be implemented. It sounds like you are after something similar to the functionality of a Parameter, however, as a global field. What I mean by that is that it might sit above/ separate to a View, where you might be able to add it as a field to another View, or have it be a compulsory part of setting up that View and then 'map' it to values in that View?


Let me know if I've misunderstood anything there, or if that is the general gist and I will go ahead and raise it for the Developers for consideration.


Kind regards,

Simon

photo
1

Hi Simon, I think it's similar to what you're thinking, and yes it is like the parameter but a layer down at the field level.

Like I map the parent org data source to each client org data source, I could then have a list of standard fields, that are used in the parent org views and at the parent org level which I then map to fields in each client's data source, or a calculated field using each client's data source.

Eg (at a very simplified level) I have a list of standard fields in the parent org: Sport Location; Favourite Sport; Sport Rank; Number of Participants.

  • Client Org A: mapped to their data fields MySportLocation; MyBestSport; SportRankings; CountDistinct(ParticipantID).
  • Client Org B: mapped to their data fields Town; TopSport; SportsNumbered; CountDistinct CASE WHEN Sport IS NOT NULL THEN PlayerID END.

Doing this then allows me to build reports at the parent level using the standard fields that then pick up each client's field/definition when that client runs it.

Does that help?

Kind regards,

Brendan

photo
1

Hi Brenadan,


Thanks for clarifying that for me. I've gone ahead and created an Enhancement Request to be looked at by Developers. They will assess this idea on a range of criteria, one of which will be feasibility, whereI don't know if this particular task is something that can be done easily. It might be the foundation for another, similar idea that achieves a similar thing in a different way. Nonetheless, I will get back to you with any updates once I hear them.


Kind regards,

Simon