0
Category:
STATUS DETAILS

Comments

Also reported in the feed of the other merged item.Any update? ETA?we have no business unit scoping but simply have security roles in d365 setup with 'parent-child' access for the journey entity (and others). Users should normally only see the list of journeys within their own BU(s) as such. The Analytics (aggregate cross-journey analytics) seem to actually aggregate cross-journeys organization wide !? + there's even no option for users to filter the statistics for relevant-only journeys => within their business unit (or child bu).. only to select their journey names .. making it very inconvenient or useless ..We hope to get aggregated cross-journey analytics but respecting the parent-child bu security setup or at least have some other alternative option to define such filtering (eg new setting)

Category:

I believe we have a similar need / requestOur security role is setup with 'parent-child' access for journeys. However the Analytics dashboard (aggregate cross-journey analytics) simply seem to display the analytics organization wide .. not just as aggregate cross-journey (for journeys users have access to).Users neither have any option to filter their own (aggregate cross-journey) statistics in here .. other than selecting the journeys by name (in the entire list of all journeys) so that makes this dashboard inconvenient or even useless as such.Is this already planned? Any update on the ETA or planning?

Category:

This is really relevant, for us as well.

Category:

Hi Ayushi.Thanks for reaching out.Could you add more details on this requirement?RegardsMukesh

Category:

This will be a great help for the users experiencing. It is not logical that the user should use filter instead of using F3 search. The user cannot see that this is a flowfield and the value by that way not are searchable. So please add this feature asap.

Category:

This is really important for maintenance of best practices while implementing MSM. You don't want to test out and approve your configurations in a sandbox environment and then recreate them manually in a Production environment. It can introduce errors.

Category:

we need this for our production environment. Once we purchase dataverse storage, we don't want the space to be utilised by other environment belonging to other country team or by our citizen developers. We don't have centralised admin and we cannot enforce limit on other countries environment

Category:

This is similar to another idea https://experience.dynamics.com/ideas/idea/?ideaid=50e51819-afc6-ea11-bf21-0003ff68dcc1

Category:

This is similar to another idea https://experience.dynamics.com/ideas/idea/?ideaid=50e51819-afc6-ea11-bf21-0003ff68dcc1

Category:

With clients having to move to new platforms from GP, it is beneficial to MS to keep these clients in the MS world. To do so requires clients to maintain the features they have in GP that they know and love along with giving them greater flexibility in a new system. Since users currently have the functionality to close out statistical accounts in GP, these would be a good selling feature and beneficial to clients to have this option in BC. Currently the options available to them are cumbersome or expensive.

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500